Page Comparison

Consider the following Country Club Membership application workflow:

• To join the Country Club, an applicant has to be sponsored by 2 members of the club. Mary Jones calls the Club office and requests a membership application. The office worker creates a frevvo user id and password for the applicant, logs into the club's frevvo space, submits the form for first step of the workflow providing the user id and password for the applicant.
• Mary Jones gets a SetupTaskNotificationEmail Task Notification Email with link back to the club space and the information she needs to login. She logs into the Country Club frevvo space, fills out the application, attaches letters of recommendation and a photo and submits the form.
• Office workers get a task notification email informing them that a membership application task is pending for final processing.
• When the office completes the final processing, an email goes to the Chairman of the Board with all documents attached – (Application, Letters of Recommendation, photo) so he can prepare for the final meeting with the applicant. 

In this scenario, the Chairman of the Board is not informed about the applicant until all of the office tasks have been completed. This could delay the process for some time. The Country Club wanted to improve the process by sending the Chairman of the board an email with the relevant documents (application, letters of recommendation, photo) attached after the step in the workflow where the applicant completes the application. 

The Email tab can be configured to send an email  to the Chairman of the Board when the applicant submits the Candidate step (Step2) of the workflow. The application, required letters of recommendation and photo are attached to the email. Now the Chairman of the Board can review the application and relevant documents ( letters of recommendation, photo) without having to wait for the office to complete the final processing step. 

Activity Document Action Behavior for Failed Post

If the HTTP POST returns a status code 422 and an error message, frevvo interprets this code to mean that the activity in question should be re-run. For workflow steps, this means that the form for the workflow step is re-rendered. 

If you want to display a message to the user when the post fails,

1. Add a Message control with the text you want to display to the workflow step
2. Add the class f-action-error to the CSS class property of the Message control. Controls with this class are not visible when the workflow step loads, even if the Visible property is checked.
   
3. If the post returns a status code of 422 and some error text, the workflow step will be re-rendered and the Message control will display.

For example, Let's say you have a fields on the last step of a workflow step to collect a credit card number and the expiration date. The user fills in the information then clicks Finish. There is a Post Submission to a web app configured on this step.

https://<your server>/services/testhttp?status={t}&content=errortext

If the web app returns a status code of 422 and some type of error message, the workflow step will be re-rendered. The message informing the user to check the information and resubmit displays.

The workflow step will continue to be re-displayed until the post returns an Ok status (HTTP 200).