Skip to main content


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

Manually deleting the connection between the Pega Process Fabric Hub and a remote application

Updated on June 15, 2021

To manage resources and facilitate routing assignments, delete a remote application from the Pega Process Fabric Hub even when you cannot access this action from the application life cycle.

For example, when your remote application no longer pertains to your business scenario, to stop publishing data from the remote application to the Pega Process Fabric Hub, delete the application from the Pega Process Fabric Hub.
Before you begin: Obtain a PPF:Administrators access group to delete applications from the Pega Process Fabric Hub. For more information, see Defining operator contact information and application access and Access groups associated with personas in the Pega Process Fabric Hub.

As a best practice, to delete an application, manage the application life cycle. However, for specific scenarios the ability to delete an application through the application life cycle is unavailable. One example is when queue processors that correspond to the Pega Process Fabric Hub have invalid configuration. As a result, you might not be able to change the application status from Sync-InProgress. In such situations, manually delete the connection, first on the Pega Process Fabric Hub side, and then in the remote application. The connection stops working when you delete the rules that the Pega Process Fabric Hub saved in the remote application.

Deleting the connection on the Pega Process Fabric Hub side

To manually disconnect your remote application from the Pega Process Fabric Hub, first delete the remote application registration from your instance of the Pega Process Fabric Hub.

  1. Log in to Dev Studio as an administrator persona to manage the Pega Process Fabric Hub application.
  2. In the navigation pane of Dev Studio, click Records.
  3. Expand the Technical category, and then click Activity.
  4. In the list of instances, open the DeleteRecord instance that applies to PPF-Work-Registration class, as shown in the following figure:
    DeleteRecord instance
    A list of activities with a DeleteRecord instance
  5. In the rule form header, click ActionsRun.
  6. In the Run Activity: DeleteRecord window, in the Parameter Value section, in the ID field, enter the ID of the application registration that you want to delete, for example, REG-24059.
    Note: Ensure that you enter the correct registration ID. If you delete data from another application, you cannot undo the deletion.
  7. Click Run.
    Result: A pop-up window displays the results.
  8. Optional: To confirm that the activity ran, verify the status of the registration:
    1. In the navigation pane of Dev Studio, click App.
    2. On the Classes tab, click PPF-Work-Registration.
    3. In the list of application registration instances, find the application that you want to delete from the Pega Process Fabric Hub, and then check the value in the Work Status column.
      For example: The status of Resolved-Withdrawn indicates that you deleted the connection to the remote application on the Pega Process Fabric Hub side, as shown in the following figure:
      Deleted application registration
      A list of application registration instances with a deleted application

Deleting the connection on the remote application side

To complete the process of manually deleting a remote application from the Pega Process Fabric Hub, delete the rules that the Pega Process Fabric Hub created in your remote application.

  1. Log in to Dev Studio as an administrator or configurator persona to manage the remote application.
  2. In the header of Dev Studio, click the name of the application, and then click Definition.
  3. On the Definition tab, in the Application rulesets section, click Open next to the top ruleset in the list.
    Typically, the Pega Process Fabric Hub uses the first ruleset in the application rulesets list to save rules. If your instance of the Pega Process Fabric Hub saves rules in another ruleset, ensure that you first open the correct ruleset.
  4. On the Versions tab, click the rule count in the All rules column, as in the following figure:
    Opening application rules
    Versions tab of a ruleset that belong to a remote application
  5. In the Rule name column, click Click to filter, and then in the dialog box, in the Search Text field, enter pyPF and click Apply, as in the following figure:
    Searching for Pega Process Fabric Hub rules
    Application rules with a dialog box to search for rules that correspond to the Pega Process Fabric Hub
    Result: The results display rules that correspond to the Pega Process Fabric Hub.
  6. Delete rules in the list:
    1. Click a rule instance.
    2. In the rule form header, click Delete.
    3. In the Delete dialog box, in the Reason for deletion field, explain why you delete the rule.
      For example: Enter Deleting connection with the Pega Process Fabric Hub.
    4. Click Delete.
    5. Repeat steps 6.a through 6.d for other rules that correspond to the Pega Process Fabric Hub.
  7. Optional: To save database resources, you can delete other records that correspond to the Pega Process Fabric Hub, such as OAuth 2.0 client registration or an authentication profile.
    For more information, see Deleting a rule.
  • Previous topic Managing applications in the Pega Process Fabric Hub
  • Next topic Viewing error logs in the Pega Process Fabric Hub

Related articles

Registering applications in the Pega Process Fabric HubProviding access rights for the Pega Process Fabric Hub by editing a service packageCustom connectors for the Pega Process Fabric Hub

Tags

Pega Process Fabric Hub 1.0 Case Management

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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