emmat

Template designer Add Recipient form validation

0 votes

Hi,

When opening a new Template in the designer view embedded in our app I've noticed some things with the Add Recipient form:

1. By default it selects Recipient when the package type is Template. It would be nice if for templates a new recipient's type is defaulted to Placeholder.

2. When the type is set to Recipient, the Role field always shows "This field is required" even when it has a value, such as the default value "Signer 1". It stays like this as long as other fields are invalid, which is confusing. Also the Email field does not show the required validation message when empty. I've added screenshots below for this.

Screenshot 1:

Example of Role field showing as invalid when value is entered
Role field showing as required when set but any other field is invalid

Screenshot 2:

 

Example of Email field not showing as required when no value entered
Email field not showing as required when empty

Screenshot 3:

 

Role field appears fine only when all fields are valid
Role field appears fine only when all fields are valid

 


Reply to: Template designer Add Recipient form validation

0 votes

Hi emmat,

 

For the first point "By default it selects Recipient when the package type is Template. It would be nice if for templates a new recipient's type is defaulted to Placeholder." I can help you raise it as an UI enhancement if you preferred and sends me a brief business motivation behind it.

For the UI validation issue, I also think these are UI flaws. I will create a support ticket on your behalf, and our support agents will help to report the issue to R&D team in short time.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Template designer Add Recipient form validation

0 votes

Hi Duo,

Thanks you for creating the support ticket.

For the first point, our business application needs to define and re-use templates for saving documents, field definitions, and recipient roles. We will only fill out the recipient information when creating a transaction from the template. For example, creating a re-usable template for a Contract document with fields to be filled and signed by a Contractor. So with the current design our template managers will need to change the recipient type from Recipient to Placeholder the majority of the time they create new templates.


Reply to: Template designer Add Recipient form validation

0 votes

Thanks for your sharing, I've created an Enhancement Request with reference ID OSSSAAS-I-929. I will update this thread as long as there's any updates.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off