ASM System Fields for Request Screens

It is possible to delete ASM System fields. When you delete a field, the data held on the field is not deleted. It is held in the database. If you were to re-add the field back to the screen, any data previously there will still be there. However, even if no data is lost, deleting the fields can still have unintended consequences: Many of the ASM System fields are referred to in Java scripts and style sheets and deleting them could impact your screens or even render them unable to load.

If a required System Field has been deleted from the screen, it will appear in the dead zone when viewing the raw HTML. These fields must not be cleared from the dead zone unless you add them back to the main body of the screen. System fields should remain attached to the screen in one of these 2 capacities.

Best Practice

Do not delete the System fields, even if you will not be making use of them. Rather, create a new section on your screen and call it System Fields, or Unused/Reserved Fields (anything you like), and then hide the section.

The following system fields must remain on the screen:

Please Note: The format below is DB (database) ID/Typical Display name and label. Labels can be reconfigured and could be different in your system. Always compare the Field's DB ID.

1. REQUEST_TITLE/Request Title

2. REQUEST_REF/Ref

3. ORDER_ITEM_QUANTITY/Service Order Item Quantity

4. REQUESTOR_REF/User

5. The Whole of the Type and Priority Section

   • Type

   • Priority

   • Risk

   • Target Date

   • Imp Start

   • Imp End

6. CLIENT_COMPANY_REF/Organization

7. REQUEST_SERVICE_REFS/Linked Services

8. REQUEST_ITEM_REFS/Linked CIs

9. REQUEST_DESC/Description

10. HISTORY_DESC_HTML_EDITOR/Actions&Solutions

11. PUBLIC_HISTORY/Visible in Self Service Portal

12. ACTIVITY_REF/Action Type

13. Action Buttons at the Bottom of the Screen

    • Buttons can be relabeled

    • Buttons can be hidden (do not hide 'Save' or 'Submit' buttons)