This documentation supports the 22.1 version of Action Request System.
To view an earlier version, select the version from the Product version menu.

Specifying roles for deployable application states

In deployable applications, role permissions resolve to different groups depending on the development state of the application, such as Maintenance, Test, or Production. By mapping roles to groups for the Test and Production states, you can assign permission for all the roles while creating the application. When you change the application state at test or production time, the permissions for the new state automatically take effect.

When you create or import a deployable application, the state is set to Production. Only administrators and subadministrators have access to the application in Production state.

Specifying roles for deployable application states

You can change an application's state in the application tab in the editor area or through workflow, as described in the following sections. You can also create custom states for use by all deployable applications on the server.

To specify deployable application states

  1. Define role-group mappings for each state in the Roles form:
    1. In the mid tier, open the BMC Remedy AR System Administration Console.
    2. Select the Roles form and search for all roles defined for the application.
      If the search returns no roles, define roles for the application.
    3. For each role, make sure that the role is mapped to an explicit group for each state.
    4. Save the roles.
      For more information about roles, see Creating and mapping roles.
  2. Specify the state for the application, as follows:
    1. To open the application for modification, right-click the application's name and select Edit.
    2. In the Application tab, expand the General panel.
    3. Select a state from the State list.
    4. Select File > Save.
      The role-group mappings for the specified application state become effective after the server re-caches.

Using the user client or workflow to change deployable application states

The state defined in application properties is stored in an entry for that application in the AR System Application State form. You can edit the entries in this form in the user client or create workflow that acts on this form to change the application's state.

When creating the workflow, remember the following tips:

  • A state value of NULL is the same as the Maintenance (administrators only) state.
  • State names are case-sensitive.
  • Entries are removed from the AR System Application State form when applications are deleted.

Creating custom states

You can create custom application states by adding fields to the Roles form. Use field IDs in the range of 2003 to 2199.

To create custom states

  1. In Developer Studio , open the Roles form.
  2. Overlay the Roles form.
    Customization on upgrade is not lost if the overlay is present. You cannot modify the Roles form if the overlay is not present.

  3. Under the Production field, add a character field.
  4. In the Properties tab, in the ID field, enter a unique field ID in the range from 2003 to 2199.
  5. Save the form.
    AR System server  automatically adds a menu to the field for selecting groups. The new state is available for deployable applications on the current server after the server re-caches.
  6. To make custom states available on another server, export the Roles form and import it on the target server.
    For more information about exporting and importing forms, see Exporting and importing definitions.
Was this page helpful? Yes No Submitting... Thank you