Jarvis Pizzeria: The Document Only Delivery Process

Let's have a look at the Delivery Process of the Jarvis Pizzeria. In this blog post, we will explain the functionality of the Delivery Process with the help of the Document Only feature when creating a new process.

When we create a new process we can select the option ‘Document Only’ in the Create Process popup.

Document Only processes are for descriptive use only and are not part of the working and running application. It is a good way to setup a process to discuss with your peers, users, architects or anyone else. One of the advantages of starting a document only process is that it will not check whether it is valid or not, since it is for descriptive purposes only.

In the Process Overview within the Application, we recognize the Document Only process with the subtle difference of having a dotted line within the thumbnail instead of a solid line.

The flow of the Delivery Process is as follows, we start with a service call to obtain the order information. The process will then decide whether it is a takeout or delivery order. When the order is a takeout, a Human Task will be generated to announce the order to the waiting customer.

In case the order needs to be delivered, we will use a decision model to determine what kind of vehicle to use for the order, then a Human Task will be generated to do the delivery.

While the customer is enjoying their pizza, the process continues. It will retrieve the customer info with a service call after which we will check if the customer is a regular at Jarvis Pizzeria. If so we will add points for the order to the customer account. If not, we will try to contact the customer with our amazing offers for regulars.

Last but not least we will wrap up the delivery, by sending some information back to the system about the delivery.

 

That’s quite the story, but luckily we can show this process in a picture as well. The Document Only Process of the Delivery Process looks like the following picture. As you can imagine, that is a lot easier to talk about than the describing text.

When we start to implement the process, we first need to uncheck the Document-Only checkbox. For this we need to go to the Process Properties within the Process Editor. On the tab Implementation, you can uncheck the Document-Only checkbox.

This will result in a changed thumbnail as well in the Process Overview within the Application.

The Document-Only feature is an effective way to describe a process and to share where we are working on among each other as well as with the audience. It takes over some of the functionalities from the on-premises BPM Composer, without the hassle of sharing your assets with PAM (Process Asset Manager).