File
This type of event is available only for on-premises installations, as they require access to resources on the client's computer.
The properties panel of the start event per file 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
This property is checked when the event activates, waiting for the file.
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 |
|---|---|
Name of the event initiator file, without the extension |
Name of the event initiator file Contains "Ticket" |
Name of the folder that contains the event initiator file |
Name of the folder that contains the event initiator file Equals "Receipt of Tickets" |
File extension (without dot) |
File extension Equals XML |
Event initiator file path |
Event initiator file path Equals "C:\Claims\Tickets Attention" |
Folder path that contains the event initiator file |
Folder path that contains the event initiator file Equals "D:\Claims Attention" |
Number of file days elapsed |
Number of file days elapsed Greater than or Equal to 9 |
File type (File or Folder) |
|
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 a file to the case.
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 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.
