Skip to main content


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

Adding a custom tool

Updated on March 15, 2022

This procedure uses the example scenario from Adding a subsection for similar tools.

  1. Right-click the handle (blue dot) of the Comment row for the section that you want to add tools to and click Add Sibling Below.
  2. Add a new page row.
    1. In the Action column, select Append and Map to.
    2. In the Target column, enter .pyRulesAndToolsList.
    3. In the Relation column, select a new page.
  3. Complete four Set rows for the top-level expandable section. In the Action column, select Set and then enter the following:
    RowTarget column valueSource column value
    Note: Be sure to include the quotation marks
    1.pyNoteThe tooltip text to be displayed in Access Manager; a short description of the tool function.

    For example:"Retrieve number of items in worklist."

    2.pyPrivilegeThe privilege name.

    For example:"CanUseWorklistCounter"

    3.pyClassNameThe privilege class name.

    For example:"@baseclass"

    4.pyLabelThe tool function name to be displayed on Access Manager.

    For example:"Worklist items counter"

  4. Save the data transform.
For example:

The preceding example creates a custom tools section with a subsection for Worklist tools, as shown in the following figure:

Custom tools section with Worklist tools subsection
The custom tools section with the worklist tools subsection

This data transform renders a section in Access Manager as shown in the following figure. (Refresh the display to see the changes.)

Access Manager section with Worklist tools subsection
What to do next: In Access Manager, secure the tool. For more information, see Editing tools authorization for a single access group.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us