Hi Krishna,

I am not sure how you are working with the array of phone numbers you got from the database, but I have modified your workflow (see attached) to show how it should be done. Please take a look and see if it makes sense. Please feel free to message me and we can setup a call to look into this further if you need help. Thanks!

Raúl,

What you are asking here is beyond Engagement Designer. I assume that you are talking about Oceana email solution. The details about the email are indeed stored in the Omnichannel database, but I do not have insight into whether that database has been exposed to end users. In Engagement Designer, there are ways to read from database tables using the DB tasks (Read from DB & Update DB). But for those tasks, the database should be exposed through Breeze Data Source Provider.

Several users are looking for this detail on how to get the email contents into the workflow to make intelligent decisions inside the flow. Some investigations are going on to see how to address this request. Maybe, outside of the workflow, there is a way to write the contents of the email into the Context Store and read them from the Context Store inside the flow. This is one of the options that is being investigated. Please stay tuned. Thanks!

Prakash.

Have you installed the SDKs? You will first need to install the Breeze SDK and then the Engagement Designer SDK - in that order. The error tells that the ED task archetype is not found on your machine, which will be installed as part of the SDK installation.

Marcus,
Can you get the DEBUG log for the workflow that hangs please?

Marcus,

Generally, for these kind of problems we need to review the setup and configurations. But if you are seeing the event arriving in ED, but not instance is kicked off, that may be some configuration within the ED itself. Do you know if the instance was created but just not showing in the instance tab? Do you have a Play Announcement or something in the workflow that was heard / not heard in the call?

First thing that comes to mind is - do you have the flag to delete instances after they are completed set to true? This is a flag in SMGR --> Breeze --> Configuration --> Attributes --> Service Globals, choose Engagement Designer service in the drop down, you will see a list of properties there. There will be an attribute called "Completed instance to be deleted or not". By default it is set to true. It needs to be set to false. Select that checkbox and remove true and set it to false.

If this is set correctly, then we need to review the configurations like routing rules, workflow names, etc..

Can you attach the workflow and the ED log in DEBUG level please?

No there is no such task in ED today.

Andrew,

The way you need to achieve conferencing in a Breeze / Engagement Designer scenario is to use a Conferencing Bridge and keep dialing participants into that Breeze into the conference. Breeze supports only two participants in a call natively.

Andrew,

This is the same problem you sent in email earlier today and the problem was with the filtering data you use in the query. Here is my last response to you in the email chain:

In your query outside of the Engagement Designer workflow, the company ID is ‘…FD9D’ with Status ‘Assigned’. That has two rows.
In your query inside the workflow, the company ID is ‘…5151’ with Status ‘Assigned’. There is no data in the table that matches this criteria. But there is data with company ID ‘…5151’ with Status as something else. That is why if you remove the Status input in the query it works.

If you can confirm that, we can close this topic here. Thanks!

Marcus,

What exactly is the SQL query in the task?
Is it "select top 1 * from dbo.tablename where sip = ?"

Did that same query work before you upgraded?

Instead, can you just do select * from tablename where sip = ? and then when the result set is created, just use only the first one in the array?

Jack,

Sorry that you didn't get a response. Somehow it got missed in our radar. Joel brought this to my attention yesterday and here is something that you can build upon:

Depending on which version of Engagement Designer you are running on, there were some changes to Forward Call. Regardless, to achieve what you need, you take a look at the attached workflow instance screenshots. In the Instance1 image, I have shown the use case where the Forward Call will fail and in Instance2 image, I have shown the same workflow with the use case where the Forward Call will succeed. I have also attached the workflow (ForwardTest.xml) for your reference. Note that this workflow will open only in 3.5 or later releases. If you want a version of this xml for earlier releases, please let me know. Please look into those and let me know if this would help with your requirement. Thanks!

Andy,

Please find new set of attachments where I have built the flow with 3.4 and the screenshots from it. We did not have the Data Manipulation task back in 3.4. We had Assign task. It is a bit messy task, that is why we came up with Data Manipulation task starting 3.5 release. In fact, you don't even need this Assign or Data Manipulation task to do this. You can do it on any Output Data Mapping of any task.

Andy,

It should be straight forward substring function.

In Assign or Data Manipulation task, substring the original timeOfEvent string to two different strings:
timeOnly = timeOfEvent.substring(0, 10)
dateOnly = timeOfEvent.substring(11)

Please see the attached document where I have put some screenshots. And also I have attached the workflow that I created.

Did you migrate to 3.4.0.1 from 3.4 on this lab? Can you please give a background on it?
Also, can you please uninstall Engagement Designer and reinstall it, and check if the problem goes away? Thanks!

Gentlemen, It appears multiple topics / problems are being discussed in this one thread. Going back to the original problem of this thread, do we have a problem with "simple outbound call workflow doesn't work"? I see that a workflow is kicked off, an instance is created, and it is an active instance.

Can you go into the instance and check what is going on in the instance? Do we have a problem with the workflow whatsoever? Thanks!