Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Creating a requestor type

Updated on July 8, 2022

Create a requestor type data instance by selecting Requestor from the SysAdmin category. Provide access to applications for any person or external system signing in through the requestor type. Optionally, identify an access group — or in special situations, more than one access group — to be available to requestors of this type. As a user or other requestor signs on, the system adds the RuleSets and versions in the application rules of the selected access group to the user's RuleSet list.

Create a requestor type only in rare special situations.
  1. In the header of Dev Studio, click CreateSysAdminRequestor Type.
  2. Create the requestor type:
    1. In System Name, enter a name for the system instance you are creating.
    2. In Requestor Type, enter a name for this requestor type, such as BROWSER, APP, or BATCH. Start the name with a letter and use only letters and numbers.
    3. Click Create and open.
  3. On the Definition tab, define the requestor type access permissions according to the following table:
    Define this requestor type usingSelect Application-based Access Group.
    Access Group NameEnter an access group that contains an application rule and one or more access roles. The RuleSets and versions identified in the application rule in this access group become visible (to rule resolution) for all requestors of this type.

    Except as described below, enter only one row in this array, and select the radio button for that row

    For the BATCH instance, you can list additional access groups that are to be available to legacy agents, for the agents where the Agents field on the Security tab of the Agent Queue data instance is blank.

    Note: Make sure that all of the roles and permissions needed for agents and DelayedItemsDataFlow to run are available through the configured access group.

    For example, list access groups for the Pega-ProCom agent here; the agent needs application-specific access to send correspondence and to find and enforce service-level agreements (SLAs).

    • If the Agents field on the Security tab of the Agent Queue data instance is not blank that access group is used, and the list in the BATCH requestor data instance is ignored.

    For the BROWSER instance, you can list additional access groups that are to be available to all browser users — including unauthenticated users — through the application switching facility.

    • As a best practice to restrict access to authenticated users, list such access groups in an Organization data instance, rather than in the BROWSER requestor data instance.
    • It is required to distinguish unauthenticated access groups from authenticated access groups. Therefore, any access groups specified here must NOT match access groups specified for operators.

    You may enter additional access groups in this array for requestor data instances other than the BATCH and BROWSER instance.

    • Standard rules ignore all rows except the single access group that is marked with a selected radio button.
    • This array is not a means to provide more than one access group to services or portals.
  4. To start an activity when a browser-based requestor connects to the system, click the Activities tab, and then select the activity.

    Identify the first activity to be executed when a browser-based requestor connects to the system. If this field is blank, the system uses the default starting activity Code-.Web-Start, which displays the login window.

    Enter both key parts, in the format Code-.ActivityName. Make sure this activity belongs to a RuleSet and version that is available to guest users.

    When they connect, users can override this setting by specifying another activity in the URL.

  5. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us