Update Entities and Save Entities differences?

Unknown

Update Entities and Save Entities differences?

Unknown

As in title, not sure what the differences are between the update entities and save entities steps. What are these and when should I use one over the other?

Unknown

The Update Entities step contains Fetch Entities functionality with it to so it may grab the desired entities to update. Once the fetch criterion are met, the entity alongside its individual data members updates with new data and then saves that onto the entity. That being said, the Update Entities step requires pre-existing data to perform. If youre trying to maintain data that requires change (i.e. it is not expected to stay static once submitted), then the Update Entities step should work for most use cases.

On the other hand, the Save Entities does not contain Fetch functionalities because it does not require pre-existing data to perform: it just saves the entirety of the predefined entity in the database. This is better used for saving something after its been manipulated by a flow such as in the case of leased entities.

An example of using Save Entities in this way is exemplified in the [url=https://documentation.decisions.com/docs/leased-entities]Leased Entities[/url] article under the Leased Entities in a Workflow Proces subsection.