Bizagi is a collaborative tool that allows many users to work in the Work Portal on the same process at the same time, in parallel activities. To make sure the integrity of the information, Bizagi uses a concept called Long-term transactions. This is an essential technology used when many people work on a project simultaneously, to prevent different users editing (overwriting) the same data. In Bizagi this technology is called Scopes.
To this end, the information of all activities is stored in the Scope and only updates the database when the user clicks the Next button.
When a user is entering information onto a pending activity in the Work Portal, it can be saved by clicking the Save button; the case can be continued later. However, this information is not validated until the user clicks Next, at which time the rules that make sure data integrity are run, i.e. when the user is sure he wants to end this activity.
Think of the Scope as a temporary memory storage that ensures the information is saved and remains as the end user enters it, but is not reflected in other opened activities of the same process, until Next is clicked; this is when it is finally persisted.
In the event that the user clicks Save, the information will remain in the Scope of the activity and not in the database.
When Next is clicked, the information entered will persist in the database and thus, be available for all other opened activities (in opened parallel activities) and for the next pending ones in the process flow.
XPath navigation uses the information in the Scope, not the database. You must always use XPath navigation in Expressions, Document templates, Policies, interfaces, etc.
When it is necessary for an external system to send information to Bizagi it must use methods of the Bizagi SOA Layer to send information directly to the Scope and not to the database.