...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| 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.
...
| Note | ||
|---|---|---|
| ||
Use of the Anonymous Task step requires that the ACL for "who can use the flow" is set to Pubic Public. This is because your flow now contains a step that is performed by a person who is not an authenticated user - someone who is not logged into Note: If you want to control who can use the flow, then set a role(s) on the first step of your workflow. |
...
Anonymous Task steps are performed by an anonymous user - the user is not required to sign into .
- The behavior of workflows consisting of multiple consecutive anonymous steps has changed. Refer to this Multiple clicks on an Anonymous Email link for the details.
The Anonymous Task step will show up in the navigation bar for other users as usual; you can assign it a decorator but you cannot click on it.
The task will show up in the Audit Trail in the Waiting state when it is waiting for an anonymous recipient. You can search for it, do all the usual things.
Users can reject Anonymous Task steps in a flow by clicking the Reject button but a subsequent user cannot reset a flow back to these steps. See the topic below for more information.
If the Navigation Toolbar is used to go to previous step, the Anonymous Task step will be skipped. It would get recalled if you reset to a prior step and the flow continues through it's normal flow.
The Navigation Toolbar can be used to navigate to a previous step in a screenflow performed by anonymous users. See Anonymous Screenflows
Configure a History Message on the step before the Anonymous Task step if you want to see relevant information in the audit trail. The History Message can be templatized so you can see the email address of the recipient.
If you are setting up Escalations on an Anonymous Email step and you choose to send emails to your users to let them know that the deadline for the task is approaching, change the default template {task.perform.url} to the {task.notify.url} template in the body of the Reminder message on the escalation screen. See the Reminder Message Template for Anonymous Task step for the details.
- Confluence users must set the flow to public and allow anonymous access to your Confluence page. The only way for anonymous users to access the flow task from is to use the built-in {task.notify.url} function.
Anonymous Screenflows
| Expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
...
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 Anonymous Task step
Consider a flow with the following navigation: Step 1 is performed by an Employee > Step 2 is an Anonymous Task 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. If the manager is also a flow admin, they can reset the flow to a previous step
- A flow cannot be reset to the Anonymous Task step. In this example, only a reset to the employee step is allowed.
- The task is returned to the Employee Task List. When the employee performs the step again and clicks Continue. The Anonymous Task 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 Anonymous Task step
...
The Form Viewer control is used to allow a generated PDF to be viewed as part of a form step in a flow. This control only appears on the Forms palette in the flow designer when you click the icon to edit an step in a flow.