ASM System Fields for Approval 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.

triangle-exclamation
circle-info

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. REQUEST_DESC/Description

  4. The Whole of the Task Information Section

    • Task Title

    • Order

    • Task Priority

    • Task Type

    • Task Phase

    • Planned Start

    • Target Date

    • Auto Calculate Target Date

    • Recalculate Dependent Tasks

    • Planned Time

    • Work Start

    • Work End

    • Resource Managed

    • Resource Allocated

    • Duration

    • Skills

  5. TASK_DESC/Task Description (This is often used to form the body of emails the task sends)

  6. Manage CMDB Transactions

  7. REQUEST_SERVICE_REFS/Linked Services

  8. REQUEST_ITEM_REFS/Linked CIs

  9. HISTORY_DESC/Action

  10. PUBLIC_HISTORY/Visible in Self Service Portal

  11. HISTORY_REF/Action Type

  12. FORWARD_DATE_/Action Start

  13. END_DATE_/Action End

  14. ACTION_TIME/Action Time

  15. HISTORY_EXPENSE/Expenses

  16. CLEAR_APPROVAL_COMMENTS/Clear Approval Comments on Activation

  17. Action Buttons at the Bottom of the Screen

    • Buttons can be relabeled

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

  18. For User Approval Tasks, the whole of the Recipient Section

    • Select Users

    • Defer

    • Forward to Recipient Set on Template

    • Forward to Recipient on Activation

    • Forward to Last Forward to Recipient

    • Forward to Last Recipient

Last updated