Definition
Notification Definition allows to configure the Notification (content, recipients…) that will be sent by Memority.
Configuration
You can access the Notification configuration :
-
by clicking on "Notifications" → “Emails” or Notifications" → “SMS”
-
by clicking on "System" → "Configurations" → "Notification Service" and perform an import/export.
Global Properties
|
Domain |
Code |
|---|---|
|
Version and encoding : Each Email Definitions starts by announcing the version and the encoding. |
XML
|
|
DataSet: Each Email Definitions starts by announcing the DataSet. |
|
|
Notify |
Notification Definition Properties - Common to Email & SMS
|
Property name |
Type |
Mandatory |
Description |
Values (default value in bold) |
|---|---|---|---|---|
|
id |
|
YES |
The id is the unique identifier of the Notification. It is case sensitive and no special characters (except - or _) are allowed. |
- |
|
name |
|
YES |
The Notification name. The name may be different from the identifier.
|
- |
|
defaultLanguage |
|
NO |
Used to define a default language |
|
|
description |
|
NO |
Used to describe the Notification that will be configured. |
- |
|
eventType |
|
YES |
Allows to define a Notification type which corresponds to a specific business use case. Only one event type on each Notification. |
All events types are listed below. |
|
|
YES |
Allows to list all recipients. |
- |
|
|
sender |
|
YES |
Allows to determine who send the notification. |
- |
|
textBodyTemplateId |
|
NO |
Allows to provide a Notification Template Id for a text message |
|
|
|
YES |
Allows to define different contents. |
- |
Recipients
|
Property name |
Type |
Mandatory |
Description |
Values (default value in bold) |
|---|---|---|---|---|
|
recipient |
|
YES |
Allows to determine actors of the notification. The value can be an :
|
requester, system, beneficiary, identity, subject |
Contents
|
Property name |
Type |
Mandatory |
Description |
Values (default value in bold) |
|---|---|---|---|---|
|
|
YES |
Allows to define a specific content in French and/or in English. |
- |
Content
Each content will have the following configuration:
|
Property name |
Type |
Mandatory |
Notification Type |
Description |
Values (default value in bold) |
|---|---|---|---|---|---|
|
locale |
|
YES |
ALL Notifications |
Allows to define the language of the email. |
- |
|
htmlBody |
|
YES |
email only |
Allows to define the body of the email. |
- |
|
subject |
|
YES |
email only |
Allows to define a subject for the email. |
- |
|
textBody |
|
YES |
ALL Notifications |
Allows to define the text of the email. |
- |
Notification Definition Properties - Email
|
Property name |
Type |
Mandatory |
Description |
Values (default value in bold) |
|---|---|---|---|---|
|
id |
|
YES |
The id is the unique identifier of the Notification. It is case sensitive and no special characters (except - or _) are allowed. |
- |
|
name |
|
YES |
The Notification name. The name may be different from the identifier.
|
- |
|
defaultLanguage |
|
NO |
Used to define a default language |
|
|
description |
|
NO |
Used to describe the Notification that will be configured. |
- |
|
eventType |
|
YES |
Allows to define a Notification type which corresponds to a specific business use case. Only one event type on each Notification. |
All events types are listed below. |
|
|
YES |
Allows to list all recipients. |
- |
|
|
sender |
|
YES |
Allows to determine who send the notification. |
- |
|
reply |
|
NO |
Allows to provide a reply email address. |
|
|
textBodyTemplateId |
|
NO |
Allows to provide a Notification Template Id for a text message |
|
|
htmlBodyTemplateId |
|
NO |
Allows to provide a Notification Template Id for an HTML message |
|
|
attachments |
|
NO |
Allows to add one or more attachments. |
- |
|
ccs |
|
NO |
Allows to add one or more actors in copy. |
- |
|
ccis |
|
NO |
Allows to add one or more actors in hidden copy. |
- |
|
|
YES |
Allows to define different contents. |
- |
Notification Definition Properties - SMS
|
Property name |
Type |
Mandatory |
Description |
Values (default value in bold) |
|---|---|---|---|---|
|
id |
|
YES |
The id is the unique identifier of the Notification. It is case sensitive and no special characters (except - or _) are allowed. |
- |
|
name |
|
YES |
The Notification name. The name may be different from the identifier.
|
- |
|
defaultLanguage |
|
NO |
Used to define a default language |
|
|
description |
|
NO |
Used to describe the Notification that will be configured. |
- |
|
eventType |
|
YES |
Allows to define a Notification type which corresponds to a specific business use case. Only one event type on each Notification. |
All events types are listed below. |
|
|
YES |
Allows to list all recipients. |
- |
|
|
sender |
|
YES |
Allows to determine who send the notification. |
- |
|
textBodyTemplateId |
|
NO |
Allows to provide a Notification Template Id for a text message |
|
|
|
YES |
Allows to define different contents. |
- |
Example
Notification Events Type
Objects
MyMfa
Password
Public Access
Workflow
Synchronization
Roles
AM
Others
Example
Domino_with_Simulation_tag.xmlOrga_Patch.xmlRole_Assignment.xml
Reuse an Email Templates
An Email Template can be reused in the html Body and/or in the text Body by using this syntax:
|
Property name |
Code |
|---|---|
|
htmlBody |
XML
|
|
textBody |
Read Next
-
Notification Definition -
Notification Template The Email Templates are useful to be reused in the configuration of Notification Definition (for example: greeting).
-
Notification Service