Scope

The Scope tab allows you to define the hierarchy of the functional area from the topmost level to the bottommost level. Since approvers are to be added at the last level of the sub-functional area hierarchy, it is recommended that the entire hierarchy be created first and values added later. Click Add Scope to define the first scope (sub functional area). Provide the following information in the panel displayed below:
  1. In the Sub Functional Area Name field, provide a name for the scope (sub functional area).
  2. From the Functional Area Variable drop-down list, select the required variable. All the variables created in Infor Risk & Compliance for the selected Insight are available for selection.
  3. Select the Applies to Emergency Access Requests check box if the functional area is for emergency requests.
    Note: This check box is enabled only if the functional area variable with technical name Role/Responsibility is selected.
  4. Select the Available in Request Submission check box if the roles selected in the Functional Area Variable field must be available for assignment through FA variables when creating a request. If this option is not selected then the role selected in the FA variable is not available on the request creation page. However, a user can assign those role through direct role assignment.
    Note: This functionality is currently supported only by AI for SAP.
  5. Use the Naming Convention Mapping or the Explicit Mapping panel or both to associate specific values to the scope. You can also assign specific approvers for these objects. For example, select Role in the Functional Area Variable field, Role 1 and Role 2 in the Value field from any one of these panels and User 1 in the Approvers field. In this case, when a request for Role 1 or Role 2 is created, it is routed to User 1 for approval.
  6. Naming Convention Mapping Panel

    Use this panel to associate specific objects to the selected functional area variable or to provide the naming convention for certain objects. For example, specify A*( with the wildcard * or ?) in the Value field to associate all the objects starting with A with the scope of the functional area. Expand the Naming Connection Mapping panel and provide the following information:

    1. In the Value field, provide the naming convention for the specific object. For example, A*.
    2. In the Approvers field, specify the required approver. Multiple approvers may be selected.
    3. Click Add to List. The naming convention and approvers selected are displayed in the panel below.
    4. The object is displayed as a hyperlink. Click the link to change the object or the approver. The Update List tab is displayed. Click this tab and make the required modifications
  7. Explicit Mapping Panel

    Use this panel to associate specific objects with the selected functional area variable. Expand the panel and provide the following information:

    1. The objects displayed in the Value drop-down list depend on the functional area variable selected in the Functional Area Variable field. For example, if Connection is selected, all the Insight specific connections available in the application are displayed. Select the required object.
    2. From the Approvers drop-down list, select the required approver for this object. Multiple approvers can be selected.
    3. Click Add to List. The selected object and the approver are displayed in the grid below.
    4. The object is displayed as a hyperlink. Click the link to change the object or the approver. The Update List tab is displayed. Click this tab and make the required modifications.
  8. Click Add to add these objects and assigned approvers to the sub functional area.
  9. Click Add Scope to add another scope. All additional sub functional areas are added below the first one.
  10. After adding all the required scopes, click Save and Close to save your changes to the database.

    If you are adding only one scope, you have to add approvers to this scope. On the other hand, if you are adding multiple scopes, only the leaf level approver is considered in approval stages. For example, if you add sub functional areas for the functional area variables Connection, User and Role (in this order), the approver associated with Role is only considered for approval.

    Note: A maximum of five levels of sub-functional areas can be added.