Hi Niel,
I followed the same thing as suggested by you but somehow it is not working as expected , don't know if something is missing attaching screen shot below, could you please have a look and see if I am missing anything.
{
"flowId": "c6edd3d6-0fbb-443e-aada-1c2e14f5a52c",
"flowVersion": "",
"inputData": {
"callback": {
"Flow.interactionType": "Outbound",
"Flow.callResult": "Success"
}
}
}
Below is the JSON response:
{
"flowVersion.inputSchema.definitions.archString.oneOf.type": [
"null",
"string"
],
"flowVersion.inputSchema.description": "Schema defining flow input parameters. Property names map to flow scoped variables marked as a flow input. If you do not supply a property value for an input variable, the variable value will be set to the initial value configured on it in the flow at flow startup.",
"flowVersion.dateSaved": 1725262308609,
"flowVersion.generationId": "WORKFLOW_VERSION_PUBLISHED",
"flowVersion.supportedLanguages.isDefault": [
true
],
"flowVersion.supportedLanguages.language": [
"en-us"
],
"completionReason": "Success",
"flowVersion.inputSchema.definitions.archString.oneOf.description": [
"A NOT_SET String value.",
"A character string. Examples: \"\", \"Hello\", \"Just say \\\"No!\\\"\""
],
"flowVersion.name": "2.0",
"dateCompleted": "2024-09-02T16:10:15.026Z",
"flowVersion.outputSchema.$schema": "http://json-schema.org/draft-07/schema#",
------------------------------
Ashish Kumar Sinha
Cognizant Technology Solutions India Private Limited
------------------------------
Original Message:
Sent: 08-30-2024 10:26
From: Ashish Kumar Sinha
Subject: Workflow API
Thanks for the response !
I am directly using data action to invoke Workflow.
Will follow these steps and test it out.
------------------------------
Ashish Kumar Sinha
Cognizant Technology Solutions India Private Limited
Original Message:
Sent: 08-30-2024 09:06
From: Niel Vicente
Subject: Workflow API
Hi Ashish,
Are you calling the API directly from postman or via data action in an architect flow?
From postman, you can just put the variables directly without the 'input." prefix and then flatten the inputData attributes.
Test with hard-coded data first to test if data is getting pushed to workflow.
In Architect, ensure these flow variables are created and marked as input to flow:
Then in your workflow, do a simple update data where you assign above flow variables to task variables before ending the workflow. Check workflow execution replay and verify the attributes are passed.
Your formatting above is intended for a data action where you are passing architect variables as input.
------------------------------
Niel Vicente
DAMAC Properties Co. LLC
Original Message:
Sent: 08-30-2024 07:44
From: Ashish Kumar Sinha
Subject: Workflow API
Thanks Niel, for the quick response with the above suggestion.
I tried same way and passed the variables in the api as suggested by you and referenced these variables as input and out variable in the Workflow but still I am getting some error:
"flowVersion.inputSchema.properties.Flow__scheduleStatus.$ref": "#/definitions/archString",
"flowVersion.outputSchema.properties.Flow__scheduleType.$ref": "#/definitions/archString",
"flowVersion.inputSchema.description": "Schema defining flow input parameters. Property names map to flow scoped variables marked as a flow input. If you do not supply a property value for an input variable, the variable value will be set to the initial value configured on it in the flow at flow startup.
Could you please suggest if I am missing something.
------------------------------
Ashish Kumar Sinha
Cognizant Technology Solutions India Private Limited
Original Message:
Sent: 08-30-2024 06:07
From: Niel Vicente
Subject: Workflow API
Hi Ashish,
I recommend flattening your attributes. You can declare and reference them directly as Flow variables:
------------------------------
Niel Vicente
DAMAC Properties Co. LLC
Original Message:
Sent: 08-30-2024 05:32
From: Ashish Kumar Sinha
Subject: Workflow API
Hi All,
Currently I am invoking Workflow through api : /api/v2/flows/executions with the below request body to pass some value and it is successfully invoked as per the response.
{
"flowId": "${input.flowId}",
"inputData": {
"Callback": {
"interactionType": "${input.interactionType}",
"callResult": "${input.callResult}"
}
},
"name": "${input.name}"
}
Now I want to retrieve this data in my Workflow to use in some other logic but not sure how to do that.
Have anyone implemented the similar logics, please let me know how this can be done.
#API/Integrations
------------------------------
Ashish Kumar Sinha
------------------------------