The feature of copying and pasting parts of workflows from different workflows / different tabs in a workflow is not available today. To overcome this, you can "modularize" your workflow - if multiple people need to contribute to the workflow building process. What I mean by this is that, different people can work on different workflows, and you can use the Create Process task to kick off another workflow from inside a workflow.

Kata,

The icons for the tasks developed by Avaya are designed and created by our UX team. However, any icon with the .png extension should work for you. For the third party tasks, the only detail required is that the icons are of size 32x32 pixels - to get the whole icon to be visible. This information is present in the SDK document. But even if your icons are bigger, it will still work showing part of the image. I hope this information helps.

Kata, I have sought some help from the Breeze team to answer this. Please stay tuned.

Kata,

I think this explains why it was working right for me when I tested with your workflow as I was working with the latest code base. We will have this fix in 3.2.2 of ED/Oceana release which will be available by end of March. If you can't wait until then, please let us know and we will see if we can escalate this process and get the fixes to you.

Thanks!

Kata,

Thanks for posting this question in this forum here. I pulled your workflow from the question, deployed and executed. I got this after the JSON Stringify task:

2017-01-25 10:13:20,828 [WebContainer : 4] EngagementDesigner FINE - EngagementDesigner-3.2.2.0.715119 - starting data mapper: [associations] [ContextStore:uuid907e7f36_c4ee_8a97_e1d2_1485190677806:ContextStoreJSON:uuid97868095_5462_3335_96bd_1485344707942:[.:CSJSON:{"range":[0,57],"type":"CallExpression","callee":{"range":[0,14],"type":"MemberExpression","computed":false,"object":{"range":[0,4],"type":"Identifier","name":"JSON"},"property":{"range":[5,14],"type":"Identifier","name":"stringify"}},"arguments":[{"range":[15,56],"type":"Identifier","name":"uuid907e7f36_c4ee_8a97_e1d2_1485190677806"}]}]][lvars][out.put:{"outputString":"tmp","outputInt":1}, uuid97868095_5462_3335_96bd_1485344707942:{}, uuid12345678901234567890:{"wfdVersion":"1","instanceId":"301","securityIP":"10.129.177.184","wfdName":"test11"}, uuid907e7f36_c4ee_8a97_e1d2_1485190677806:{"csDataInput":{"contextId":"temptestContextId","data":{"ServiceMap":{"1":{"priority":"5","attributes":{"Service":[null],"Channel":[null],"Location":[null],"Language":[null]}}}}}}, uuidProperties1234567890:{}][rvars][uuid97868095_5462_3335_96bd_1485344707942:{}, uuid12345678901234567890:{"wfdVersion":"1","instanceId":"301","securityIP":"10.129.177.184","wfdName":"test11"}, uuid907e7f36_c4ee_8a97_e1d2_1485190677806:{"csDataInput":{"contextId":"temptestContextId","data":{"ServiceMap":{"1":{"priority":"5","attributes":{"Service":[null],"Channel":[null],"Location":[null],"Language":[null]}}}}}}, uuidProperties1234567890:{}]

As you can see above, the ServiceMap gets an array. It is getting a null because I dont have a value for your property there, but, it is an array containing a single null. So may be there is something wrong on your side... We can troubleshoot in a live session if you like.

Thanks!

Thanks for triggering an alert by posting a msg in this thread. We are actively working on fixing this problem. The drop downs to access AMS recordings in the two Play tasks in Engagement Designer have some problems accessing AMS starting 3.2. We will notify you once a fix is available. Thanks for your patience!

If it helps you Shay, I have made the world's simplest workflow that makes a 1 party call to FirstParty, then uses Add Participant to add the SecondParty to the call to establish the call between FirstParty and SecondParty. Is this something along the lines that you are trying to do here? If you can send us your workflow (along with the answers to the other questions I posted in my previous response), it would be helpful to help you more. Please let us know. Thanks!

Shay,

I think you are trying to create a workflow in Engagement Designer. Can you please:

(1) Give us the workflow you have so far.
(2) Tell us what version of Engagement Designer / Breeze you are using?
(3) Provide bit more description on what are you trying to achieve? You have a make call. I am assuming it is a Make 1 Party Call. I dont think you can add a participant like this after making the call. You can make the Make Call task into Make 2 Party Call and provide your second party information there itself - if you are trying to make a call between two parties... if that is what you are trying to achieve.

Thanks!

Please bear with us... We just returned back after the holidays and we are looking into this.

I am assuming this is Engagement Designer 3.2 (as the ED version is not mentioned in the topic so far). There may be a problem with these drop down boxes to access the media files that we are discovering. We are not sure yet if what you are seeing is related to this problem or not. Please give us some time to determine the root cause. If we need access to your system, we will request for it. Thanks!

There is no 'straight forward' way Andrew... like a tool or something - if that is what you are looking for..
But the manual steps are pretty much straight forward anyway.

- You edit the tasks.json and add the other two tasks into the categories array.
- Bring the resources of the other two tasks (help files, icons)
- Bring the source files from the other two tasks (Modal and Execution classes and any other helper classes if you used them)
- Finally bring any external dependencies you have in the pom.

It may not take more than a few minutes to do these steps... I can help you if you need. Please let me know.

Can you please answer these questions first:

(1) Was these drop downs working before with a different version of Media Server?
(2) Do you have a workflow with Play Media tasks configured with media defined and categorized into namespaces and groups?
(3) If it has been working before, let us start with the Engagement Designer logs first, captured in FINE level.

If it wasn't working until now with any other version of Media Server, then you need to configure the Media Server with the choices of namespaces and groups. I guess the Avaya Media Server documentation tells how to do this. Once it is configured, those categories should be available in those drop downs.

Can we start with answering the questions above please?

Andrew,

Sorry I am not with my laptop... on personal travel. So I cant really verify your code right now, but from the looks, it appears that it is validating only one property because of the "return"s when you catch a validation msg after validating the first property. Instead of those return statements you may need to add your validation msg to the errors or warnings list and move on to validate the next property. I can help you more when I return back to work after the first week of December. If you need immediate help, please say so in your response here and someone else in the team will help you. Thanks!

Anderson,

From the description you have provided, you don't need a dynamic task. You can build a simple workflow with the out of the box tasks in Engagement Designer and accomplish what you need.

Here is what you will need:

Call Intercept --> Ask to punch in the pin using Play and Collect --> Validate the pin by reading from a database (or something similar) --> Make a decision about the validity of the pin (Exclusive Gateway) --> On valid, go to the second Play and Collect for the choice of 1-5 and move on to your REST, on Invalid, play a different message and forward the call to a specific extension --> End the flow.

This is the typical flow you are describing. You can fine tune it though. Please let us know if you need help building this workflow and I would be happy to help. Thanks!

You Rock Andrew! :-)

I was kind of expecting to have a meeting with you to explain this!!

Andy,

Using Sub-Process across workflows is not supported today as the sub processes today are defined as "inline" subprocesses - which means that they are defined inside a main workflow and is available only in that workflow.

However, if you want to re-use workflows across multiple different workflows today, you can use a task called "Create Process" that will allow you to call a different workflow from one workflow.

I hope this helps.