Creating a business process
In this example, you want to define a commonly encountered business process: order placement. In this example, the business process is defined as follows
- The beginning of the order placement process is defined as the moment when the visitors first add an item to their shopping basket. It also includes retrieval of a previously saved shopping basket.
- The next major step of the process is when the visitor begins the order submission sequence by clicking Checkout.
- On the next page, the visitor provides shipping and payment information.
- Following that is the final order inspection/submission page.
- If the visitor clicked Submit Order, the order confirmation page is displayed.
- If the visitor clicked Cancel Order instead, the order cancellation page is displayed.
- If the visitor clicked Continue Shopping, the visitor returned to the site's home page to continue shopping.
If order confirmation page or order cancellation page is displayed after order inspection/submission page, then it marks the end of this business process.
Example: Processing web pages
The ordering business process in this example website consists of the following sequence of pages.
- Beginning of the business process, depending on the visitor action:
- Add item to shopping basket:
/addtobasket.jsp. This step can occur multiple times, with visits to other pages in the site.For example, product search or browsing pages, other products' detail pages interspersed. - Retrieve previously saved shopping basket:
/getsavedbasket.jsp.
- Add item to shopping basket:
- Checkout page:
/checkout.jsp. - Shipping and payment information entry page:
/shipping.jsp. - Order inspection and submission page:
/confirm.jsp. - End of this business process through either of the following pages:
- Order confirmation page:
/ordercompleted.jsp. - Order canceled page:
/ordercanceled.jsp.
- Order confirmation page:
Presentation of the order canceled page or any other failure to reach the order confirmation page, represents abandonment of this business process.
- Saving a basket through
/savebasket.jspor continuing to shop for more items after the order inspection/submission page is presented does not constitute an abandonment. These events are postponement of completion of the ordering process. - Special handling is required for orders that are saved during a session but never submitted during that session. It can be necessary to define two slightly different business processes account for saving a shopping basket.
Tealeaf users can decide whether they are interested in just the workflow of submitting an order or it is friendly and usable, regardless of beginning of the order.
Checkout process scorecard
You can define per-hit events to detect the URLs listed and assign them to the sections of the scorecard. You can create events by using the preconfigured pattern to match the URL, setting the condition of each event to be one of following file names listed.
Process steps: The sequence of steps in the process is defined by events that detect the following URLs, occurring in this order:
/addtobasket.jsp OR /getsavedbasket.jsp/checkout.jsp/shipping.jsp/confirm.jsp/ordercompleted.jsp
Abandonment Step: /ordercanceled.jsp
Failure Step: Define the failure step to be a compound event by using as conditions the output of all error events that can apply to the process pages. These conditions must be configured to a logical OR evaluation.
Checkout process scorecard with advanced abandonment
This business process example creates a more sophisticated measure of abandonment. You can define the following events that are listed and assign them to the sections of the scorecard definition.
Process steps: The sequence of steps in the process is defined by events that detect the following URLs and evaluation to true if they are present.
/checkout.jsp/shipping.jsp/confirm.jsp/ordercompleted.jsp
Abandonment Step: Create an event with an End of Session trigger that evaluates all of the following things:
/checkout.jsp OR /shipping.jsp OR /confirm.jspNOT /ordercompleted.jspNOTthe failure step event (next step)
Failure Step: Create an event with an End of Session trigger that evaluates all of the following things:
/shipping.jsp AND /confirm.jsp, NOT /ordercompleted.jsp
New user registration
The following process scorecard definition can be used as a template for measuring the process for registering a new user.
Process steps: You can defined the new user registration business process in the following steps:
/registernewuser.jsp/registrationcompleted.jspIf the registration is successful, a message is included in the response:
Thank you for registering.
Define the events that are listed and assign them to the sections of the scorecard definition as shown.
The sequence of steps in the process is defined by events that detect the following URLs.
/registernewuser.jsp/registrationcompleted.jsp
Abandonment Step: Create an event with an End of Session trigger that evaluates all of the following things:
/registernewuser.jspNOTresponse contains the phrase "Thank you for registering."
Insurance policy purchase
The following business process scorecard definition monitors a simple transaction to purchase an insurance policy. You can define the following events and assign them to the sections of the scorecard definition as shown.
Process steps: The sequence of steps in the process is defined by events that detect the following pages of the application.
- Policy Holder Information
- Insured Party Details
- Review
- Notices
- Payment Information
- Payment Method
- Confirmation
- Policy Welcome
Abandonment Step: Create an End of Session event that is composed of events 1 AND NOT 8 AND NOT 6.
Failure Step: Create an End of Session event that is composed of Events 1 AND 7 AND Global Error Page AND NOT 8.