{SAVE POINT: }
This rule is valid within onchange directives only. It provides a temporary “checkpoint” save of an issue for the current user. Issues are only submitted for permanent saving to the database when the user subsequently clicks on the Submit button, or they are idle for a period that amounts to the value stored within the behavior setting named SAVE_CONTINUE_TIMEOUT_SECS. This command is typically used within sites with complex workflow, where users spend a large amount of time processing an issue, and where there is a concern that they may be interrupted by a system failure or that they may leave their computer screen open with unsaved work in progress. Once the SAVE POINT action has been triggered and before the Submit button has been clicked, other users may not update the same issue. If they attempt to do so, they will receive an error message.
The command is typically executed within the rules when the user completes a part of the screen and is about to move to a new section. For example:
<== onchange ==>
if (FOLD_PRE_DETAILS.{changed}) {
{SAVE POINT: }
}
When the user clicks on the fold field named FOLD_PRE_DETAILS, the issue will be saved temporarily. Processing continues normally for the user, and they will need to click the Submit button in the normal way to permanently update the issue, or they leave their screen open for the amount of time specified in the bahavior setting named SAVE_CONTINUE_TIMEOUT_SECS. However, if the user closes the screen or there is some failure, and they edit the issue again within the timeframe specified within SAVE_CONTINUE_TIMEOUT_SECS, they regain their place and all field values at the checkpoint where the issue was last saved.
During the time that the issue has been saved at a checkpoint, until the issue is Submitted or automatically saved, no other user can edit the issue.