| Section | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Previously completed steps in a workflow can be viewed by all users but editing data is only allowed for the user that initiated the flow. For example, if the Summary step is part of a screenflow performed by the same user, editing is allowed when this user clicks on the Details button. Once the flow navigates to a different user, previous steps are rendered read-only and cannot be edited. Refer to Flow Processing Modes for more information.
The Print button is available on Summary steps by default. Refer to Printing Flows for the details.
The designer can specify a CSS class, a Button label and a Decorator for the Summary step on the Settings property tab.
The fields that display on the Summary Step are selected by the designer in the Summary wizard.
http Wait Notify
http Wait-Notify is a step, configured with a post url, that can be added to a flow. The flow data is posted to this url when the task is executed. A call back url is included in the post. The flow and task are suspended until the receiver posts back.
...
Configure a History Message on the step before the http step if you want to see relevant information in the audit trail.
Anonymous Email
| Info |
|---|
offers the flow designer many ways to send emails from workflows. You can:
The Email in the flow designer palette is ONLY used to route a workflow to someone who does not have a login(anoymous user). It does send an email to the anonymous user that contains a link to the step in the flow that the anonymous user performs. The anonymous user completes the step and then the workflow is routed back to a user who must login for the workflow to continue. Examples of workflows that would have an anonymous email step would be a request to an outside vendor for a quote, or a Purchase Order that is sent to the customer for approval. Refer to the Flow Tutorial for step by step instructions to implement this feature for a Purchase Order workflow. |
...
|
Many business scenarios require a step in the workflow to be performed by a person who is not an authenticated user - someone who is not logged into .
...
Step Doc Actions work exactly like they do on other types of steps.
When you click on the step in your flow that is seen by the anonymous user, a Properties pane displays. Several of these properties, do not apply to a task performed by a non-authenticated person and will have no effect. These properties are: Role List, Role, User, Task Info, CSS class, Preconditon, Save Load, Save to Role, and Save to User and . You can customize the button label, history message and select a decorator for this task that will display on the Navigation toolbar.
The Task Notification Email wizard also works exactly like it does on other types of steps except that the default message content is slightly different. It references {task.notify.url} which is the back link URL that the non-authenticated person clicks in the email to perform their step in the workflow. The designer can customize this message however, if you don't include the {task.notify.url} in your email content, the email recipient will never be able to access the task.
Resetting a Flow with an Email step
Consider a flow with the following navigation: Step 1 is performed by an Employee > Step 2 is an Email step > Step 3 is performed by an Anonymous user > Step 4 is performed by a manager.
- Employee starts flow, email gets sent, the anonymous step is performed and a task is generated for manager.
- A flow cannot be reset to the Email or Anonymous user step. In this example, only a reset to the employee step is allowed.
- The Employee performs the step again and clicks Continue. The Email step is performed again and another email will go to the anonymous user.
The same behavior applies to a flow with an http step.
Searching Tasks with an Email step
...