Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Preferences
Replies
Topics Started
Topic Started
Topics |
---|
Hi OneSpan Team - As per our requirement , the ESign process for 2 roles happen within the pega application process flow , We need not send emails to the Esign users
to complete the Esign process via
|
Hi OneSpan Team - I have gone through the below article and it mentions that the Session Expiry Redirect URL can be configured at Account Level , I have gone through my account and not found any con
|
Hi OneSpan Team - We have a requirement where when the ESign doc is loaded in IFRAME , we need to capture events (consent accept , E sign acceptance)
via the window listener, we have included the atta
|
Hi Team - Once we have accepted the consent document , and when the document is loaded again to be accepted ,what we see is the the confirm button
on top right above the the navigation tool , Also on
|
Hi OneSpan Team - As per our requirement , we need to have a Signature block at the end of the document to capture the Fullname and DateTime when the
document was signed.
|
Replies Created
Reply to: FULLNAME signature block format changing between English and French
Tuesday, April 2, 2019 at 03:01amHi Haris - Had the same issue here , For the french version the FULLNAME attribute is working fine , we are getting the fullname and datetime for the Signer but
for the english version only getting the fullname of the Signer . Not sure why we need help from Support team to get this configured on the account when we are setting the Language at the document level
Reply to: Enum value FULLNAME does not populate ESign date for English version
Tuesday, April 2, 2019 at 07:18amHi Duo - Thanks for the reply , I have already sent a request mail to the email id you posted along with my account details. Waiting to hear back from them
once they have configured.
Regards,
Danny
Reply to: ESign document has 2 SIGNATURE block
Wednesday, April 3, 2019 at 01:41amHi Duo - Thanks for your reply , we have tweaked the Request body to remove the approval structure under documents , which was causing the issue ,Its working fine now
Regards,
Danny
Reply to: False Link and confirm Button on ESign accepted doc
Wednesday, April 3, 2019 at 10:09amHi Duo - Thanks for your reply , we have now removed the tag (that you posted) from to the request body and its working fine as expected. Appreciate for your quick response.
Regards,
Danny
Reply to: Window event listener not getting called on consent and doc acceptance in IFRAME
Wednesday, April 3, 2019 at 02:48amHi Duo - Have attached the same in zip
Regards,
Danny
Subscriptions
Topics | Replies | Freshness | Views | Users |
---|---|---|---|---|
Hi OneSpan Team - As per our requirement , the ESign process for 2 roles happen within the pega application process flow , We need not send emails to the Esign users
to complete the Esign process via
|
3 | 4 years 11 months ago | 26 | |
Hi OneSpan Team - I have gone through the below article and it mentions that the Session Expiry Redirect URL can be configured at Account Level , I have gone through my account and not found any con
|
4 | 4 years 11 months ago | 32 | |
Hi OneSpan Team - We have a requirement where when the ESign doc is loaded in IFRAME , we need to capture events (consent accept , E sign acceptance)
via the window listener, we have included the atta
|
12 | 4 years 11 months ago | 75 | |
Hi Team - Once we have accepted the consent document , and when the document is loaded again to be accepted ,what we see is the the confirm button
on top right above the the navigation tool , Also on
|
3 | 4 years 11 months ago | 26 | |
Hi OneSpan Team - As per our requirement , we need to have a Signature block at the end of the document to capture the Fullname and DateTime when the
document was signed.
|
3 | 4 years 11 months ago | 12 |
Subscriptions Release Notes
This user is not subscribed to any release notes.