| Section | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
HTTP Wait-Notify is a new type of activity that can be added to a flow. It is configured with a post url. 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. YYou can send data back to the flow in the POST payload to the frevvo.notifyUrl callback. It must be an XML document that conforms to the flow's schema. Click the "Schema" button on your flow to download the XSD that the XML document must conform to.
The timezone must be added programmatically by the service you are using. HTTP activities can be performed by an anonymous user.
Let’s 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 Wait-Notify can be added to the Live forms 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.
...
Email activities can be performed by an anonymous user.
- An anonymous activity cannot be performed twice. If you click the link again, it will give you an error.
- The anonymous email activity 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.
- There is currently no way for an Anonymous recipient to Reject a flow. This will be added in a later release. The workaround is to send it forward to the internal employee for review and that internal employee can reject it all the way back to the first step.
If navigation is used to go to previous activity, the EMail activity will be skipped. It would get recalled if you reset to a prior step and the flow continues thru it's normal flow.
Configure a History Message on the activity before the Email activity 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.
Email Properties
When you drag/drop an Email activity into your flow and click on it, a Properties panel displays. The Name, Pending Message and Decorator properties work exactly like they do on other types of activities. Task Info and Precondition do not apply and 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 Email activity in the flow.
Activity Doc Actions work exactly like they do on other types of activities.
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 activities 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 Activity
Consider a flow with the following navigation: Step 1 is performed by an Employee > Step 2 is an Email activity > 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 activity is performed again and another email will go to the anonymous user.
The same behavior applies to a flow with an HTTP activity.
Searching Tasks with an Email Activity
...