Skip to main content


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

Extensions to Pega Process Fabric worklists

Updated on November 9, 2021

Extensions pass fields from your application to the Pega Process Fabric Hub so that the Pega Process Fabric Hub reflects data from your application. Overriding default extensions maps the values between your application and the Pega Process Fabric Hub in a way that is accurate for your unique business scenario.

Additional fields that the Pega Process Fabric Hub includes are Customer, Product, and Account. With the additional fields, you can present more detailed assignment data in the Pega Process Fabric Hub. If your application stores related data in fields with different names, by overriding default extensions, you ensure that information between your application and the Pega Process Fabric Hub passes correctly.

Standard assignment data

The Pega Process Fabric Hub includes the following standard fields to store assignment data:

  • RegistrationID
  • AssingTo
  • AssignToType
  • CaseTypeClass
  • Status
  • TaskID
  • Label
  • Priority
  • TaskCreateDateTime
  • TaskCreateOperator

The Customer, Product, and Account fields are additional and you can use these fields to pass more detailed data to the Pega Process Fabric Hub by using extensions.

You add the Pega Process Fabric extensions to your application when you install the Pega Process Fabric Hub connector component. The extensions use both bulk sync and real-time APIs to pass data from your applications to the Pega Process Fabric Hub. If you want to pass values from fields in your application, first you need to identify the class that stores the field value in your Pega Platform system.

Assign- classes

To pass values that the system stores in the Assign-Worklist or Assign-WorkBasket classes, you override the following items:

  • The Assign-Worklist.pyPF_PublishBulk and Assign-WorkBasket.pyPF_PublishBulk report definitions by adding your columns to these reports.

    The bulk sync that runs during the registration activation process uses these reports to fetch assignment data from the database. However, real-time sync uses assignment BLOB for sourcing assignment data. As a result, overriding the Assign-Worklist.pyPF_PublishBulk and Assign-WorkBasket.pyPF_PublishBulk report definitions impacts only bulk sync.

  • The Assign-.pyPF_SetRequest data transform by adding your field, for example RequestPage.label = Primary.pxTaskLabel.

    Both bulk sync and real-time sync use this data transform to prepare the task request.

Work- classes

To pass values that the system stores in your Work- class, you override the following items:

  • The Work-.pyPF_GetCases report definition by adding your column to this report.

    Both bulk sync and real-time sync use this report definition to fetch case information in the task request preparation.

  • The Work-.pyPF_SetRequest data transform by adding your field, for example the RequestPage.caseLabel = Primary.pyLabel format.

    Both bulk sync and real-time sync use this data transform to prepare the task request.

Other classes

If the value belongs to a class that is different than the Assign- or Work- classes, you override the System-Queue-PPF-Connect-Assign data transform by adding your field, for example RequestPage.accountID = Primary.pyAccountId. Both bulk sync and real-time sync use this data transform to prepare the task request.

Order of preference

Avoid including a field in multiple extensions. However, if your business process requires the same field in multiple extensions, the system considers classes that store fields in the following order:

  1. The System-Queue-PPF-Connect-Assign.pyPF_SetRequest data transform
  2. Your Work- class
  3. The Work- class
  4. The Assign- class

For example, if you include the same field in the Work- and Assign- classes, the system references the field from the Work- class.

AllowedRegistrationAccessGroups dynamic system setting

To register an application in the Pega Process Fabric Hub, your access group needs to have administrative privileges. The default administrative access groups are Application:Administrators and Application:Authors. To meet your unique business requirements, you can create your custom access group with administrative privileges. To use your custom access group to register applications in the Pega Process Fabric Hub, edit the AllowedRegistrationAccessGroups dynamic system setting.

A default value of the AllowedRegistrationAccessGroups dynamic system setting is All:Administrators,All:Authors. You edit the dynamic system setting by adding your custom access group in the comma-separated list.

For more information, see Editing a dynamic system setting.

    • Previous topic Activating applications in the Pega Process Fabric Hub
    • Next topic Managing applications in the Pega Process Fabric Hub

    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