If the object you are saving to is the primary work object (the one whose flow the utility shape is in), then don't save at all.  Just update the property.  The system will save it for you.

If the object you are saving to is another object, then use obj-open with locking and then use write-now on the save.

It is important not to save or commit the primary work object, because if the system ever has to roll back, it will cause errors such as "flow not at task" or "flow removed".

The general difference between save with write-now and commit is that the first saves only one specific object, whereas commit saves ALL the objects that have data waiting to save.

Until the next commit has occurred, either explicit or automatic, changes are not reflected in the
database. Automatic commits are performed:

• When a new item is created
• When a work object is updated, resolved, or reopened after processing for a flow-action is completed
• When an assignment is created or completed
• When GetNextWork processing transfers an assignment from a workbasket to a worklist
• When an additional flow execution starts for an existing work item