Versions Compared

Old Version 94

changes.mady.by.user Manuel Gierlinger

Saved on

compared with

New Version 95

changes.mady.by.user Manuel Gierlinger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section


Column
width150px


Column

Feature Release

eSignAnyWhere 23.36

Date: Planned September 2023 - Release Candidate installed on demo already

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces the following:

Expand
titleDrawToSignSignature feature flag

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.


Expand
titleBackup feature flag

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.


Expand
titleNotification Plugin

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:

and






Section


Column
width150px


Column

Feature Release

eSignAnyWhere 23.31

Date: August 2023 (Shared SaaS: September)

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces the following:

Expand
titleClickToSign signature feature flag

We are pleased to announce the introduction of a new feature flag, "ClickToSign", 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 ClickToSign 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 ClickToSign as 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.


Expand
titleSPID Integration

Introducing SPID Integration in eSignAnyWhere!
We are thrilled to announce the upcoming feature release of SPID integration into eSignAnyWhere, which will greatly enhance the signing process. SPID (Sistema Pubblico di Identità Digitale or Public Digital Identity System) will now be available as an OAuth Ident Provider, allowing seamless and secure authentication.

Key features of SPID integration:

  1. Signer OAuth Ident - With SPID integration, users can now enable SPID as their OAuth Ident for a streamlined and efficient signing process.
  2. Enhanced Security - SPID will serve as the OAuth Ident provider, ensuring robust security measures during the authentication process.
  3. Recipients who opt for SPID will have this Public Digital Identity System configured as their method of authentication.

Moreover, the system administrator can now define, for specific identification providers such as SPID, to overrule the configuration of the Local Registration Authority (LRA) for issuing Namirial Disposable Certificates.

Further information can be found here: SPID Identification via OIDC and Namirial RemoteSignaturePlugin#SSPVersions%3E=23.31

Prepare to elevate your e-signing process with the SPID integration in eSignAnyWhere. Stay tuned for this exciting release, as we continue to prioritize security, efficiency, and user satisfaction.





...