POST /associations/batch

Each batch request can contain up to 50 request items.

The Publish Associations in Batch REST API is optional. Once data sync of all the resource types (which is tasks, work queues, and operator mappings), is complete, the registration automatically moves to the active state and the application that you register is ready for use in Pega Process Fabric.

The following table shows a sample request body for the batch endpoint for associations:

{ 
  "requests": [ 
    { 
      "body": { 
        "fromType": "case", 
        "fromID": "EPIC-123", 
        "toID": "begua", 
        "toType": "operator", 
        "action": "create", 
        "category": "Follower",
        “createDateTime”: “20220223T002801.893 GMT”,
        “createOperator”: “0055g000004ccPCAAY”,
        "updateOperator": "0055g000004ccPCATL",
        "updateDateTime": "20210226T061742.441 GMT", 
        "ID": "EPIC-123!begua!Follower" 
      }, 
      "method": "PUT" 
    }, 
    { 
      "body": { 
        "fromType": "case", 
        "fromID": "kYC-123", 
        "toID": "begua", 
        "toType": "operator", 
        "action": "update", 
        "category": "Interested Party",
        “createDateTime”: “20220223T002801.893 GMT”,
        “createOperator”: “0055g000004ccPCAAY”,
        "updateOperator": "0055g000004ccPCATL",
        "updateDateTime": "20210226T061742.441 GMT", 
        "ID": "kYC-123!begua!Approver" 
      }, 
      "method": "PUT" 
    } 
  ] 
}

After you publish all the existing associations, invoke the Publish Associations in Batch REST API with the preactivationDataLast query string parameter set to true with no request body. Invoking this request informs Pega Process Fabric Hub that the associations sync is complete. For example, the following table shows information about the endpoint that you invoke to inform Pega Process Fabric Hub that the application has published all the associations data:

For more information, see the Swagger documentation and Accessing and testing Pega DX API Version 1.