Reltio Connect

 View Only
  • 1.  DCR Submitted Through API Not Present in Inbox

    Reltio Partner
    Posted 03-02-2022 13:01
    Hi Reltio Community!

    I'm testing DCR submission through API, and facing this initial problem:
    I'm using the "entities" API to create an Entity. I'm submitting a "POST {TenantURL}/entities" request.
    I've added parameter "alwaysCreateDCR" set to True, and in fact apparently the DCR is being created. Here is the response which I'm getting:

    {
    "uri": "changeRequests/33wUHVdj",
    "createdBy": "mfruscella",
    "createdTime": 1646243922208,
    "updatedBy": "mfruscella",
    "updatedTime": 1646243922208,
    "type": "configuration/changeRequestTypes/default",
    "state": "AWAITING_REVIEW"
    }

    The problem is that I don't get any DCR in the Inbox. My Inbox is empty.
    If, instead, I create the same new Entity from the UI, in "Suggesting" mode, the DCR is created and visible in the Inbox.

    What am I missing?

    Thank you in advance.
    Regards,

    Michele


  • 2.  RE: DCR Submitted Through API Not Present in Inbox

    Reltio Employee
    Posted 03-03-2022 13:47
    Hello Michele, 

    Interesting question! 

    Let's review the API call first: 
    For POST ../entities call: 
    a.  DCR is created in two cases only: 1) there is a changeRequestId parameter, and 2) there are no CREATE and UPDATE privileges for all incoming entities, but there are READ and INITIATE_CHANGE_REQUEST for all of them. In this true in the scenario where alwaysCreateDCR is set to True
    b. confirm if preserve hidden is specified,
    • preserveHidden: if specified, the API does not create a DCR to delete hidden attributes if they are not specified in the request.

    Secondly, since you are able to create a DCR in the UI, you can capture the API call and the parameters from the UI --> Developer mode and replay from Postman. This should highlight any incorrect parameters that you are using currently. 

    Please let me know if this helps. Find below the documentation links for reference:
    https://docs.reltio.com/search.html?searchQuery=create+dcr
    https://docs.reltio.com/workflow/workflow.html

    Thanks,
    Shantanu



  • 3.  RE: DCR Submitted Through API Not Present in Inbox

    Reltio Employee
    Posted 03-04-2022 00:39
    Hi Michele,

    creating DCR object is not enough to see workflow tasks in the Inbox. You also need to start related DCR workflow process using the API https://docs.reltio.com/workflowapi/startprocessinstance.html
    F.e. if your tenant is AABBCCDDEE on 361.reltio.com environment your request will look like:

    curl --location --request POST 'https://prod-workflow.reltio.com/workflow-adapter/workflow/AABBCCDDEE/processInstances' \
    --header 'Authorization: Bearer ***' \
    --header 'Content-Type: application/json' \
    --header 'EnvironmentURL: https://361.reltio.com' \
    --data-raw '{
        "processType""dataChangeRequestReview",
        "objectURIs": [
            "changeRequests/33wUHVdj",   <-- your change request ID
            "entities/1HGY4n5" <-- entity id which the DCR was created for (if it is existing entity)
       ]
    }'

    This API will start DCR workflow process and create a task that will be displayed in the Inbox.

    Regards,
    Yury.


  • 4.  RE: DCR Submitted Through API Not Present in Inbox

    Reltio Employee
    Posted 12-07-2023 08:36

    The link is updated now. Below is the latest one:

    https://docs.reltio.com/en/explore/get-going-with-apis-and-rocs-utilities/reltio-rest-apis/engage-apis/workflow-api/start-a-process-instance



    ------------------------------
    Piyush Sharma
    ------------------------------