ASM Application Configuration Change Management
Implement Change Management around your ASM application's configurations.
Last updated
Implement Change Management around your ASM application's configurations.
Last updated
The ASM Application Configuration Change Management Workflow as detailed here, is provided as an example for those clients wishing to implement a targeted CM process around managing changes and configuration in their ASM application post go-live.
ASM ships with a standard Change Workflow for you to use that is widely applicable to all changes in your organization. ASM does not ship with the Change Management Workflow Template, message templates, or screens outlined in this section.
It is important when changing the ASM application configurations that all changes are captured. ASM has a native Audit capability that will track changes to the system values, screens, workflows, tickets, and virtually all other entities. You can even turn on field-level auditing to capture changes to individual fields in real-time. System Auditing is not the same as Change Management. Auditing merely captures changes as they occur, whereas Change Management will potentially stop changes before they occur. For a complete solution, enable both System Audit and Change Management.
Audience: System Administrators/ASM Developers with sufficient rights to update, change, and configure ASM, ASM Screens, and ASM Workflows.
For this document, we will talk about the administration Audit and Workflow Auditing only. To find more information about the other audits you can make use of, enter the word "Audit" in the global search above.
Using Change Management, you are able to automate, track, gain approvals, and capture details that System Auditing simply can not. The next section will illustrate a sample ASM Change Management Workflow and screens that you can use in your own organization to begin defining and capturing all of the changes to ASM.
