Hi Vishal,
I will work with customer to get logs.

Thanks,

Yidi

Hello,
I have a customer who reported that the workflow processes just fine and sends the SMS successfully but receiving a RED error on the termination end of the workflow. The error is confusing and make them think the workflow failed when it did not. The ED work flow processes just fine and the SMS message does reach the customer. So they are just trying to understand why they are receiving this error. I attached workflow image.

Hi Wilson,
This is very clear and helpful!
I also verified in lab using Tomcat (I don't have WAS) and it is working as designed.

Thanks,

Yidi

Hi,
I have a customer question. They saw there are two options in runtimeconfig Certificates page:

1. Use system default or externally configured certificate store.
2. Use other: with full path of the key store file

They are using WebSphere 7.x and would like to use the keystore configured on the container (Websphere JVM) not the one in runtimeconfig. However, even they check Use system default or external configured certificate store in runtimeconfig Certificates page, it seems that OD application still tries to use the key store file configured in option 2. They have two questions:

1. What does option 1 "use system default..." mean and how it works?
2. In order to use keystore configured on the container, they have to use option 2 to point to the file referred by this discussion:

https://www.devconnectprogram.com/forums/posts/list/20036.page#p144896


Thanks,

Yidi

Thank you!

Hi Wilson,
Thanks a lot for the quick reply!
Do you have an estimated timeframe for next release?

Thanks,

Yidi

Hi,
I have a question from customer.

The latest AES connector from AAOD 7.2.1 still doesn’t support TLS 1.2 as we can see that the current JTAPI client(version 6.3.3) only supports TLS 1.0. It seems a product limitation, no work around available to set TLS 1.2 in current version.

Is there any plan from product house to support TLS 1.2 in AES connector? If so, what is estimated timeframe?

Thanks,

Yidi

Hi Bill,
Thanks for the quick answer!

Hi,
I have a customer question. They are encountering an issue that French accent characters not being passed to their TTS system correctly. The TTS vendor suspects it is a codification (charset) of the text and is asking if they can use ISO-8859-15 as the charset for the text. Does Engagement Designer support this, if so how could it be implemented?

Thanks,

Yidi

Hello,
Thanks a lot for your reply!
I also would like to clarify if the first workflow using loopback. Is it normal that after 3 attempts, the exclusive gateway (IDloop) will fork the call to a Play Announcement and drop the call?

Thanks,

Yidi

Hello,
This is a customer question I received and would like to get your insights about it.

Here is an example of the question 3. The more I read on Breeze, the more I think that loop backs are not recommended. In the image below, the user enters his user ID (Play and Collect6) and it is verified with the Rest Service (RestVerifyID). The exclusive gateway (Client Verification) will compare the user ID and will loop back if the user ID is incorrect. This loop is done 3 times based on a counter. After 3 attempts, the exclusive gateway (IDloop) will fork the call to a Play Announcement and drop the call.


Should I use the logic on page 129 (Use Case Interactive voice task) of the ED Developer Guide for Oceana 3.4. I cascade 3 exclusive gateways checking for the user ID and each time forking in a different Play and collect. All the paths will be reconnected to one exclusive gateway like the example in the ED guide. (page 129) When I test my logic below, ExcGwy3 and ExcGwy6 will get this warning: The gateway has only one output connected. Please see if you really need this gateway in the workflow. This warnings is there for every type of gateway.

I added workflow image as attachment.

Thanks,

Yidi

Hi Wilson,
Thanks a lot for the quick response!

Have a great day!

Yidi

Hi Wilson,
So there is no plan to support P12 type in runtimeconfig page as users can always use other interface to manage certificates, is it correct?

Thanks,

Yidi

Hi,
I have a customer whose WAS environment doesn't recognize JKS type keystore file. Could OD runtimeconfig Certificates page supports P12 format as keystore file? When we entered .p12 file in keystore file path, it failed with error "Invalid keystore format" in OD 7. Is there any plan for OD to support P12 format in the future?

Thanks,

Yidi

In customer DD application, it assigned the following values which are valid XML characters

89:<param name="psPin" value="&quot;/&gt;&lt;exit&gt;"/>
90:<param name="psContactLogComment" value="&quot;/&gt;&lt;exit&gt;"/>

However as following show, the output values are not same as the value assigned above.

47:<var name="pin" expr="'\"/&gt;&lt;exit&gt;'"/>
48:<var name="contactLogComment" expr="'\"/&gt;&lt;exit&gt;'"/>

Is this an issue in DD or VP platform?

Thanks,

Yidi