...
This section deals with the Communication Activities of the systego flowster Design Pool
...
| Table of Contents | ||
|---|---|---|
|
Contents
| Anchor | ||||
|---|---|---|---|---|
|
Communication
1.1 Activities
1.1.1 HTML Composer
1.1.2 Send Email
1.2 Workflow
1.3 Parameters
1.3.1 General Guidelines
1.3.2 HTML Composer
1.3.3 Send Email
1.4 On Execution Workflow
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
This activity substitutes a visual HTML editor.
| Anchor | ||||
|---|---|---|---|---|
|
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Variables and Arguments
In general terms of parameters in WF4, there are two main concepts: Variables and Arguments. The definitions for each are that Variables are used to store data within a workflow and Arguments are used to passing data in/out of a workflow. The concept of „binding" parameters has been replaced with the usage of variables and arguments.
Variables are to be used in a workflow whenever the need to store data is limited to the current workflow and the output/input of the workflow is not used anywhere else (for example in Admin Suite).
Arguments are to be used whenever the input parameters of an activity are given by the user using for instance a web-based application, (for example when running a workflow in Admin Portal) and if the output of an activity is to be returned and used outside of DesignStudio application . (for example Admin Portal)
All parameters that have an Expression editor in Activity Properties panel can be used for value storage and passing, through variables and arguments.
Example: Collection From String activity
Defined IN arguments, with default value to be filled in by the user when running the workflow:
Defined variables to store the output of the Collection From String activity:
Parameters with different editors, like Folder editors or ComboBox cannot be bound to variables nor arguments.
Activity Properties
In general terms of activities properties, there are two main concepts: „Stop On Error" and „Enabled".
The concept of „Stop on error" and „Enabled"mechanisms are defined for runtime purposes.
„Stop on error" Property
On runtime (nn. Start button), if the Stop on error property is set to Yes for an activity and an error or exception is thrown, the execution of the workflow stops on the activity that caused the error /exception to be thrown.
If set to No, the error message is displayed in Tracking Data panel, but the execution of the workflow continues.
„Enabled" Property
On runtime, if the Enabled property is set to Yes for an activity,the activity is executed.
If set to No, the activity will not be executed on runtime.
WF Designer panel view:
Tracking Data panel view:
Activites Parameters
| Anchor | ||||
|---|---|---|---|---|
|
...
- Content: the value stored in HTML_Output it is used for this parameter
- Subject: the value for this parameter is passed via IN argument Subject
- File attachments: 1.jpeg has been attached to the email:
...