[email protected]'s account

Hi Peter,

Sorry for the inconvenience.  There was an issue in our email template service last week, and apparently engineering missed that it was still there for the Rapid POC Welcome email.  Any where it says "localhost:32778" it is safe to replace that with "gs.onespan.cloud".  In production you will have your own domain so you will replace the "gs.onespan.cloud/rpoc-saa/" with your own OneSpan tenant domain.  The "https://salesdemo-dealflo.uat.eu1.tid.onespan.cloud" is the Sales Demo OneSpan tenant domain, which we have put behind the proof of concept environment.  You can replace the "https://salesdemo-dealflo.uat.eu1.tid.onespan.cloud" with "https://gs.onespan.cloud/rpoc-saa/" and it will correctly send the transaction for you.

With regards to being able to perform the hand-off between the desktop and the mobile and then back to the desktop, this is completely supported.  Each workflow ID actually has different configurations to allow proof of concepts to test different features of the product.  The feature you are looking to test is called our multi-device handoff feature.  It is enabled in all of our Fast Track workflow IDs.  In your transaction JSON, where you currently have a workflow ID from the welcome email of "00000001-0001-0002-0002-310000000007" this is enabled for the Multi-Device Handoff feature.  If you are experiencing problems with that workflow ID, please try the "00000001-0001-0001-0002-310000000007" which is a similar configuration and also supports the Multi-Device Handoff feature.

I will ask engineering to clean up the email and I apologize for the problems.

Thanks
-Will

Hi Peter,

Engineering informs me that they have repaired the broken email template processor.  We can resend you the Rapid Proof Of Concept Welcome Email with the corrected links if you would like.  Please let me know if that would be helpful.

Thanks

-Will

Hi Peter, 

I had engineering look into the error you were receiving during the Multi-Device Handoff workflow as well.  They have identified and fixed the issue, sorry for the inconvenience.  Everything should be behaving as normal now.

Thanks

-Will