Hello,
I think this is because of your use of tuple in your output contract (which is maybe not what you wanted to do/achieve - or it can be done differently).
I mean that you have defined an array with a single tuple type inside (the object with id and name properties).
I would tend to think this is also why it is not showing in the Workflow Call Data Action - the flow probably not being able to flatten that object (as flow doesn't manage an output property of type object). Definition of tuple is specific and may not have been totally managed in the flow.
To define the array tuple, the string/integer/... tuple types would be directly below the "Tuple" toggle button - a first type for an integer, a second type for a string, ...
This is to define an array (ordered list) containing elements of different types.
What you could do instead is to have something like this in your output contract:
{
"type": "object",
"properties": {
"presence": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"name": {
"type": "string"
}
}
}
}
}
Using a response configuration like this (assuming you just want to retrieve one system presence):
{
"translationMap": {
"presence": "$[?(@.name == \"ON_QUEUE\")]"
},
"translationMapDefaults": {
"presence": "[]"
},
"successTemplate": "{ \"presence\": ${successTemplateUtils.firstFromArray(\"${presence}\", \"{}\")} }"
}
Regards,
------------------------------
Jerome Saint-Marc
Senior Development Support Engineer
------------------------------