Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Pega Process Fabric Hub for the enterprise

In large enterprises, it is common that a number of new and old technologies are used to construct separate applications to automate the business. To complete their work, users commonly log in or switch contexts several times between applications during the workday. Most of these applications exist in their own silo. Siloed applications increase the effort to complete tasks because the information is not easily shared between applications.

The Pega Process Fabric Hub is a tool that allows you to unify, manage, prioritize and automate the tasks related to employees or users by using data from multiple independent applications running on different technologies. This gives your managers and employees a single touchpoint for worklists, assignments, and insights.

Consider the following scenario:

A major bank has the following applications.

  • Pega Platform™ is used to develop credit card and loan applications.
  • ServiceNow is used to develop complaint management and account opening applications.

Tasks are routed to a worklist or work queue in each application. Analysts can perform those tasks by switching/logging into the independent applications hosted on different URLs.

Alternatively, the Pega Process Fabric Hub can be used which allows analysts to access tasks from several disparate applications. Logging into the Pega Process Fabric Hub lets analysts complete tasks from all applications without switching context multiple times during the workday, which saves time and increases efficiency.

Pega Process Fabric Hub uses open (REST) API architecture, which makes it possible for other open (REST) API-based applications to connect with the centralized Pega Process Fabric Hub application.

Beginning with Pega Platform version 8.1, the Pega Process Fabric Hub supports applications that are hosted on the following deployments:

  • On-premise
  • Pega Cloud® services
  • Client-managed clouds

Pega Process Fabric Hub relies on case types and assignments and fetches data about assignments that users complete as part of case processing.

Note: Tasks that are created as part of Pulse or Spaces are not supported in Pega Process Fabric Hub.

The Pega Process Fabric Hub's central storage has the following data:

  • Application registry.
  • Tasks of all registered applications.
  • Association of operator work queues.
  • NextBestWork/GetNextWork configuration.

 

Pega Process Fabric Hub Architecture
In this diagram, the Pega Process Fabric Hub leverages Rest APIs to Register, Sync assignment data from remote applications, and persists into central storage in this image. ProcessFabric-component is used to register or sync Pega Platform remote apps, while the external connector component is used for non-Pega remote applications. The Configurator persona is responsible for remote application registration. The User (Employee) persona has access to an interwoven worklist or Next Best Work (NBW). The Manager persona has access to insights.
 

The Pega Process Fabric Hub includes the following features:

  • Interwoven Worklist
  • Application Registry
  • Insights
  • Next Best Work

 For more information, see Process Fabric.


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

100% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice