Package Level Signer Experience Customization
Wednesday, April 6, 2022 at 09:39amHello! For my project, I'm creating signing packages using the API. I believe I was customizing the signer experience at one point from the package payload using the settings property. Specifically the layout.brandingBar.logo.src, and the colours in style.dialog/toolbar/titleBar.
However, this wasn't working when I tried it again yesterday, and from looking around the documentation, I'm not sure if the settings property is not applicable to the New Signer Experience — I may have been using the old signer experience before.
Is it no longer possible to customize the signer experience via these properties in the package creation payload? Otherwise I'm probably doing something wrong. Thanks!
Reply to: Package Level Signer Experience Customization
Wednesday, April 6, 2022 at 10:24amHi Abbie,
Yes, the properties you were referring to only take effect in old signing experience. For New Signer Experience, logo customization and color theme customization can only specified at account level, please refer to my blog below:
https://www.onespan.com/blog/onespan-sign-developer-new-signer-experience-branding-customization
Duo
Reply to: Package Level Signer Experience Customization
Wednesday, April 6, 2022 at 03:01pmThanks for the answer! Is it still possible to switch to the old signer experience?
Reply to: Package Level Signer Experience Customization
Wednesday, April 6, 2022 at 03:06pmHi Abbie,
I am afraid not, as per documentation, as of the 11.42 release of OneSpan Sign, the Classic User Experience is no longer supported for SaaS customers (nor allow to switch back).
Duo
Reply to: Package Level Signer Experience Customization
Tuesday, April 12, 2022 at 12:21amDoes that mean it is not possible to configure different logos in a single account? i.e. there can only be one logo shown per account?
I would like to be able to show one logo for one type of message, and a different logo for a different type (something like what layout.brandingBar.logo.src would have achieved, I assume).
Thanks.