Hi Jackie,

Thank you for the detailed response, we also use participant data and milestones for logs in architect call flows (inbound and in-queue), but you give me a good idea to combine them. Just wanted to clarify, when you add to participant data key-value pair like "Further.CustomerJourney038" - "ExitType=transferred", you set the participant data value hard-coded, or there is an option to choose an existing milestone as a variable for the participant data value?

However my original question was about Architect Workflow:

For workflows there is no option to set participant data, milestones or add audio prompts. 

The only way I found to debug a workflow, is to create common module with the workflow logic, test it using participant data in dummy inbound flow, then remove all participant data from it, and call this common module from the workflow. But this is time-consuming, complicated and not good for complex workflows, so I would like to find another way to debug workflows. Do you have any idea?

Thanks,

Hi Jackie,

Thank you for the detailed response, we also use participant data and milestones for logs in architect call flows (inbound and in-queue), but you give me a good idea to combine them. Just wanted to clarify, when you add to participant data key-value pair like "Further.CustomerJourney038" - "ExitType=transferred", you set the participant data value hard-coded, or there is an option to choose an existing milestone as a variable for the participant data value?

However my original question was about Architect Workflow:

For workflows there is no option to set participant data, milestones or add audio prompts. 

The only way I found to debug a workflow, is to create common module with the workflow logic, test it using participant data in dummy inbound flow, then remove all participant data from it, and call this common module from the workflow. But this is time-consuming, complicated and not good for complex workflows, so I would like to find another way to debug workflows. Do you have any idea?

Thanks,

"Further.CustomerJourneyxxx" - "key=value", which is logged we use two steps. We first perform a set participant data with the following:

Attribute Name 1
     Append("Further.CustomerJourney",
     If(Length(ToString(Flow.MilestoneCount))==1,Append("00",ToString(Flow.MilestoneCount)),
     If(Length(ToString(Flow.MilestoneCount))==2,Append("0",ToString(Flow.MilestoneCount)),
     ToString(Flow.MilestoneCount))))

Value to Assign 1... two options shown below: hard coding the key-value pair, OR hard code the key, but leveraging the flow variable for the value. The method we use is determined by what type of data we are needing to log.
     key=value or Append("CollectedSSN=",Flow.sSSN)... see below for examples of each

Example 1 - hard coded key-value pair

Example 2 - Leveraging a flow variable for the ssn

For step 2 of this process, we need to update the sequence number with a Update Data action:

Hope this makes sense and is helpful.

Concerning your question regarding debugging a workflow in Architect... I don't know. I haven't had to do that yet, as all of traffic is using inbound and secure flows, nothing more. Sorry I cannot be of help with workflows Irina.

Hi Jackie,

Thank you for the detailed response, we also use participant data and milestones for logs in architect call flows (inbound and in-queue), but you give me a good idea to combine them. Just wanted to clarify, when you add to participant data key-value pair like "Further.CustomerJourney038" - "ExitType=transferred", you set the participant data value hard-coded, or there is an option to choose an existing milestone as a variable for the participant data value?

However my original question was about Architect Workflow:

For workflows there is no option to set participant data, milestones or add audio prompts. 

The only way I found to debug a workflow, is to create common module with the workflow logic, test it using participant data in dummy inbound flow, then remove all participant data from it, and call this common module from the workflow. But this is time-consuming, complicated and not good for complex workflows, so I would like to find another way to debug workflows. Do you have any idea?

Thanks,