Can it be that in the 2.5 Beta, an object is committed to the database immediately after it has been created? It appears that when, in a microflow, I do a create and then immediately a retrieve from the db ( [id=$createdobject] ) the object already exists in the db. As a result I can not use this to check whether an object has already been saved by the user or not. If so, is this on purpose? And is there an alternative to perform the check?
Frans Verschoor (FraternIT)
You can perform this check by using the isNew() function in a microflow expression. This function returns true if an object is created but not yet committed.
After create an object is indeed already available in the database (within the same transaction). This is needed to determine the ID of the object.