Skip to main content


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

Custom connectors for the Pega Process Fabric Hub

Updated on November 9, 2021

The Pega Process Fabric Hub is an application that consolidates assignments from multiple distributed applications, in order to speed up work processing and provide a comprehensive overview of the workflows in your organization. To incorporate non-Pega applications into centralized work processing, you can implement custom connectors to create communication with the Pega Process Fabric Hub.

The Pega Process Fabric Hub uses open APIs to collect assignment data from distributed applications. The Pega Process Fabric Hub then implements the collected information across unified worklists and work queues, the Next Best Work algorithm, and reports that users with managerial roles can view in the Pega Process Fabric Hub Insights. When you create a connection between the Pega Process Fabric Hub and an application that you build on Pega Platform version 8.1 or later, you use the default Pega Process Fabric Hub connector. For your non-Pega applications, implement the Pega Process Fabric Hub APIs and publish the data.

You can connect your non-Pega application to the Pega Process Fabric Hub provided that the remote application supports invoking the Pega Process Fabric Hub APIs to publish the assignment data. The Pega Process Fabric Hub utilizes the following APIs:

Registration APIs
Use the registration APIs to create a connection between your remote application and the Pega Process Fabric Hub, and then manage the application life cycle, for example, to resynchronize the application or delete the connection between your application and the Pega Process Fabric Hub.
Data synchronization APIs
Use the data synchronization APIs to sync assignment data from your remote applications with the Pega Process Fabric Hub.

The following figure describes the communication between the Pega Process Fabric Hub and remote applications. Applications that you deploy on Pega Platform use the Pega Process Fabric Hub connector, while third-party applications use the Pega Process Fabric Hub APIs:

Communication between the Pega Process Fabric Hub and remote applications
A diagram that presents how the Pega Process Fabric Hub communicates with Pega and non-Pega applications

Note: As a best practice, use custom connectors only for non-Pega applications. For applications that you build on Pega Platform, download the Pega Process Fabric Hub connector component from the Pega Marketplace. For more information, see Process Fabric Connector for Pega Platform.

Requirements for applications that you connect to the Pega Process Fabric Hub

Before you connect your third-party application to the Pega Process Fabric Hub, ensure that your application meets the following requirements:

  • The Pega Process Fabric Hub accepts assignment metadata that the registered remote applications publish by using REST APIs. Ensure that the remote application can pass assignment metadata by invoking the Pega Process Fabric Hub APIs, either through itself or through an intermediate logic, which is a connector.
  • Ensure that the operator ID for specific users is identical across all registered applications, including the Pega Process Fabric Hub.
  • Ensure that your remote application publishes the data of assignments that can be processed by users in your organization who have access to the application. Avoid publishing the data of assignments that users cannot process for any reason.
  • Communication models of remote applications and the Pega Process Fabric Hub

    Work management in the Pega Process Fabric Hub is possible because of data publication from a remote application. When you host your instance of the Pega Process Fabric Hub on Pega Cloud, the communication schema depends on the deployment of your remote application.

  • Application registration life cycle for third-party applications

    Application registration is a process of configuring a remote application to connect to the Pega Process Fabric Hub. You can register applications that you build on Pega Platform version 8.1 and later by using a designated portal in the Pega Process Fabric Hub. To incorporate non-Pega applications into your case processing and to resolve more cases faster, register your non-Pega application with the Pega Process Fabric Hub by using REST APIs.

  • Registration APIs for the Pega Process Fabric Hub

    Registration REST APIs help you manage your application life cycle in the Pega Process Fabric Hub. By calling relevant endpoints, you can register your remote application with the Pega Process Fabric Hub, and then manage the application in a way that meets your unique business needs.

  • Data Synchronization APIs for the Pega Process Fabric Hub

    The Pega Process Fabric Hub accepts data that a remote application publishes by invoking the Pega Process Fabric Hub Data Synchronization APIs. For example, a remote application can publish information about open assignments and operators.

  • Deployment models for connectors

    Connectors fetch data from your remote application to publish this data to the Pega Process Fabric Hub. For example, by using connectors, you can publish assignment data from your application to the Pega Process Fabric Hub. Before you deploy connectors, consider which deployment model suits best your scenario.

  • Previous topic Pega Process Fabric Hub Insights
  • Next topic Communication models of remote applications and 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