Deployment

This release is being gradually deployed and will be available on all tenants soon. 

Improvements

• Administrators can now define which fields should be visible or even required when declining a consent form.
  
  By default, new consent form templates will have the fields for first name, last name, first name guardian, last name guardian, and email set to Show (Declining) and Required (Declining). This also applies to existing templates, allowing customers to keep their current settings provided the signee agrees to the requirement for these fields when declining consent. However, customers with specific needs for existing consent form templates must manually update their existing templates. You can adjust existing (and new) templates by following some rules. For more information, see Creating a consent form template.
   
• The Required (Declining) fields are adjustable to a certain extent for all existing and new consent form templates: Required when declining must be selected for either both the First name and Last name fields, or for the Email field. This ensures you receive at least some information from the person who has declined consent. It is not enough to just set the phone number field as required when declining, for example. You cannot save and set such a consent form to active.
   
• Since the introduction of Consent Management, the functionality to have fields required when signing has been available only for fields with the data type Text. This functionality remains unchanged with these new extended configuration options. It means that only fields with the data type Text can be configured as Required (Declining). Fields with another data type can still be configured as Show (Declining).
   
• When customers prefer to display only the name of either the person or the guardian when declining consent, the email field will still be required. Signees must provide both a name (either the person or the guardian) and an email address. As a workaround, customers can use templates designated for the person or guardian signee type.
   
• In the Consent Form overview, the guardian's first and last names are displayed in the Signee column when neither an email address nor the name of the person that the guardian signed for is given. This is indicated by (Guardian) after the name.
  
  
• The decline function can now also be previewed when previewing a consent form. 
  

Fixed issues

The following issues are fixed in this release: 

• When using keyboard navigation, the tab order was incorrect on the Forgot Password page.
• When editing a date in the date field, the monthly calendar moved up behind workflow symbols and archive tabs. 
• Running an action that modified a metadata field on the source asset, which was not editable in the metadata view of the source archive, failed with an error message. This was an issue in the October update.

Known issues

• In the web interface, when declining consent (with the option to upload a photo enabled), you don't see the This information will be used only to register your decision to decline consent. text as you do in the Fotoware Mobile app. 
• The new Consent Management changes are not yet available in all languages. The Danish, Dutch, Finnish, French, Italian, Portuguese, and Spanish translations will be available in an upcoming release.