unlock signer doesn't work when transaction is completed via sender UI
Thursday, July 30, 2020 at 07:03pmHi ,
In on-prem v11.25, currently when the transaction is completed and signer received the completed email to download, and client is locked due to too many sms attempts, in this case, the sender is not able to unlock the signer. there is only 2 option available for the signer: 1) send new SMS code 2) notify email, both of them can’t unlock the signer.
I tried the same scenario in Saas, and it’s working there. The sender has 3 options: 1) unlock the signer 2) send complete email 3) send SMS code.
Does it mean there is the defect in v11.25 and somehow it is fixed in the later version? If so, could you let me know which version has the fix and in our current verion (v11.25), is there an alternative way to unlock the signer?
thanks,
Cindy
Reply to: unlock signer doesn't work when transaction is completed via sender UI
Friday, July 31, 2020 at 10:12amHi Cindy,
This is a known defect in classic sender UI and hasn't been fixed in SaaS environment yet, below screenshot is taken at Sandbox where the "unlock" button is missed:
PS: it's expected if the function works normal in new sender UI.
Since this scenario won't happen a lot, you can invoke API calls to have the signer unlocked and work it around. Otherwise you can create a support ticket and we can report to R&D team to see if there's a quick fix for your on-premise environment.
Duo
Reply to: Hi Cindy, This is a…
Friday, July 31, 2020 at 10:18amHi Duo,
I tested Saas new sender UI yesterday and found the fix is there. so seems like the fix is only included in new sender UI, isn't it? if so, could you please check if v11.25 new sender UI also have the fix? we have v11.25, I knew there is new sender UI in it, but we are not enable it yet.
thanks,
Cindy