Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column

’ flow palette contains all of the forms you have already created in the Forms tab of the application you are currently editing. These forms are available for you to add as steps of the flow. The palette also contains a new form which lets you create a new form step directly within the flow designer. Additional step types for flow steps are Summary, http and Email. The purpose of each is described below.

Column
width240px

On This Page:

Table of Contents
maxLevel2

...

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.

Image Modified

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.

...

  • Email 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 email 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 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 navigation is used to go to previous step, the Email step will be skipped. It would get recalled if you reset to a prior step and the flow continues thru it's normal flow. 

  • The Navigation Toolbar can be used to navigate to a previous step in a screenflow performed by anonymous users.

    Expand
    titleClick here to for the details...

    Insert excerpt
    Flow Setting Properties
    Flow Setting Properties
    nopaneltrue

  • Configure a History Message on the step before the Email step if you want to see relevant information in the audit trail. The History Message can be templatized so you can see who 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 Email 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.

Email Properties

When you drag/drop an Email step into your flow and click on it, a Properties panel displays. The The Name,    Pending Message and Precondition and Decorator properties work exactly like they do on other types of steps. Task Info and Precondition do  does not apply and if to an EMail step. If you want to set up a History Message you  you must do so on the step in your flow that the anonymous user is going to see.  Note  Note the envelope decorator to identify the Email step in the flow. 

 Step Doc Actions work exactly like they do on other types of steps. 

Image Modified 

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.  

  Image Modified

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.

  Image Modified

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

...