Different operators are grouped in this category.
|
This operator calculates an end date based on a start date and a duration. A Timer event is delayed by 18 hours up from the point in time that the process instance reached this event. |
|
The operator checks whether the user or user group exists in ARIS Administration. The input data is a scalar value representing either a user or a user group. If the user or user group exists in ARIS Administration, the operator returns TRUE. Otherwise, it returns FALSE. You cannot use this operator with constants of Localized string type. Constants of Localized string type can be maintained in multiple languages. |
|
Textual concatenation of values; here the concatenation between the result from the Automated task and the value of the variable Log of entire history. You can use this operator with constants of Localized string type. During execution time of the automated process, the text contained in the constant is displayed in the preferred language of a user. If you combine constants of Localized string type with constants of String type, the result of the Concatenate operator returns a string of Localized string type. The result contains all locales of the constant of Localized string type. If you combine constants of Localized string type, the result returns a string of Localized string type containing all locales contained in the single strings. |
|
This operator converts a Base64-encoded time stamp or a date into a readable string. |
|
Data OR (XOR): Uses the first available input The database name is determined by either the Human task (priority 1) or – if this returns no value – by Event (process instance started). You cannot use this operator with constants of Localized string type. Constants of Localized string type can be maintained in multiple languages. |
|
This operator identifies the user who has the specific name, user name, or e-mail address. E-mail: Standard SMTP e-mail address of type text), for example: peter.smith@company.com. The data is searched in this order: user name (person), e-mail address (person), name (role), name (organizational unit). If this input data is unknown, the operator creates a new user. The output of the operator is a reference to this user, which can be used as input for tasks of type Notification (To, Cc, Bcc) or Human task (group of executors). You cannot use this operator with constants of Localized string type. Constants of Localized string type can be maintained in multiple languages. |
|
This operator accepts automation-relevant organizational elements (e. g., roles) as input and returns the persons who belong to these organizational elements and who participated in the workflow. Example: The role Modeler consists of five members, but only one of these members has processed all of the Human tasks assigned to this role. Thus, this user is the only output of the operator Get committed resource. This operator is automatically created when a data flow of a notification function is created and the connected organizational element has the attribute Only inform people involved (connection type Must be informed about). |
|
This operator converts the technical representation of an executor into their name. |
|
The Switch operator is used to implement a decision not via the XOR branches of a process, but to shift the decision into the data flow of the function. The Switch operator has exactly three incoming slots and one outgoing slot. As input value for the topmost slot, specify a Boolean value. You can specify a variable of any data type for the other two incoming slots, but the values of the two slots must have the same data type. Normally, you must model a decision in ARIS using an XOR operator and you must model a data flow for each path. With the Switch operator you can model this over a path. The result of the decision must be a Boolean value and is entered in the first operator slot. If the first slot is set with true, the second slot is used, if the first slot is set with false, the third slot is used. |
Operators arranged in the Data elements category do not have any input parameters and behave more like functions that return specific values.