Different Email Templates

Hi Michail,

For most customer-facing email templates (a complete list of email templates here), for example "email.activate", there's a parameter "$PACKAGE_MESSAGE;" (guide here) which allows sender to set different values per signer/package. So if you used code below

DocumentPackage pkg = PackageBuilder.newPackageNamed("Example Package " + System.currentTimeMillis())
        .withEmailMessage("This is a package level email message.")
        ......
        .build();

The package level message "This is a package level email message." will appear in the invitation email like below:

Because you can only pass in plain text (no javasciprt allowed), it works well when there's only minior change in the email templates like different brandings. 

Duo

Hello Duo,

I would like to have two completely different templates for the same account.

Would it be possible?

Best Regards,

Michail

Hi Michail,

Because the email templates are set up at account level, normally you'll have to create different accounts on the basis of different lines of business. After the introduction of sub-account feature, it's possible to have two different "email.activate" templates for two child sub-accounts. However, because the sub-account feature is still experimental, it's temporary not advised to move to "roles and permissions" or "sub-accounts" feature if ANY chance of using an integration.

Duo

Hello! I'm wondering if using sub-accounts is still considered an experimental feature, or if this is production-ready for using with an integration. Thanks!

Hi Abbie,

I can't guarantee that the subaccounts feature is production-ready, but depending on the complexity of your integration, it's already possible to accommodate some of the integration use cases. I would suggest creating sandbox accounts first, migrating the code to a subaccount fashion, and fully testing the functionalities before moving to your production account.

For your further reference, the below guides or blogs could be helpful:
 

#1. Roles & Permissions feature

https://www.onespan.com/blog/onespan-sign-developers-account-role-part-1

https://www.onespan.com/blog/onespan-sign-developers-account-role-part-2

#2. How to retrieve Sub-account API keys of your admin user

https://www.onespan.com/blog/onespan-sign-release-1143-enhancements-sdks

#3. Within each subaccount, how to manage senders' transactions

Send on behalf of: https://www.onespan.com/blog/onespan-sign-developers-manage-senders-transactions-part-1
Retrieve, Manage, Download: https://www.onespan.com/blog/onespan-sign-developers-manage-senders-transactions-part-2

And please bear in mind that typically we suggest adding senders under the main account level and assigning account roles to senders in each subaccount level, subaccounts created in this fashion might behave differently (from API's perspective) from subaccounts that were formerly individual accounts and later merged under the main account.

Duo

Thanks for the quick reply! I think at this point, all we really need is to have different email templates for different packages on one account (this is why I replied to this thread instead of starting a new one :) ). Will check it out on my sandbox.