Email Connector

Introduction

The Email Connector allows you to send and receive emails using your own email server. It supports features like template-based emails, digital signatures, and encrypted email sending.

The Email Connector is a toolkit providing reusable components (snippets, microflows, entities, and Java actions) for building custom email functionality. This documentation covers the setup and configuration of these components in your Mendix application.

Key Features

The Email Connector includes the following capabilities:

• Multiple email accounts

• Authentication support:

  • Basic Authentication (username/password)
  • OAuth 2.0 (Authorization Code Flow & Client Credentials Flow)
  • Microsoft Entra ID integration

• Email protocols:

  • POP3 and POP3S
  • IMAP and IMAPS
  • SMTP

• Security features:

  • Digital signatures (PKCS#12 certificates)
  • Email encryption with LDAP integration
  • SSL/TLS encryption
  • XSS attack prevention

• Shared mailbox support

• Email Templates with rich text editor and placeholder tokens

• Real-time email monitoring and folder management

• Attachment support (normal and inline)

Prerequisites

Before using the Email Connector in your app, make sure to complete the following steps in the order described.

1. Download and configure the latest version of the Mx Model Reflection module.

2. Download and configure the latest version of the Community Commons module.

3. Download and configure the latest version of the Encryption module. The EncryptionKey constant must be set up in your application settings. See the EncryptionKey Constant section of Encryption.

4. Uninstall any previously installed email modules, such as IMAP/POP3 and Email Module with Templates.

5. Remove any JAR files still present in the userlib folder from older email modules which are now unused (for example, javax.mail-1.6.2.jar, activation-1.1.jar, and commons-email.jar).

6. Clean the deployment directory.

7. Add the Email_Connector_Overview page located in the USE_ME > Pages to your app navigation.

   The Email_Connector_Overview page launches the user interface which allows you to configure email accounts. This overview page provides access to configure and manage the following configurations and settings:

   • Send Email
   • Receive Email
   • Templates
   • Configure OAuth

Migrating From Another Module

When migrating to the Email Connector from a different email module, it is recommended to test your configuration in a separate app before applying it to your main project.

Mendix recommends that you use the community-supported Email Connector Migration Utility module to migrate data from the Email Module with Templates service.

Included Widgets

The module includes the following bundled widgets:

• HTML Element
• Rich Text
• Pop-Up Menu

Setting Up the Email Connector in Studio Pro

Configuring Roles

The module includes a default EmailConnectorAdmin role with preconfigured access rights for common use cases. Review and verify that the access rights align with your specific requirements and security policies before assigning this module role to user roles in App Security. In addition, configure any required module roles for the prerequisite modules you are using.

Building Email Functionality

The Email Connector provides building blocks you can assemble to create email functionality.

Domain Model

The domain model in Mendix is a data model that describes the information in your application domain in an abstract way. For more general information, see Data in the Domain Model. To learn more about entities and their associations in the domain model of the Email Connector, see the section below.

EmailAccount

The EmailAccount entity manages email account configurations, authentication methods, and security settings for both incoming and outgoing email operations.

IncomingEmailConfiguration

The IncomingEmailConfiguration entity manages email retrieval settings, processing options, and server connection parameters for incoming messages.

OutgoingEmailConfiguration

The OutgoingEmailConfiguration entity manages Send Protocol settings, security protocols, and reliability options for sending emails.

EmailMessage

The EmailMessage entity represent individual email messages with complete metadata, content, and processing status tracking. This entity is used for both sending and receiving emails.

EmailTemplate

The EmailTemplate enables reusable email designs with dynamic content placeholders for consistent and efficient messaging.

Attachment

Specialized file Attachment entity extend Mendix System.FileDocument to provide comprehensive file handling capabilities for email communications.

Snippets

Snippets allow you to make interface changes in one place that automatically apply to every page where the snippet is used, reducing maintenance effort and ensuring consistency. You can find the following snippets in the USE_ME > Snippets of the Email Connector module:

Authentication & Configuration

• SNIP_Configure_OAuth – Select OAuth provider from configured list when setting up email accounts
• SNIP_Configure_PrimaryUser_Login – Configure primary user login details for an email account
• SNIP_Configure_Shared_Mailbox – Option to set up shared mailbox access using primary account details
• SNIP_OAuthProvider_CreateEdit – Create or modify OAuth provider configuration

Account Management

• SNIP_EmailAccount_SendAccountSettings – Configure outgoing EmailAccount settings and preferences
• SNIP_EmailAccount_ReceiveAccountSettings – Configure incoming EmailAccount settings and preferences

Email Operations

• SNIP_EmailTemplate_CreateEdit – Create or edit email templates with rich text and placeholder tokens
• SNIP_Incoming_Email_Config – Manage incoming email settings including folders and processing options
• SNIP_EmailLog_Overview – View email sending and receiving activity logs

Protocol & Security

• SNIP_Send_ProtocolDetails – Configure outgoing/send email protocol (SMTP) details
• SNIP_Receive_ProtocolDetails – Configure incoming/receive email protocol details
• SNIP_Send_EmailSecurity_Edit – Manage email security features including digital signatures and encryption

Microflows

The Email Connector module contains a number of pre-written microflows you can use to carry out various email-related functions.

Core Microflows

• SUB_SendEmail – Send emails using selected EmailAccount
• SUB_RetrieveEmails – Fetch emails from selected EmailAccount
• SUB_EmailAccount_CheckServerConnection – Validate email server connectivity and account configuration

Sample Microflows

• Sample_ASU_SubscribeForEmailNotification – Set up email notification subscriptions
• SUB_GetSystemError – Retrieve system error information

Java Actions

The Email Connector module contains a number of Java actions which you can use to carry out various email-related functions.

• SendEmail – Accepts EmailMessage and EmailAccount objects to send an email
• RetrieveEmailMessages – Fetches emails from the server based on specified EmailAccount
• GetAutoConfig – Automatically discover email server settings for common providers
• GetFolderNames – Retrieve available email folders from the server
• GetBaseDNList – Get directory service base distinguished names for LDAP integration

Send Email

1. Deploy your application to set up your Send Email accounts through the Email Connector user interface.
2. Navigate to the Email Connector Overview page.
3. Select the Send Email tab.
4. Click Add New Configuration or edit an existing one using the Action.

You can now set up your account for sending email by providing the following details:

Authentication Methods

Configuration supports two authentication methods:

• Basic Authentication
• OAuth 2.0

You can set these up using the Enable Microsoft Entra ID Authentication:

• Select Yes to enable OAuth 2.0 authentication through Microsoft Entra ID – you will need to fill in the details described under OAuth Authentication
• Select No (default) to use basic authentication with username and password – you will need to fill in the details described under Basic Authentication

Basic Authentication

Primary Account Details

• Display Name – The name shown to email recipients
• Email or Username – The email address or username for the sending account
• Password – The account password for basic authentication; the field is masked for security

Configure Shared Mailbox

This is an optional feature for setting up shared mailbox access. It requires using the primary account details for configuration. Enable this feature by clicking the checkbox Shared mailbox.

Email Protocol

Email Protocol currently supports SMTP for outbound email transmission.

Server Configuration

• Server Host – The SMTP server hostname or IP address
• Server Port – The port number for SMTP communication

Security Options

• SSL – Enable Secure Sockets Layer encryption
• TLS – Enable Transport Layer Security encryption

OAuth Authentication

You can configure your account to authenticate with Microsoft Entra ID OAuth 2.0. Multiple OAuth 2.0 providers can be configured per app.

To manage configurations:

• Select the Configure OAuth tab to add, delete, and edit OAuth configurations
• If no OAuth configurations are configured, you can create a new configuration

For detailed steps and implementation guidance, see the Configure OAuth section below.

Additional Account Settings

You can view and change the following settings by clicking View Settings as the Action of an existing account.

Email Settings Tab

Server Identity

• Use SSL check server identity – Select this to turn on the optional security feature to verify server identity during SSL connections and enhance connection security by validating server certificates
• Connection Timeout (Milliseconds) – Configure the maximum time to wait for server connections; default is 20000 milliseconds (20 seconds)

Outgoing Emails

• Full Name – The display name for outgoing emails; this name appears in the From field of sent messages
• Max. send attempts – Maximum number of retry attempts for failed email sends; default is 0 (no retry attempts)

Email Security Tab

Configure Digital Signature

• Configure Digital Signature – Check this option to digitally sign outgoing email messages during send email actions using the following settings; once configured,it provides message authentication and integrity verification
  • Certificate (PKCS#12) – Upload a PKCS#12 certificate file for digital signing; this supports standard PKCS#12 format certificates
  • Passphrase – Required to access the PKCS#12 certificate; this field is mandatory when using certificate-based digital signatures

Configure Email Encryption

• Configure Email Encryption – Check this option to encrypt outgoing email messages during send email actions using the following settings; it provides additional security for sensitive email communications
  • LDAP Configuration
    • LDAP Host – LDAP server hostname for certificate lookup
    • LDAP Port – LDAP server port (default: 389)
  • Authentication Method – The system supports two authentication methods for LDAP access:
    • No Authentication – Connect to LDAP server without credentials
    • Basic Authentication – Use username and password for LDAP server access

Error Logs Tab

This tab displays a list of any log entries related to errors which occurred during a send email operation in the Email Connector module.

Sending Email via Microflow

Use the SUB_SendEmail microflow for standardized, Mendix-compliant email delivery with proper error handling and configuration management. For this you will need to create your message as an object of type Email_Connector.EmailMessage and associate it with the Email_Connector.EmailAccount object containing the send mail account.

When sending an email, the To, From and Content fields are mandatory. When sending emails using templates, refer to the Templates section below.

Sending Email via Java Action

When modeling your app in Studio Pro, use the SendEmail Java action to send emails. The input parameters are as follows:

• EmailAccount – The entity containing the configuration details for the outgoing email account
• EmailMessage – The entity instance containing the content and details of the email to be sent

The return type is a Boolean value. This Java action uses the provided details to connect to the email server and send an email. It returns True if successful and displays the error object and cause if it fails.

When sending an email, the To, From and Content fields are mandatory. In To,CC, and BCC, you can optionally specify multiple email addresses, each separated by a semicolon (;).

Receive Email

1. Deploy your application to set up your Receive Email accounts through the Email Connector user interface.
2. Navigate to the Email Connector Overview page.
3. Select the Receive Email tab.
4. Click Add New Configuration or edit an existing one using the Action.

You can now set up your account for receiving email by providing the following details:

Authentication Methods

Configuration supports two authentication methods:

• Basic Authentication
• OAuth 2.0

You can set these up using the Enable Microsoft Entra ID Authentication:

• Select Yes to enable OAuth 2.0 authentication through Microsoft Entra ID – you will need to fill in the details described under OAuth Authentication
• Select No (default) to use basic authentication with username and password – you will need to fill in the details described under Basic Authentication

Basic Authentication

Primary Account Details

• Display Name – The name shown to email recipients
• Email or Username – The email address or username for the sending account
• Password – The account password for basic authentication; the field is masked for security

Configure Shared Mailbox

This is an optional feature for setting up shared mailbox access. It requires using the primary account details for configuration. Enable this feature by clicking the checkbox Shared mailbox.

Email Protocol

Email Protocol – Choose from available email protocols for receiving emails:

• IMAP – Internet Message Access Protocol for email retrieval and management
• IMAPS – IMAP over SSL/TLS for secure email access
• POP3 – Post Office Protocol for email downloading
• POP3S – POP3 over SSL/TLS for secure email downloading

Server Configuration

• Server Host – The hostname or IP address of the incoming mail server
• Server Port – The port number for the email protocol – by convention these are usually the following:
  • IMAP – Port 143 (non-encrypted) or Port 993 (SSL/TLS)
  • IMAPS – Port 993 (SSL/TLS encrypted)
  • POP3 – Port 110 (non-encrypted) or Port 995 (SSL/TLS)
  • POP3S – Port 995 (SSL/TLS encrypted)

OAuth Authentication

You can configure your account to authenticate with Microsoft Entra ID OAuth 2.0. Multiple OAuth 2.0 providers can be configured per app.

To manage configurations:

• Select the Configure OAuth tab to add, delete, and edit OAuth configurations
• If no email accounts are configured, you can create a new OAuth configuration

For detailed steps and implementation guidance, see the Configure OAuth section below.

Additional Account Settings

You can view and change the following settings by clicking View Settings as the Action of an existing account.

Email Settings Tab

Server Identity

• Use SSL check server identity – Optional security feature to verify server identity during SSL connections and enhance connection security by validating server certificates
• Connection Timeout – Maximum time to wait for server connections; default is 20000 milliseconds (20 seconds)

Incoming Emails

• Folder to replicate E-mails from – Specify the email folder to monitor for incoming messages; default is "INBOX" – click Select… to choose any existing email folder on the account
• Subscribe to incoming emails – Disabled by default. Enable this option if you want to receive notifications for new incoming emails. For modeling purposes, use the SubscribeToIncomingEmail Java action. This feature is supported only for IMAP protocols, and some mail servers may not support it.
• Replicate everything in 'INBOX' folder – Disabled by default. When off, retrieves only the specified number of emails based on the fetch strategy. When enabled, replicates all emails from the specified folder in batches (oldest to newest) using the configured batch size.
• Number of emails to retrieve from server – Set the maximum number of emails to fetch in a single operation; default is 50
• Fetch strategy – Controls the order in which emails are retrieved from the server
  • Latest – Retrieves most recent emails first
  • Oldest – Retrieves oldest emails first
• Email handling on server after replication – This setting determines what happens to emails on the server after they have been replicated to your Mendix application.
  • None (default) – does the following:
    • Leaves emails unchanged on the server after replication
    • Suitable for read-only processing or multi-system access
  • Remove original emails from server – does the following:
    Use this setting with caution, as this action is irreversible.
    • Permanently deletes emails after replication
    • Helps manage server storage space
  • Move emails on server to another (existing folder) – does the following:
    • Transfers processed emails to a different folder
    • Maintains email history while organizing processed messages
    • Requires specifying an existing target folder
• Inline image rendering (HTML emails will have images visible in browser) – does the following:
  • Controls how HTML email images are displayed
  • When enabled, images embedded in HTML emails are rendered in the browser
  • Enhances readability but may have security implications
• Sanitize email to prevent XSS attacks – does the following:
  • Enables security filtering to prevent cross-site scripting attacks
  • Removes potentially malicious scripts and content from email messages

Error Logs Tab

This tab displays a list of any log entries related to errors which occurred during a receive email operation in the Email Connector module.

Receiving Email

To receive emails in your Mendix app, use the RetrieveEmailMessages Java action. This action fetches emails asynchronously in batches using multiple threads and returns a list of EmailMessage objects. Email retrieval continues until the criteria specified in the email account settings are met (for example, fetching the latest 1,000 emails). For details, see Additional Account Settings.

The input parameters for receiving email are the following:

• EmailAccount – This is an email account containing the incoming email configuration.

• onEmailFetchMicroflow – This is a microflow that is triggered when a list of EmailMessage is fetched from the email server, as per the batch size specified in the email account settings. You can process the list according to your needs.

  If duplicating the onEmailFetchMicroflow microflow, do not change the input parameter name or data type. To prevent errors, make sure you have List of Email_Connector.EmailMessage as a parameter to this microflow.

• onFetchCompleteMicroflow – This is a microflow that is triggered when the email fetch action is successfully completed.

• onFetchErrorMicroflow – This is a microflow that is triggered if there are errors while fetching from the email server.

Configure OAuth

1. Deploy your application to set up your OAuth Configuration through the Email Connector user interface.
2. Navigate to the Email Connector Overview page.
3. Select the Configure OAuth tab.
4. Click Add New Configuration or edit an existing one using the Action.

The Email Connector supports two sorts of OAuth authentication. Under Choose Authentication select one of the following:

• Auth code grant flow – OAuth 2.0 Authorization Code Flow
• Client credential grant Flow – for Microsoft Entra ID (formerly Azure Active Directory) accounts

Auth Code Grant Flow

To configure an OAuth provider for the Auth code grant flow, provide the following details:

• OAuth Configuration Name – A name to identify this configuration
• Client ID – Application identifier obtained from Microsoft Entra ID after app registration
• Client Secret – Authentication key generated during Microsoft Entra ID app registration
• Callback Path – Custom string used to autogenerate the callback URL
• Callback URL – Redirect URI where the OAuth provider returns after authorization
• Token endpoint URL – Used by client to exchange an authorization grant or refresh token for an access token. https://login.microsoftonline.com//oauth2/v2.0/token

<rule name="mxecoh">
<match url="^(mxecoh/)(.*)" />
<action type="Rewrite" url="http://localhost:8080/{R:1}{R:2}" />
</rule>

Configuring Microsoft Entra ID

Follow Microsoft's tutorial Register an app with Microsoft Entra ID to register your app on the Microsoft Entra ID. As mentioned above, make sure to set the Redirect URI to the Callback URL.

This connector contains functionality for sending and receiving emails, so during the OAuth process, the connector will ask for permissions for sending and receiving emails.

API Permissions

On the Microsoft Entra ID, ensure you have the following permissions enabled under the API permissions tab on the sidebar.

Depending on your use case, modify the azure_defaultConfig constant to specify the required OAuth scopes for your application.

Send Emails

Receive Emails

Client Credential Grant Flow

To configure an OAuth provider for the Client Credentials Flow, provide the following details from Microsoft Entra ID after app registration:

• OAuth Configuration Name – A name to identify this configuration
• Client ID - Application identifier from your registered app
• Client Secret - Authentication key generated for your application
• Tenant ID - Directory identifier for your Microsoft Entra ID tenant
• Token endpoint URL – Used by client to exchange an authorization grant or refresh token for an access token. https://login.microsoftonline.com//oauth2/v2.0/token

With the Email Connector version 5.2.0 and above, you can send emails using the Client Credentials Flow.

Follow Microsoft's Register an app with Microsoft Entra ID to register your app in the Microsoft Entra ID portal.

This connector contains functionality for sending and receiving emails. APIs related to Office 365 Exchange Online need to be given permission along with admin consent.

API Permissions

On the Microsoft Entra ID, ensure you have the following permissions enabled under API permissions tab on the sidebar.

Send Emails (Application Permissions)

Receive Emails (Application Permissions)

Admin status is given on the added API permissions. The tenant admin must register the Microsoft Entra ID application's service principal in Exchange via Exchange Online PowerShell, as described in Register service principals in Exchange.

Templates

The Templates tab allows you to configure templates you can use to send your emails.

1. Deploy your application to set up your Email Templates through the Email Connector user interface.
2. Navigate to the Email Connector Overview page.
3. Select the Templates tab.
4. Click Add New Template or edit an existing one using the Action.

Creating an Email Message from a Template

Use the CreateEmailFromTemplate Java action to generate a draft email message that can be previewed and customized. Once finalized, send it using the Send email action. The input parameters are as follows:

• DataObject – Entity object from which placeholder tokens are extracted. To retrieve data from multiple objects, create a non-persistable entity. This is an optional parameter; it is required only if the template contains placeholder tokens.
• EmailTemplate – Email template used to construct and send an EmailMessage object.
• Queued – When enabled (true), the email message is stored in the EmailMessage entity with a Queued status. This configuration enables later transmission via scheduled events.

You can leverage the SE_SendQueuedEmails microflow to set up the necessary scheduled events. You can also create a task queue and run the microflow in that task queue to minimize system resource usage. With a task queue, you can set the number of threads, node or cluster-wide scope, time intervals, and other parameters.

Review the demonstration microflow Sample_ACT_CreateEmailFromTemplateAndThenSend as a reference. This microflow demonstrates how to implement the CreateEmailFromTemplate Java action while managing attachments for the EmailMessage, incorporating both existing EmailTemplate attachments and supplementary files.

Sending an Email with a Template

Use the SendEmailWithTemplate Java action to send an email from a template. The input parameters are as follows:

• Data Object – Entity object from which placeholder tokens will be extracted. To retrieve data from multiple objects, create a non-persistable entity.
• EmailAccount – Email account with the necessary send email configuration details.
• EmailTemplate – Email template used to construct and send an EmailMessage object.
• Queued – When enabled (true), the email message is stored in the EmailMessage entity with a Queued status. This configuration enables later transmission via scheduled events.

You can leverage the SE_SendQueuedEmails microflow to set up the necessary scheduled events. You can also create a task queue and run the microflow in that task queue to minimize system resource usage. With a task queue, you can set the number of threads, node or cluster-wide scope, time intervals, and other parameters.

Review the demonstration microflow Sample_ACT_SendEmailWithTemplate as a reference. For dynamic configuration of To, CC, or BCC fields, update the EmailTemplate object with the required attribute values and provide this modified EmailTemplate object as input to the Java action.

Export Email Template

You can export an email template using the Email Connector to streamline the process of template recreation across various environments including development, acceptance, and production. Follow the steps below:

1. Choose the email template you want to export.
2. Select Export from the Pop-up Menu.

An XML file will be generated with a filename that combines the template name and current datetime, and will be saved directly to your default downloads folder. The following image illustrates the downloaded XML file after completing the email template export.

Import Email Template

An exported email template can be imported into the current deployment environment or a different one. To import, follow these steps:

1. Click Import Template.
2. Select the template file (.xml) you want to import.
3. Click Import Template.

Troubleshooting

Sending or Receiving Email

If you have issues sending or receiving emails:

1. Check the Error logs in Account Settings.
2. Review the logs in Studio Pro.

If an email does not appear in your app and there is nothing in the logs, the problem is not with the connector.

Gmail Accounts

Gmail no longer supports basic authentication (usernames and password). However, you may still be able to set up an account in the Email Connector by doing the following:

1. Read Less secure apps & your Google Account and turn off the Less secure app access setting in your Google account.
2. Set up an app password to sign in to the Email Connector. For more information, see Sign in with app passwords.

Deprecation of Basic authentication in Microsoft Exchange Online

As of October 1, 2022, Microsoft has deprecated Basic Authentication, and it is no longer supported in Exchange Online, promoting Modern Authentication (OAuth 2.0) for enhanced security. From that date, Microsoft started disabling Basic Authentication for the following protocols:

• Outlook
• EWS
• RPS
• POP
• IMAP
• EAS

Deploying to On-Premises Cloud Environments

When deploying on premises on Microsoft Windows, you need to add the following rule to the web.config file:

<rule name="mxecoh">
   <match url="^(mxecoh/)(.*)" />
   <action type="Rewrite" url="http://localhost:8080/{R:1}{R:2}" />
</rule>

For more information, see the Reverse Proxy Inbound Rules section of Microsoft Windows.

Configuring Local Email Clients

Configuring local clients, such as Papercut, is supported. If you are using a tool like Papercut, do the following:

1. Deploy your application to set up your Send Email accounts through the Email Connector user interface.
2. Navigate to the Email Connector Overview page.
3. Select the Send Email tab.
4. Click Add New Configuration or edit an existing one using the Action.
5. Select SMTP for the Protocol, and enter localhost for the Server host. Enter the Server port number (for example, 25).

Both email and password are not required.

Adding Attachments

Normal Attachment

To add attachments to the email message, do the following:

1. Create an Attachment entity. The Attachment entity extends the FileDocument entity by making it usable in all the places where the FileDocument entity is required.

   If you have a custom entity, extend it with the Attachment entity instead of FileDocument, or use the community commons DuplicateFileDocument function to create an Attachment from your custom entity.

2. Set the Attachment_EmailMessage association.

Inline Attachment

To add inline attachments to an email message, use the Rich text editor to insert images directly into the email body. Alternatively, you can insert inline attachments using a microflow by following these steps:

1. Create an EmailMessage with the Content property set as seen below:

   'before inline image<br><img src="cid:mxcid:test.png" width="530" height="110"><br>after inline image'

2. Specify the image's tag source using the cid:mxcid prefix before the source file to have the image added as inline image.

3. Create the attachment with the Position attribute set to ENUM_AttachmentPosition.Inline.

4. Associate the attachment with EmailMessage. You can then send the email using the SUB_SendEmail microflow.

Page Styling

If the Email Connector page styling is affected as you select and view email messages, it is likely due to errors in the email message CSS.

To resolve the errors, turn on Sanitize email to prevent XSS attacks in Account Settings.

Importing Emails with Long Attachment Names

Some email clients (for example, Gmail) break down the name of attached files if it is longer than a specific value, and add the file name in the Content Type for an attachment. This can cause an error while fetching or importing emails with long attachment names. For example: "ERROR - Email_Connector: Attribute 'Email_Connector.Attachment.attachmentContentType' has a maximum length of 200, tried setting a value of length xxx.".

Known Issues

Widgets

If you already have the included widgets in your app, and they are not up to date, you may get a "Some widgets cannot be read" error when trying to run locally.

Consistency Error

You may get a consistency error when importing the Email Connector module in Mendix 10.1 or above that states "No argument has been selected for parameter "Token" and no default is available". This can be resolved by double-clicking the error, which takes you to the snippet SNIP_EmailTemplate_NewEdit. Double-click the Edit [default] button, then in the Events field under Page settings, click Edit. Once the Page Settings dialog box opens, click OK, as shown in the image below. The error should resolve.

Duplicate Mx Model Reflection Objects in Email Template

The Email Template export/import functionality introduced in EC v5.8.0 had a bug, which was subsequently fixed in v5.9.0. If you exported and imported Email templates using EC v5.8.0, you may see duplicate records in the placeholder entity drop-down, as shown below.

To clean up these duplicate Mx Reflection records, a microflow is delivered as part of EC v5.9.2. As the cleanup microflow (DEL_DuplicateMxReflectionObjects) deletes database records from certain tables, it is strongly advised to complete a full DB backup before proceeding with the steps below. At a minimum, the following 3 tables must be fully backed up before starting.

1. MxObjectMember
2. MxObjectReference
3. MxObjectType

To perform the cleanup, follow these steps:

1. Call the DEL_DuplicateMxReflectionObjects microflow from a page using the Call microflow button. This should preferably be executed by an Admin user as a one-time activity.

   This microflow identifies and removes duplicate records from the backend. Upon completion, a pop-up dialog confirms the process has finished. The Console log displays the number of records removed from each respective table.

   

2. After completing the cleanup process, remove the Call microflow button from the page to prevent the microflow from being triggered again.