Genesys Cloud - Developer Community!

Dear Genesys Developer Community,

I hope you are doing well.

I am reaching out to seek guidance on an issue I am encountering while attempting to retrieve dynamic objects from a Data Action within a workflow/Architect flow. Below are the steps I have followed:

Steps Taken:

1. Created a Data Action to retrieve contact information using contactID and contactListID. The Data Action is designed to fetch details from a contact list in an object format.

2. Defined ContactData as an object in the contracts output section to store the retrieved contact details.

3. Used the following schema to structure the output:

   {

     "translationMap": {

       "contactData": "$.data"

     },

     "translationMapDefaults": {

       "contactData": "UNKNOWN"

     },

     "successTemplate": "{\r\n  \"contactData\": ${contactData} \r\n}"

   }

4. Successfully retrieved the entire data object inside the raw result, storing it in the ContactData object.

5. Saved and published the Data Action.

6. Invoked the Data Action inside a workflow/Architect flow, but the output section is not display.

Issue:

• The Data Action does not return the expected dynamic object when used inside the workflow.

• I intend to reuse this Data Action to dynamically fetch contact details, but currently, it only shows the input contact.

Request for Assistance:

Has anyone encountered a similar issue? How can I ensure that the Data Action correctly returns the dynamic object inside the workflow? Any suggestions or best practices would be greatly appreciated.

I appreciate your time and support and look forward to your insights.

Architect requires that there be an output contract with specific data types.  If the output response is dynamic the I suggest you have a single "string" returned in your output contract. In your data action take the existing response and json escape it. Then in architect you can unescape that string into JSON and work with it as JSON.

Dear Genesys Developer Community,

I hope you are doing well.

I am reaching out to seek guidance on an issue I am encountering while attempting to retrieve dynamic objects from a Data Action within a workflow/Architect flow. Below are the steps I have followed:

Steps Taken:

1. Created a Data Action to retrieve contact information using contactID and contactListID. The Data Action is designed to fetch details from a contact list in an object format.

2. Defined ContactData as an object in the contracts output section to store the retrieved contact details.

3. Used the following schema to structure the output:

   {

     "translationMap": {

       "contactData": "$.data"

     },

     "translationMapDefaults": {

       "contactData": "UNKNOWN"

     },

     "successTemplate": "{\r\n  \"contactData\": ${contactData} \r\n}"

   }

4. Successfully retrieved the entire data object inside the raw result, storing it in the ContactData object.

5. Saved and published the Data Action.

6. Invoked the Data Action inside a workflow/Architect flow, but the output section is not display.

Issue:

• The Data Action does not return the expected dynamic object when used inside the workflow.

• I intend to reuse this Data Action to dynamically fetch contact details, but currently, it only shows the input contact.

Request for Assistance:

Has anyone encountered a similar issue? How can I ensure that the Data Action correctly returns the dynamic object inside the workflow? Any suggestions or best practices would be greatly appreciated.

I appreciate your time and support and look forward to your insights.

Architect requires that there be an output contract with specific data types.  If the output response is dynamic the I suggest you have a single "string" returned in your output contract. In your data action take the existing response and json escape it. Then in architect you can unescape that string into JSON and work with it as JSON.

Dear Genesys Developer Community,

I hope you are doing well.

I am reaching out to seek guidance on an issue I am encountering while attempting to retrieve dynamic objects from a Data Action within a workflow/Architect flow. Below are the steps I have followed:

Steps Taken:

1. Created a Data Action to retrieve contact information using contactID and contactListID. The Data Action is designed to fetch details from a contact list in an object format.

2. Defined ContactData as an object in the contracts output section to store the retrieved contact details.

3. Used the following schema to structure the output:

   {

     "translationMap": {

       "contactData": "$.data"

     },

     "translationMapDefaults": {

       "contactData": "UNKNOWN"

     },

     "successTemplate": "{\r\n  \"contactData\": ${contactData} \r\n}"

   }

4. Successfully retrieved the entire data object inside the raw result, storing it in the ContactData object.

5. Saved and published the Data Action.

6. Invoked the Data Action inside a workflow/Architect flow, but the output section is not display.

Issue:

• The Data Action does not return the expected dynamic object when used inside the workflow.

• I intend to reuse this Data Action to dynamically fetch contact details, but currently, it only shows the input contact.

Request for Assistance:

Has anyone encountered a similar issue? How can I ensure that the Data Action correctly returns the dynamic object inside the workflow? Any suggestions or best practices would be greatly appreciated.

I appreciate your time and support and look forward to your insights.

Hi Jason Mathison,

If I set the ContactData as a String type in the contracts section, I am unable to store the entire object inside ContactData. My intention is to store the entire data object and use it from Architect.

Could you suggest an approach to achieve this while ensuring the full object is retained?

Architect requires that there be an output contract with specific data types.  If the output response is dynamic the I suggest you have a single "string" returned in your output contract. In your data action take the existing response and json escape it. Then in architect you can unescape that string into JSON and work with it as JSON.

Dear Genesys Developer Community,

I hope you are doing well.

I am reaching out to seek guidance on an issue I am encountering while attempting to retrieve dynamic objects from a Data Action within a workflow/Architect flow. Below are the steps I have followed:

Steps Taken:

1. Created a Data Action to retrieve contact information using contactID and contactListID. The Data Action is designed to fetch details from a contact list in an object format.

2. Defined ContactData as an object in the contracts output section to store the retrieved contact details.

3. Used the following schema to structure the output:

   {

     "translationMap": {

       "contactData": "$.data"

     },

     "translationMapDefaults": {

       "contactData": "UNKNOWN"

     },

     "successTemplate": "{\r\n  \"contactData\": ${contactData} \r\n}"

   }

4. Successfully retrieved the entire data object inside the raw result, storing it in the ContactData object.

5. Saved and published the Data Action.

6. Invoked the Data Action inside a workflow/Architect flow, but the output section is not display.

Issue:

• The Data Action does not return the expected dynamic object when used inside the workflow.

• I intend to reuse this Data Action to dynamically fetch contact details, but currently, it only shows the input contact.

Request for Assistance:

Has anyone encountered a similar issue? How can I ensure that the Data Action correctly returns the dynamic object inside the workflow? Any suggestions or best practices would be greatly appreciated.

I appreciate your time and support and look forward to your insights.

You can use this macro to convert the JSON object into a string:

$esc.jsonEncode(): Use this method to escape JSON's reserved characters in the output. It allows JSON to be stored in a string form.

https://help.mypurecloud.com/articles/velocity-macros-data-actions/

Hi Jason Mathison,

If I set the ContactData as a String type in the contracts section, I am unable to store the entire object inside ContactData. My intention is to store the entire data object and use it from Architect.

Could you suggest an approach to achieve this while ensuring the full object is retained?

Architect requires that there be an output contract with specific data types.  If the output response is dynamic the I suggest you have a single "string" returned in your output contract. In your data action take the existing response and json escape it. Then in architect you can unescape that string into JSON and work with it as JSON.

Dear Genesys Developer Community,

I hope you are doing well.

I am reaching out to seek guidance on an issue I am encountering while attempting to retrieve dynamic objects from a Data Action within a workflow/Architect flow. Below are the steps I have followed:

Steps Taken:

1. Created a Data Action to retrieve contact information using contactID and contactListID. The Data Action is designed to fetch details from a contact list in an object format.

2. Defined ContactData as an object in the contracts output section to store the retrieved contact details.

3. Used the following schema to structure the output:

   {

     "translationMap": {

       "contactData": "$.data"

     },

     "translationMapDefaults": {

       "contactData": "UNKNOWN"

     },

     "successTemplate": "{\r\n  \"contactData\": ${contactData} \r\n}"

   }

4. Successfully retrieved the entire data object inside the raw result, storing it in the ContactData object.

5. Saved and published the Data Action.

6. Invoked the Data Action inside a workflow/Architect flow, but the output section is not display.

Issue:

• The Data Action does not return the expected dynamic object when used inside the workflow.

• I intend to reuse this Data Action to dynamically fetch contact details, but currently, it only shows the input contact.

Request for Assistance:

Has anyone encountered a similar issue? How can I ensure that the Data Action correctly returns the dynamic object inside the workflow? Any suggestions or best practices would be greatly appreciated.

I appreciate your time and support and look forward to your insights.

Hi Jason Mathison,

If I set the ContactData as a String type in the contracts section, I am unable to store the entire object inside ContactData. My intention is to store the entire data object and use it from Architect.

Could you suggest an approach to achieve this while ensuring the full object is retained?

Architect requires that there be an output contract with specific data types.  If the output response is dynamic the I suggest you have a single "string" returned in your output contract. In your data action take the existing response and json escape it. Then in architect you can unescape that string into JSON and work with it as JSON.

Dear Genesys Developer Community,

I hope you are doing well.

I am reaching out to seek guidance on an issue I am encountering while attempting to retrieve dynamic objects from a Data Action within a workflow/Architect flow. Below are the steps I have followed:

Steps Taken:

1. Created a Data Action to retrieve contact information using contactID and contactListID. The Data Action is designed to fetch details from a contact list in an object format.

2. Defined ContactData as an object in the contracts output section to store the retrieved contact details.

3. Used the following schema to structure the output:

   {

     "translationMap": {

       "contactData": "$.data"

     },

     "translationMapDefaults": {

       "contactData": "UNKNOWN"

     },

     "successTemplate": "{\r\n  \"contactData\": ${contactData} \r\n}"

   }

4. Successfully retrieved the entire data object inside the raw result, storing it in the ContactData object.

5. Saved and published the Data Action.

6. Invoked the Data Action inside a workflow/Architect flow, but the output section is not display.

Issue:

• The Data Action does not return the expected dynamic object when used inside the workflow.

• I intend to reuse this Data Action to dynamically fetch contact details, but currently, it only shows the input contact.

Request for Assistance:

Has anyone encountered a similar issue? How can I ensure that the Data Action correctly returns the dynamic object inside the workflow? Any suggestions or best practices would be greatly appreciated.

I appreciate your time and support and look forward to your insights.

Great.

Hi Jason Mathison,

If I set the ContactData as a String type in the contracts section, I am unable to store the entire object inside ContactData. My intention is to store the entire data object and use it from Architect.

Could you suggest an approach to achieve this while ensuring the full object is retained?

Architect requires that there be an output contract with specific data types.  If the output response is dynamic the I suggest you have a single "string" returned in your output contract. In your data action take the existing response and json escape it. Then in architect you can unescape that string into JSON and work with it as JSON.

Dear Genesys Developer Community,

I hope you are doing well.

I am reaching out to seek guidance on an issue I am encountering while attempting to retrieve dynamic objects from a Data Action within a workflow/Architect flow. Below are the steps I have followed:

Steps Taken:

1. Created a Data Action to retrieve contact information using contactID and contactListID. The Data Action is designed to fetch details from a contact list in an object format.

2. Defined ContactData as an object in the contracts output section to store the retrieved contact details.

3. Used the following schema to structure the output:

   {

     "translationMap": {

       "contactData": "$.data"

     },

     "translationMapDefaults": {

       "contactData": "UNKNOWN"

     },

     "successTemplate": "{\r\n  \"contactData\": ${contactData} \r\n}"

   }

4. Successfully retrieved the entire data object inside the raw result, storing it in the ContactData object.

5. Saved and published the Data Action.

6. Invoked the Data Action inside a workflow/Architect flow, but the output section is not display.

Issue:

• The Data Action does not return the expected dynamic object when used inside the workflow.

• I intend to reuse this Data Action to dynamically fetch contact details, but currently, it only shows the input contact.

Request for Assistance:

Has anyone encountered a similar issue? How can I ensure that the Data Action correctly returns the dynamic object inside the workflow? Any suggestions or best practices would be greatly appreciated.

I appreciate your time and support and look forward to your insights.

I am trying a similar data-action but something not working.
I run the get-conversation API in data-action and want to convert all the results into architect where i can then process it as JSON, but I surely am missing something. Any help would be really appreciated.

Input: /api/v2/conversations/calls/${input.ConversationID}

Output: JSONString (type string)
Data Action Response : 

Great.

Hi Jason Mathison,

If I set the ContactData as a String type in the contracts section, I am unable to store the entire object inside ContactData. My intention is to store the entire data object and use it from Architect.

Could you suggest an approach to achieve this while ensuring the full object is retained?

Architect requires that there be an output contract with specific data types.  If the output response is dynamic the I suggest you have a single "string" returned in your output contract. In your data action take the existing response and json escape it. Then in architect you can unescape that string into JSON and work with it as JSON.

Dear Genesys Developer Community,

I hope you are doing well.

I am reaching out to seek guidance on an issue I am encountering while attempting to retrieve dynamic objects from a Data Action within a workflow/Architect flow. Below are the steps I have followed:

Steps Taken:

1. Created a Data Action to retrieve contact information using contactID and contactListID. The Data Action is designed to fetch details from a contact list in an object format.

2. Defined ContactData as an object in the contracts output section to store the retrieved contact details.

3. Used the following schema to structure the output:

   {

     "translationMap": {

       "contactData": "$.data"

     },

     "translationMapDefaults": {

       "contactData": "UNKNOWN"

     },

     "successTemplate": "{\r\n  \"contactData\": ${contactData} \r\n}"

   }

4. Successfully retrieved the entire data object inside the raw result, storing it in the ContactData object.

5. Saved and published the Data Action.

6. Invoked the Data Action inside a workflow/Architect flow, but the output section is not display.

Issue:

• The Data Action does not return the expected dynamic object when used inside the workflow.

• I intend to reuse this Data Action to dynamically fetch contact details, but currently, it only shows the input contact.

Request for Assistance:

Has anyone encountered a similar issue? How can I ensure that the Data Action correctly returns the dynamic object inside the workflow? Any suggestions or best practices would be greatly appreciated.

I appreciate your time and support and look forward to your insights.

Looks like thissuccessTemplate": "{\"JSONString\": $esc.jsonEncode(${rawResult}) }"might need escaped quotes around the encoded JSON like this:successTemplate": "{\"JSONString\": \"$esc.jsonEncode(${rawResult})\" }"

I am trying a similar data-action but something not working.
I run the get-conversation API in data-action and want to convert all the results into architect where i can then process it as JSON, but I surely am missing something. Any help would be really appreciated.

Input: /api/v2/conversations/calls/${input.ConversationID}

Output: JSONString (type string)
Data Action Response : 

Great.

Hi Jason Mathison,

If I set the ContactData as a String type in the contracts section, I am unable to store the entire object inside ContactData. My intention is to store the entire data object and use it from Architect.

Could you suggest an approach to achieve this while ensuring the full object is retained?

Architect requires that there be an output contract with specific data types.  If the output response is dynamic the I suggest you have a single "string" returned in your output contract. In your data action take the existing response and json escape it. Then in architect you can unescape that string into JSON and work with it as JSON.

Dear Genesys Developer Community,

I hope you are doing well.

I am reaching out to seek guidance on an issue I am encountering while attempting to retrieve dynamic objects from a Data Action within a workflow/Architect flow. Below are the steps I have followed:

Steps Taken:

1. Created a Data Action to retrieve contact information using contactID and contactListID. The Data Action is designed to fetch details from a contact list in an object format.

2. Defined ContactData as an object in the contracts output section to store the retrieved contact details.

3. Used the following schema to structure the output:

   {

     "translationMap": {

       "contactData": "$.data"

     },

     "translationMapDefaults": {

       "contactData": "UNKNOWN"

     },

     "successTemplate": "{\r\n  \"contactData\": ${contactData} \r\n}"

   }

4. Successfully retrieved the entire data object inside the raw result, storing it in the ContactData object.

5. Saved and published the Data Action.

6. Invoked the Data Action inside a workflow/Architect flow, but the output section is not display.

Issue:

• The Data Action does not return the expected dynamic object when used inside the workflow.

• I intend to reuse this Data Action to dynamically fetch contact details, but currently, it only shows the input contact.

Request for Assistance:

Has anyone encountered a similar issue? How can I ensure that the Data Action correctly returns the dynamic object inside the workflow? Any suggestions or best practices would be greatly appreciated.

I appreciate your time and support and look forward to your insights.