This is an internal documentation. There is a good chance you’re looking for something else. See Disclaimer.

Mail

Migrating the legacy mail action

The legacy mail action has been migrated to the new client in version 3.13.

Difference in functionality

The new action has been split into different screens, with the second one displaying all recipients in a pagable table. Changing recipients, preview and test mails have also been moved to the second screen.

For performance reasons, the new action resolves the selection along exactly one path to find the recipient entity. It is still possible to load email addresses from different paths, but the source and recipient entities are fixed now.

The functionality of extended recipients, meaning resolving related users from the recipients, does no longer need to be enabled explicitly in the new action, and is instead always available if the recipient is a User or a path to extendable User is given.

It is no longer possible to freely define the sender of an email. Instead a new entity Mail_sender exists that needs to be configured and then selected by the user. The possibility to send an email from the currently logged in User always exists.

Recipient is no longer built from firstname and lastname. Instead, default display is used.

Form properties

The form properties that can be passed to the action have changed extensively.

Legacy property	New property	Functionality
userRelationPath / addressRelationPath	sourceToRecipientPath	Single path to load recipients. May be to many. If empty, selection is used as recipient. If both are used, leave this empty and use recipientToEmailPath instead.
emailAddressPath	recipientToEmailPath	Comma-separated paths to load email addresses from. Fallbacks for User and Address recipients exist, so this can be usually be left empty for those.
firstnamePath / lastnamePath	recipientToDisplayPath	Comma-separated paths to load default display from. If empty, default display of recipient is used.
outputLanguagePath	sourceToLanguagePath / recipientToLanguagePath	Comma-separated paths to load language from. recipientToLanguagePath has priority over sourceToLanguagePath. relCorrespondence_language is used if recipient or selection has that relation.
No equivalent	recipientToExtendedUserPath	Can be used if recipient is not a User, but using extended recipients should still be possible by resolving a relation to User first.
extended	No equivalent	Extended recipient functionality is always active if applicable to recipients.
suppressChangingRecipient	No equivalent	Removed without replacement.