i
The properties panel of the start event by email is displayed on the right side of the process modeler.
Properties
Name
Text that is displayed in the diagram next to the graphic element of the event.
It is recommended to inform a text in reference to the email expected to be received.
Enabled
Indicates that the event is enabled to receive emails and execute if applicable.
Priority
Execution priority assigned to the event. It is reported as an integer, with 0 being the highest priority. If the event performs the action mark event as processed, events with lower priority are not executed.
Description
Text that allows documenting detailed information about the event.
Conditions
They are the conditions that must be met for the event to be executed. If there are defined conditions, a list of them is displayed.
To add a condition, press the icon and from the panel that opens, select Property and Operator in the corresponding drop-down lists. Report Value and where applicable, indicate in Parameter the field to be evaluated of the form associated with the process.
Property |
Example |
---|---|
•Email subject •Email text |
Email subject contains "Information request" |
•Email sender •Email recipient |
Email sender Equals AtencionConsultas@Deyel.com
More than one address can be reported separated by ; ( semicolon ) without leaving spaces |
•Name without the attachment extension in n position (starts at 1) •Attachment extension in n position (starts at 1) |
Name without the attachment extension in n position starts with "Sheet", indicated in parameter 1 ( first position) |
•Number of email days elapsed |
Number of days elapsed Equals 3 |
Actions
They are the actions that are carried out automatically when the event occurs.
•Create Case
For all start events, a case is compulsorily created for the process and a version in which the event is executed.
•Attach file
Allows to attach one or more files to the case.
Parameter |
Description |
---|---|
Email attachment |
Position number of the email attachment that is attached to the case. (*) |
Depends on the previous execution |
Indicates if the action is executed only when the previously defined actions were executed successfully.(*) |
Note: The parameters selected with (*) are mandatory.
•Attach form
Allows to relate a form to the case.
Parameter |
Description |
---|---|
User Code |
If it is not reported, the current user is assigned. |
Values map |
Report <field1><value1><field2><value2>…, |
XML |
File path that contains the XML. |
Annex Type |
Annex type attached (*). |
Create version if it exists and if it is unique |
If when attaching the form, it already exists and is unique, a historical version of it is previously created. |
Reset previous form and it is unique |
Indicates that if there is a form associated with the case and it is unique, data is deleted from it. |
Depends on the previous execution |
The action is executed only if the previously defined actions were executed successfully.(*). |
Note: The parameters marked with (*) are mandatory.
An automatic response is sent to the email received indicating that it has been processed.
Parameter |
Description |
---|---|
Depends on the previous execution |
Indicates if the action is executed only when the previously defined actions were executed successfully (*). |
Note: The parameters marked with (*) are mandatory.
Example of Use
The "Register Email Contact" process starts its execution automatically when an email arrives to the email account established in the environment configuration, under the title "Invitation to Deyel Webinar" and the word "Agree" is in the content.