Versions Compared

Key

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

...

Consider this scenario. Your company has a purchase process workflow. One of the steps in the workflow requires approval from several other approvers before the flow can continue to the next step. These approvals should happen in parallel and not one after the other. A web component that would manage those approvals is in place. An HTTP step can be added to the Live forms frevvo flow with a URL to the web component to collect the signatures. The callback URL will be included in that post. The flow will be suspended until all the signatures are collected. The remote web component will notify the Live Form flow using the callback URL when the signature task is completed. If the HTTP step in the flow has doc actions configured, they will be performed and the flow will proceed to the next step.

...

This URL is used by the remote service to “wake” up the Live Forms frevvo flow.  Any document actions configured will be performed and the Live Forms frevvo flow will resume. Flow visibility can be set to any of the choices. 

...

Configure a History Message on the step before the http step if you want to see relevant information in the audit trail.  

Excerpt
hiddentrue

Anonymous Task

Note
titleImportant Design Fact

Use of the Anonymous Task step requires that the ACL for "who can use the flow" is set to 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  

Frevvoproduct

Note: If you want to control who can use the flow, then set a role(s) on the first step of your workflow.

Info

Frevvoproduct
 offers the flow designer many ways to send emails from workflows. You can:

...

  • frevvo login (anonymous user) - discussed below:

The Anonymous Task in the flow designer palette is ONLY used to route a workflow to someone who does not have a 

Frevvoproduct
 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 

Frevvoproduct
.  

The Anonymous Task step allows the design of a flow where some steps are performed by authenticated users/roles and other steps are performed by an anonymous user. The anonymous user receives an email, clicks on a link in the email and accesses the task without being authenticated, performs the anonymous step, clicks continue, and the flow is routed back to an internal, authenticated user. The flow is suspended (saves the flow to the database), sends an email to the specified email address with a back link. The anonymous user clicks the link email and the flow renders even though he/she is not logged in. 

A typical situation is an employee who submits a request to an outside vendor for a quote, which then needs to be approved by the employee's manager. The Anonymous Task step of the flow sends an email to the vendor, the flow is suspended until the vendor submits his quote, then the flow continues for the manager's approval. The Vendor Quote Workflow Tutorial consists of step by step instructions to completely build/test a workflow that uses the Anonymous task step.

The Vendor Quote workflow, shown in the image, has 4 steps:

  • Step 1 is the Vendor Quote request filled in by someone in the company with the employee role. The Employee role was selected from the role list for this step.
  • Step 2 of the flow sends an email to the vendor. The Anonymous Task step was dragged from the palette and dropped into the flow. This step must have an email address. It can be filled in by the user or populated via a business rule. In this case, the value of the control named VendorEmail will be used to determine the email address to send to. VendorEmail is an example of a template. An email is sent to the email address in the VendorEmail control with the link back to the flow.
  • Step 3 is what the vendor sees when the link inside the email is clicked. The step that goes to the anonymous user cannot have a role, dynamic role or user assigned to it. This step is really a section in the main form that is shown only when step 3 is being performed. The Vendor and Manager sections are shown/hidden using a business rule. The flow is suspended until the vendor completes his section. In a future version of
    Frevvoproduct
    , the amount of time the flow remains suspended can be configured. 
  • Step 4 is the Manager Approval step. After the vendor submits the quote information, the flow proceeds to the manager step and puts the Vendor Quote Task on the Task List of the employee's manager .  The manager can approve/reject the quote. If approved, the flow is completed.

Image Modified

Here is what it looks like when the flow is performed:

Image Modified

When the Vendor clicks on the link, the relevant parts of the flow are shown. The notify URL automatically adds the timezone from the browser.

Image Modified

The manager approve/rejects the flow from his Task List. Any configured Form/Doc actions , such as a display message, will execute. If the manager approves the task, the workflow is complete. Note the Vendor Quote step in the flow is greyed out.

Image Modified

Some Tips about Anonymous Task steps

  • Anonymous Task steps are performed by an anonymous user - the user is not required to sign into

    Frevvoproduct
    .

  • 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

    Frevvoproduct
    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
titleClick here to for the details...

Excerpt Include
Flow Setting Properties
Flow Setting Properties
nopaneltrue

Anonymous Task Properties

When you drag/drop an Anonymous Task step into your flow and click on it, a Properties panel displays. The NamePending Message, Precondition and Decorator properties work exactly like they do on other types of steps. Task Info doed not apply to an Anonymous Task. If you want to set up a History Message you must do so on the step in your flow that the anonymous user is going to see.  Note the envelope decorator to identify the Anonymous Task 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

View Tasks when a step is performed by an Anonymous User

 

Imagine a Software Order workflow where Step 1 is filled in by the company Sales Rep who then sends it to the customer for approval/signature via email. The Software Order is waiting for client review/signature and the Sales rep wants to view the details before the client signs and sends it back to Sales rep.

 

If your workflow was created in a version of

Frevvoproduct
previous to v8.0, then the step performed by the customer (anonymous user) was designed by dragging an EMail or Anonymous Task step from the Palette and dropping it on the Flow Designer canvas. Workflows designed in this manner will still work in v8.0 but the Audit Trail will show the task in a WAITING state when the Sales Rep clicks on the Image Modified View icon.

 

In version 8.0, the same flow can be designed by simply assigning the step to an Email Address. When the Sales Rep clicks the Image Modified View icon, shows the step performed by the customer (anonymous user) in a Pending state and displays the Email address it was sent to.

 

Image Modified

 

In all cases, the Sales Rep will see a read only view of the Software Order that they filled out and sent to the customer.

Image Modified


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.

 Image Modified

 The same behavior applies to a flow with an http step. 

Searching Tasks 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.

  • The flow has been started and the notification email has been sent.
  • The flow is now in the WAITING state.
  • The Employee can search for a status of WAITING and view the audit trail. If the employee is also a flow admin, they can reset the flow to a previous step

Image Modified

  • The tenant admin can search for a status of WAITING, reset the flow to a previous step, abort it or view the Audit trail. 

Image Modified

The same behavior applies to a flow with an http step. 

Anonymous Task Steps and the Reject Feature

If a Reject feature is configured for a workflow, non-admin users can send the workflow back to a previous step. For example, a Manager can send the workflow back to an Employee for corrections. If the workflow contains an Anonymous Task step, the anonymous user can reject the task but it is not possible to reject back to the Anonymous Task step from subsequent steps in the workflow.  

Form Viewer Control

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 Image Modified icon to edit an step in a flow.

...

 

 

...