We are pleased to announce the introduction of a new feature flag, "DrawToSignSignature", with this release. This feature flag brings forth notable implications for both existing and new organizations. Existing organizations as well as new organizations will have access to the DrawToSign signing method. However, we now offer the added flexibility of being more selective in activating this product feature to keep the UI a bit more clean. Furthermore, on-premise customers can configure on a per-organization basis if they want to allow DrawToSign signing method.

By implementing this feature flag, we empower organizations to tailor their signing preferences to their specific needs, ensuring a more customized and efficient experience.

For further details, please refer to Feature Flags#DrawToSignSignature.

We are pleased to announce the introduction of a new feature flag, "Backup", with this release. This feature flag brings forth notable implications for both existing and new organizations. Existing organizations as well as new organizations will have access to the Backup feature. We believe in giving our users the ultimate control and flexibility in managing their document workflows. With this feature flag, you now have the power to enable or disable the "Backup" envelopes functionality based on your specific needs and preferences. In addition to its control benefits, this flexibility also contributes maintaining a clean and streamlined user interface. Furthermore, on-premise customers can configure on a per-organization basis if they want to allow "Backup".

For further details, please refer to Feature Flags#Backup and Organization Settings#Backup.

We are excited to announce some significant improvements to our notification settings that will elevate your experience with our platform. To provide more clarity and organization, we have moved relevant notification settings into a dedicated <notificationSettings> node, ensuring easier access and management.

Here are the key changes you need to be aware of:

1. Move Notification relevant settings
   1. We have streamlined the location of notification settings for a smoother user experience. They can now be found within the <notificationSettings> node, making it more intuitive to customize your preferences.

2. Renaming <mailAttachmentDonwloadsExpireDays> to <attachmentDownloadsExpireinDays>

   1. To enhance consistency and understanding, we have renamed this settings. Please note that the functionality remains the same, we simply improved the naming for better clarity.
3. Change from single <emailNotificationSetting> to a list of <notificationPlugins>
   1. We are excited to introduce a powerful change that will allow you to configure multiple <notificationPlugin> instances rather than just a single one. This enhancement empowers you to have more granular control over your notification services.

For each node in the <notificationPlugins> list please take note of the following:

1. CUSTOM_PLUGIN_ID must be set and needs to be unique on the instance

2. Exactly one plugin must be marked as default (<notificationPlugin customPluginId="CUSTOM_PLUGIN_ID isDefault="1">)

3. Mail providers which previously called <FLOW_WEB_URL>/WebHook/Email to report status updates (bouncing), now need to call  <FLOW_WEB_URL>/WebHook/Email/CUSTOM_PLUGIN_ID with the same payload as before
4. Custom plugin implementations need to be adapted to follow the new format (nuget Namirial.Plugin.Notification 23.30.0.4)

Configuration changes can be found here:

• Email Plugin Configuration (restricted access)
• Plugin Development - eSignAnyWhere (restricted access)
• Organization Settings#NotificationPlugin