SAVE

{SAVE: [CONTINUE_ACTION = PAGE | AJAX | DEFAULT]}

This rule is valid within onchange directives only. 

If used on an add screen, it provides functionality equivalent to use of the Insert and Continue button.  When the action is triggered, the issue is inserted with its current values, and the user is automatically directed to the edit screen to continue working.  The behavior setting named SAVE_AND_CONT_ACTION must be set to a value of PAGE for this to work on an add screen, as ExtraView cannot perform an Ajax request to switch from the insert mode while adding an issue, to an edit screen which is what is displayed after the Continue action.

If used on an edit screen, it provides functionality equivalent to use of the Save and Continue button.  When the action is triggered, the issue is saved with its current values, and the user continues working within the edit screen of the issue to make further changes.  You may use a value of AJAX for the SAVE_AND_CONT_ACTION behavior setting.

The optional parameter CONTINUE_ACTION along with one of its three possible values define what happens following the successful completion of the SAVE rule.

• PAGE forces a full screen refresh of the current edit screen
• AJAX only performs an Ajax refresh of the screen and thereby only altered values (if any) are updated on the screen
• DEFAULT performs the default action following the SAVE action.  The DEFAULT value is taken from the behavior setting named SAVE_AND_CONT_ACTION.

Example

The following example performs a save of the current issue on an add screen, when the user alters the value of the PRIORITY field:

<== onchange ==>
if (SCREEN_NAME = 'ADD' && PRIORITY.{changed}) {
  {SAVE:}
}