Skip to main content


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

Creating personas

Updated on November 15, 2021

For enhanced planning and understanding of your business processes, add participants to your Microjourney by creating personas. When you create personas, you group users by their responsibilities in a process, the channels that they can access, and the cases on which they work.

For example, for a hiring process, you can create personas that represent a job candidate, an HR worker, and a manager.

When you create personas, you define metadata that represents the users of your application. By visualizing users, you can easily plan and communicate the development of your application.

Before you begin: Define your case type, and then populate the case life cycle with stages, processes, and steps. See Adding case types to organize work.
  1. In the navigation pane of App Studio, click Users, and then click Personas.
  2. In the Personas header, click New.
  3. In the New persona window, in the Persona name field, provide a descriptive name for your persona.
    For example: Enter HR worker.
  4. Select an avatar to represent the persona.
  5. Optional: To provide more information about the persona, in the Description field, enter additional text.
    For example: For an HR worker, enter A user that processes job applications.
  6. Click Submit.
    Result: Your application saves a new persona and adds it to the Personas landing page.
  7. Optional: To see which channels a persona uses to interact with case types in your application, on the Personas landing page, select the Include draft relationships check box.
What to do next: Associate the personas that you create with your Microjourney. See Associating personas with case types.

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