About State Configuration in ASM

ASM leverages State Configuration Roles, which you can assign to Security Users to manage who can transition strategies from one state to another.

Details

In the baseline Meridium Enterprise APM database, no State Configuration Roles are assigned to any state in theAsset Strategy State Configuration or the Asset Strategy Template State Configuration. If needed, an administrative user can assign State Configuration Roles to these states.

Throughout ASM, some options will be disabled based upon whether the current user is assigned to the State Configuration Role that is required to perform that action. In other words, if an action will change the state of the strategy (e.g., adding an Action record) and the current user does not have permission to change the state, all options that would cause the state to change will be disabled. For example, consider the following scenario:

In this case, when the ASM Reviewer opens on the Asset Strategy Actions page an Asset Strategy in the Pending Review state, the following options will be disabled on that page:

If no State Configuration Roles are specified for State Configuration, as in the baseline database, all options will be available to all users, and state changes will not be restricted. To take full advantage of the features in ASM, we recommend that you assign members of the ASM Security Groups to a corresponding State Configuration Role.

The following diagram shows the states and operations that exist in the baseline State Configuration for the Asset Strategy family. You can use this diagram to determine which operations will appear on the Operations menu when you are viewing an Asset Strategy. The Operations menu will display any operation to which the current Asset Strategy record can be transitioned from its current state.

Note: The information in this topic also applies to the configuration of Asset Strategy Template State Configuration.

Copyright © 1993-2015 Meridium, Inc. All rights reserved.