Committing Changes Made on Edit Form

Clicking Done on the Edit mode form page commits all changes to the database. Clicking Cancel cancels all changes.

When the user clicks Done, the system executes the following:

  1. Validates all the field values for the format specified in the field format setting. The system also checks for the presence of values in fields with the Required=true setting. For more information, see Validating Form Field Data.
  2. Validates all the field values using any user defined/custom JavaScript methods configured in the field Validate setting.
  3. Submits the for processing and checks to see if there are any changes made to the data.
  4. Updates the changed fields by grouping them as business object basics, attributes, relationship attributes and program fields.

If the user clicks Done multiple times, multiple submissions are not sent.

You can also refresh the view mode after editing object properties.

After the system commits the form page (in Edit mode) changes to the database successfully, it refreshes the opener frame (typically the View mode of the form page) to display the updated data.

When the object's vault is changed, the objectId changes and therefore the objectId on the View mode of the form page updates automatically to refresh the data.

ENOVIA recommends that vault changes not be done. If business logic requires that the vault be changed, then it must be controlled in an action outside of the Edit Properties function to force a full tree refresh.

When the form is updated while the context tree is present, and the change caused an objectId change, then the tree is updated with the new objectId. The form component automatically senses the change in objectId and updates the context tree as required.