Managing Changes to your ASM Application

During implementation, you will likely be working with a consultant from Alemba to configure and deliver the ASM application. It's reasonable to assume you would be making these initial configurations in Production, but what happens after it has been delivered and your organization is using it on a day-to-day basis? How will you continue to keep the system updated and relevant, or even safely add new capabilities?

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.

Best Practice: System Configuration Post Go-Live | ASM HERMES 10.6