Setting up trigger

[alex7]

I saw the admin tool under Architect to create triggers. I can't seem to find documentation or examples of how this works.

If I'm using the topic v2.detail.events.conversation.{id}.acd.end, and I want the trigger to be on the condition of the queueId to be equal to a particular queue, and the acdOutcome to be "ANSWERED", how do I put that in the value?

[zubair]

Just add values without quotes i.e. ANSWERED for acdOutcome and id of queue for the queueId

[alex7]

Thanks.... then I was doing it right. Something else isn't working then.

[alex7]

Here's my trigger:

It calls a workflow that takes the conversationId, participantId, and answeredUserId, and calls a data action that adds answeredUserId to the participant data, keyed by 'agentId'

I'm not seeing this happening when the agent answers the inbound message.

There is a "Save and Test" option of the trigger, but I'm not exactly sure how to do that either. Sorry, I'm new to this.

Can someone help me how to troubleshoot this? Since there are two parts to this: trigger and the workflow. And if it is relavant, it is for a Message.

[SimonBrown]

Will be in your workflow then.
You need to ensure the schema fields you need are created and marked as INPUT to flow to see and use them.
Make sure case correct as well otherwise fails.

In the workflows I tend to add debug participant blocks at each stage as debugging flows is not simple.

Unfortunately Genesys released this UI update without the option to call workflow with a single JSON variable, and then use that JSON collection to pick out any of the schema fields through json path statements.

workflowTargetSettings allows you to set a dataFormat to select how matching events are passed to your workflow.

• TopLevelPrimitives: The top level primitive fields (strings, enums, numbers, and booleans) of the event are sent to the workflow. Example
• Json: The entire event is sent to the workflow as a JSON object. Example

For more information about creating and managing workflows, see Work with workflows in Genesys Cloud Resource Center.

I assume you have looked at Triggers Info

[alex7]

I found out on another thread that the triggers don't work when using SSO. And that's what is happening for me.