Skip to main content

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

Defining the product operational structure

Updated on April 20, 2021

Leverage the product operational structure for routing and reporting within the application. Typically, the product operational structure does not map operators exactly to your products organization but instead, it maps the work that those operators do.

Product Designer for Financial Services

To support complex product structures, the standard Pega Organization and Security functionality is extended in the application. Use this functionality to create and name levels in the produ ct hierarchy between the Financial Institution level and other lower levels such as Business Line and Product Category.

Product Designer for Financial Services includes a sample product structure and its associated taxonomy. You should familiarize yourself with the intricacies of this organizational structure and its use by the set of Demo operators provided in the PDFS Demo application.

Use the Organization structure worksheet in the Implementation Planning Workbook to record your decisions during this procedure.

  1. Log in to the application as PDFSSysAdmin using the password that you specified when you enabled this operator; to enable Pega-provided operators, see Enabling operators.
  2. Click Dev Studio > Financial Services > Product Structure. The sample product organizational structure is named “Uplus FS Product Operations”.
  3. Review the existing structure and taxonomy.
  4. Determine the organization, division, and unit levels of the hierarchy.

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