Versions Compared

Old Version 8

changes.mady.by.user Christoph Bimminger

Saved on

compared with

New Version 9

changes.mady.by.user Manuel Gierlinger

Saved on

Key

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

...

Expand
titleAPI / Integration: How to modify SMS OTP message (language and content)?

With api v6 it is not possible to modify the message for e.g. SMS OTP via API. This customization is available for lower api versions (<= v5).the feature flag ActivityEngineCustomLocalizations its is possible to change the language and content of SMS OTP messages.

General process:

  1.  Make a copy of the file provided for downloading in the organization settings in the section Activity-Engine Custom Localizations
  2. Rename it to include the language code of the target language (e.g. Localizations.de.custom.json)
  3. Open the copied file
  4. Find the items you want to change and adapt the values accordingly,
  5. Remove all other items (which still have the default value) to receive updates automatically after a software update

For available default languages see Language Support
Attention: SMS length restrictions apply for entries in group 'transactionCodeConfigurations'"

For more information about the modifying of messages and the integration please have a look at the developer faq for lower versions. Organization Settings#Activity-EngineCustomLocalizations eSignAnyWhere Release News (v 23.49) and Feature Flags#ActivityEngineCustomLocalizations


Expand
titleAPI / Integration: Envelope is finished, but status is still "in Progress".
If you have a finished envelope (all recipients finished) and the state of the envelope is still “in Progress”, the reason could be the post processing (the callback). The callback expects a HTTP 200 and if an error is returned it tries to call the callback after some time again (up to 30 times). This could delay the “finished” or “error” of the envelope.

...