Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring a user reference on a form

Updated on April 5, 2022

After you add a user reference to a form, you can configure the way that users interact with it. For example, you can display the list of users in your application as a list or as an autocomplete that returns a list of search results.

Tip: To find the current users in your application, enable application-editing mode and then click Users.
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.

  2. On the Workflow tab, click Life cycle.

  3. Click an assignment or an approval step.

  4. Click Configure view.

  5. Click the Gear icon in the row of the user-reference field.

  6. Select a control type from the list that is displayed.

    • Search — Prompts users to search for an existing user by entering a full name or operator ID in an autocomplete field.

    • Dropdown — Prompts users to select the full name of an existing user from a list.

  7. Click OK.

Result:

At run time, users are prompted to select or search for an existing user, based on the control type that you provide. The result, a user ID, is stored in the property that is associated with your user-reference field.

  • Adding single-value fields to forms

    Collect specific information from users when they process a case by adding a single-value field to a form. For example, you can add a field that references a phone number to a form that prompts users to enter their personal and address details.

  • Storage and display of fields

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