Screen 3: Edit Screen

The Edit Screen should be accessible either as a button on an ActionGrid in the Search Results screen or a link in a View Screen or a link in a Static grid. The Edit Screen should not be directly accessible in any menu.

The link to the Edit page must contain ONLY ONE query string parameter the name of this parameter should be “id” and the value of it should be the unique identifier of the record (or parent record) being edited i.e. the UID field (prospect_uid, job_uid etc.). There should NOT be any other parameter in the query string. Please note the “id” should never be an INT and an INT should never be passed in the query string. Only an UID should be passed in the Query String.

To develop an Edit Screen follow the process:

• Create a new page using the default template.

• Add an ActionForm module to this page.

• Follow UI conventions to layout the page i.e. labels must NOT be hard-coded by stored in the table omni_system_labels

• In the Pre-Condition for the page add the SP or the Select statement to load the data – ensure that the field names are correctly called for the variables in the page. Each of the field names in the select statement must correctly map to the field names in the Form.

• For each field add the appropriate validators (See Add Screen for validators to add)

• To the Save button add Actions for saving the data.

• The data must be saved through a SP or an update statement.

• For tables with updated_on and updated_by fields ensure that these fields are populated correctly.

• The SP or Update Statement should return a Code for Success / Failure – NO Direct message should be returned by the SP/Update Statement.

• Make sure that field names DO NOT have the underscore '_' character.

See Video on setting up an Edit Screen: