DevOps process run plan

Time to run our new devops testing process by submitting three different jobs (but you can do more!):

  1. 50 lines of code (up to 50, no peer review)
  2. lines of code > 50 (peer review needed and user task approves job)
  3. lines of code > 50 (peer review needed and user task rejects job)

Build and deploying the project

Now let's deploy the devops testing project:
  • click on top right DEPLOY button
  • If all goes well you'll see a green pop-ups verifying the deployment
  • Note that deploying also triggers a build

Examine deployed process definition

Let's take a look at the process definition deployment:
  • select at top: Menu -> Manage -> Process Definitions

Process definition list view

This opens the Manage view pane where you'll see our devops testing process definition. Later you can use the drop-down menu at the top to jump between different views. We're going to open the process definition by clicking on it:

Starting first instance run

Our first process we want to run a job with 50 lines of code and it should proceed down the happy-path like this (greyed out nodes indicate processed path):

Starting a process instance

This view offers choice of definition details or image of the process. Start a new process instance by clicking on the button top right corner New Process Instance:

Welcome to your start process form

You'll see your designed start form pop-up, add data (ensure lines of code is set to 50) and SUBMIT:

Straight through processing

A green pop-up displayed the process id, now note the Instance State marked as completed because we took the happy path through the process. Straight through processing (STP) indicates fully automated process completion:

Viewing process instance diagram

Select the Diagram tab for visual status of the completed process instance. This is exactly what we expect for 50 lines of code:

Starting second process run

Our second process we want to run a job with more than 50 lines of code and it should proceed down the path requiring peer review user task, which we'll approve like this (greyed out nodes indicate processed path):

Starting the second instance

Go back to the process definition details and start a new process instance by clicking on the button top right corner New Process Instance:

The start process form again

You'll see your designed start form pop-up, add data (ensure lines of code is set to 51) and SUBMIT:

Second instance active details

A green pop-up displayed the process id, now note the Instance State is ACTIVE:

Examine second instance diagram

Select the Diagram tab for visual status of process instance. It's exactly what we expect for lines of code = 51, the rules check requires a peer review (red box indicates location):

View the waiting user task

Locate our peer review task in the task inbox:
  • navigate by clicking on top MENU
  • under Track click on Task inbox

Task inbox list view

The task inbox has your Peer Review task listed, just click on task entry to open:

Claim the peer review task

The task form for Peer Review is presented and before you can work on it you need to Claim it, removing it from the queue so other Managers can't work on it:
  • click on CLAIM

Start the peer review task

The task is now ready for the next stage, so click on START to being the task and make the form editable:

Complete the peer review task

Time to evaluate the form data and process this task by marking it approved:
  • check the box Approval
  • submit with Complete

View peer review in task list

The task is no longer in the inbox. That's due to the filters at the top (blue items), so let's remove them to view completed task:

Viewing second instance in list

If all went well our process instance is completed, so let's check:
  • open the process instance list by clicking on button View process

Review second instance diagram

Open the Diagram tab and view the diagram of the completed process instance, it should look like this:

Starting third (final) process run

Our final process run is a job with more than 50 lines of code and it should proceed down the path requiring peer review user task, which we'll reject like this (greyed out nodes indicate processed path):

Starting the third instance

Go back to the process definition details and start a new process instance by clicking on the button top right corner New Process Instance:

The (final) start process form

You'll see your designed start form pop-up, add data (ensure lines of code is larger than 50) and SUBMIT:

Third instance active details

A green pop-up displayed the process id, now note the Instance State is ACTIVE:

Examine third instance diagram

Select the Diagram tab for visual status of process instance. It's exactly what we expect for lines of code = 100, the rules check requires a peer review (red box indicates location):

Viewing the waiting task

To find our peer review task we need to look in our task inbox:
  • navigate by clicking on top MENU
  • under Track click on Task inbox

Task inbox list view

The task inbox has your Peer Review task listed, just click on task entry to open:

Claim and start peer review task

Let's take task Peer Review and click through CLAIM, START:

Complete peer review task (diapprove)

Time to evaluate the form data and process this task as not approved:
  • do NOT check the box Approval
  • submit with Complete

View peer review in task list

The task is no longer in the inbox. That's due to the filters at the top, so let's remove them to view completed tasks (note there are a few listed):

Viewing third instance in list

If all went well our process instance is completed, so let's check:
  • open the process instance list by clicking on button View process

Review third instance diagram

Open the Diagram tab and view the diagram of the completed process instance, it should look like this:

Viewing business logs

To verify the logging, see Logs tab, but it's business level logging only:

Viewing developer logs

Let's check the server logs, go to console used to start from:
  • we see there the entire run of our process including the logging
  • the second part is after user task peer review completed

Lab sub-goal

To view and explore available process and task reports

Viewing process automation reports

Data gathering from processes and tasks can be found in reports:
  • open Menu -> Track -> Process Reports
  • initial process reports lack data, explore now for reference

Viewing user task reports

Let's look at the task reports:
  • Now open Menu -> Track -> Task Reports
  • Feel free to start and complete more process instances

The end of the workshop

...or is it?
Eric D. Schabell
Portfolio Architect Director
@ericschabell
http://schabell.org
Other Red Hat Process Automation Manager Workshops

Red Hat Process Automation Manager Articles

Red Hat Process Automation Manager Demos: