Message |
[+]
Engagement Designer
» ED call flow ends with error, 18/09/2018 20:13:00
» Go to message
|
|
Hi Yidi
When you hover over the error terminate event, what does it say? Your workflow has finished correctly. Can you double check the logs?
|
|
[+]
Engagement Designer
» Multiple Call Intercept WorkFlows, 12/07/2018 02:05:56
» Go to message
|
|
In 3.4, you can design a workflow to intercept the calls and then have the sequence of WorkFlows invoked from this parent flow.
|
|
[+]
Engagement Designer
» Paly and Collect not passing digits to Gateway, 13/05/2018 00:34:06
» Go to message
|
|
Good to hear. Even 3.2 should have worked too - happy that you are out of the woods. Happy modeling !
|
|
[+]
Engagement Designer
» Designer Console URL looping back to SMGR login then get error of too many redirects, 02/05/2018 23:15:25
» Go to message
|
|
Note from Breeze install guide: The Avaya Breeze™ node where Engagement Designer is installed and System Manager must be in the same domain.
|
|
[+]
Engagement Designer
» Invoke engagement designer application from Avaya Experience portal, 23/03/2018 10:49:00
» Go to message
|
|
|
|
[+]
Engagement Designer
» Invoke engagement designer application from Avaya Experience portal, 22/03/2018 11:09:35
» Go to message
|
|
Rangari - can you check this item on the Exp Portal forum.
|
|
[+]
Engagement Designer
» Problem with database connection, 06/03/2018 13:13:56
» Go to message
|
|
Did you reboot all Breeze instances as recommended?
|
|
[+]
Engagement Designer
» Engagement Designer / Zang Studio REST task - Dynamic URI?, 03/03/2018 13:16:00
» Go to message
|
|
Hi Neil,
The path variable or the request parameter is in the curly brackets {}. Its name should contain only alphanumeric characters “-” and “_”. For example,
http://host:port/your-rest-resources/{pathVar1}/{pathVar2}/...
After that click Retrieve and tool will generate a schema for you where you can map the values of your variables.
Quoting from the help file:
"Input schema (mandatory) – Click Retrieve to generate the input schema of the Call Rest task based on the input in the Rest URI, Customized Headers and Payload fields, so ensure that all those fields are configured properly first. The schema is based on the input from these fields and is not based on anything retrieved remotely. Click the Show checkbox to view the generated input schema. The input schema allows you to do input mapping."
|
|
[+]
Engagement Designer
» Procedure Call from Engagement designer, 28/02/2018 12:04:58
» Go to message
|
|
Hi Rangari,
For calling your stored procedures, it might be best to write a simple Java dynamic task. The SDK is available to do the same.
Thanks
Vishal
|
|
[+]
Engagement Designer
» Get the Disposition Code in a flow, 03/01/2018 09:17:55
» Go to message
|
|
Hi Murillode,
I reached out to workspace team.
What is the exact use case you are trying to build? We can look at ways to facilitate the same.
Thanks
Vishal
|
|
[+]
Engagement Designer
» I don't see workflows in System Manager, 22/12/2017 12:56:00
» Go to message
|
|
All workflows are available in Admin Console and you can define rules for invocation.
|
|
[+]
Engagement Designer
» Get the Disposition Code in a flow, 22/12/2017 12:44:38
» Go to message
|
|
I will post this question to our Workspace team.
|
|
[+]
Engagement Designer
» I don't see workflows in System Manager, 19/12/2017 01:13:58
» Go to message
|
|
If you navigate to admin console, you can define your rules for when to invoke which workflow. E.g. For all incoming calls to "NNN-NNN-NNNN" use the WFD "Handle NNN" Version 1.
|
|
[+]
Engagement Designer
» changing Event family/type for a Start event, 20/11/2017 10:51:07
» Go to message
|
|
You can select the start event from the list? Your workflow doesnt need to change, only the payload will be different.
|
|
[+]
Engagement Designer
» ED announcement flow, 07/11/2017 00:36:50
» Go to message
|
|
Once you allow the call you cant do any Play announcement etc. Allow Call should be the last step in your workflow.
|
|