See Variables for an introduction.
The Case variable contains the data that starting a case creates. This variable has several fields. You cannot change most of this data, except for the case name and due date.
An email has a composite type, with the following properties.
||Text||Entered or generated editable name|
||Number||Sequential case number|
||User||User who created the case|
||Date||Date and time the Creator started the case|
||Date||Optional editable due date|
||Text||Case priority - values
||Text||URL of the case page in Signavio Workflow Accelerator|
||Duration||The duration the case has been open|
||Text||The last milestone the case has passed|
The case variable’s ID uniquely identifies this case among cases for all processes.
The Name field stores the name that either the Creator entered manually, or that Workflow Accelerator generated. Case participants can edit this name. You might use the case name variable in a Send email action configuration, to send emails that clearly identify their context by prefixing the subject line with the case name.
The Number field stores a sequential case number. Each process uses a separate case number sequence for its cases. In a Handle customer order process, you could use the case number as a generated order reference, for example.
The Creator field records the Workflow Accelerator user who started the case. The User type includes name and email address fields, so you can use the case creator to configure a Send email action that automatically notifies the requestor of an approval process’ result.
The Start date records when the Creator started the case. In an order process, for example, you could use this as the order date.
Trigger email variable¶
The Trigger email variable contains the email that started the case, for processes that have an Email trigger. You can use this variable to use information from the email that started the case during the process, and to send email to the sender.
This variable has the fields that the Email type defines. You cannot change their values.
Variables store workflow information. Each variable has a user-defined name and a type. A type can represent a single value, like text or an email address. ‘Composite’ types such as user, file or email consist of several values.
When using expressions or configuring some action, you refer to workflow data. This can use references to variables, or to fields inside composite variables. The user interface guides you and shows the options you have.
The Choice type stores a text value from a fixed list of configured options.
The Date type stores a date, or a date and a time of day.
The email type stores an email, which the email trigger uses. A variable stores the email that triggers the process. You can use the email’s data fields, such as from address or the attachments, later in the process.
An email has a composite type, with the follow properties.
||ID||The unique identifier for this email|
||Email address||The sender email address|
||Text||The sender’s display name (optional)|
||List of Email address||The email addresses of the recipients|
||Email address||The email address to send replies to (optional)|
||List of Email address||Email addresses that receive a copy of the message (optional)|
||Text||The subject of the email (optional)|
||Text||The plain text message (optional)|
||Text||The HTML code for an HTML email (optional)|
||List of File||The files to attach to the email (optional)|
The email address type stores an email address.
The file type stores a file.
||ID||The unique identifier for this email|
||Text||The file’s media type|
||Text||The file’s name|
||User||The user who uploaded the file|
An ID has special kind of string type.
Workflow Accelerator creates these IDs to identify objects; they have no other meaning.
An ID string looks like
A list simply represents a collection of values. The list has an order and all elements have a single specified type.
The Money type stores a currency amount for a particular currency.
The Number type stores a number.
Objects have a composite type, with a list of named fields.
For example: a user has an object type,
with fields such as
The Text type stores plain text.
A variable of type user refers to a user in your organization. A user has an object type, with the following properties.
||ID||The unique identifier for this user|
||Email address||The user’s email address|
||Text||The user’s first name|
||Text||The user’s last name|
The Yes/No Checkbox type stores a single value that represents either Yes or No.