#433 Process Cloud Service - Application Roles & Admin role - who can do what during process execution

..and what they allow us to do...

I have covered the basic PCS roles, their rights and their responsibilities in an earlier post.
You can check it out here

Now to go into some more depth...
Here is my sample process -

You see the 2 app roles CSR and MGR.

 We also have the default roles -
Process Owner and Process Reviewer

Ok, so let's kick off an instance of the process...

jcooper logs in and clicks on the MySimpleOrderApp (MS) icon.

jcooper can leverage Tracking to follow the instances he has initiated -

What can the process owner see and do?

As you can see, he too sees a high level overview of issues with running instances of
which he is the process owner.

He can leverage Tracking to get process instance details -

He can take control - Approve/Reject the order etc., as well as Alter Flow.

What can the process reviewer see and do?

wshake logs in to Workspace and clicks on the Tracking tab -

He then filters by Reviewed by Me

As regarding the Approval task itself, all he can do is post a comment -

What can the admin user see and do?

The admin user, e.g. weblogic, sees the following information when she logs in
to Workspace -

As you can see, it is a high level overview of issues with running instances.

Clicking on the Alerted Tasks -

The admin opens the first alerted task to find out what went wrong -

She sees the task was assigned to an invalid user -

She can then re-assign -

#432 Process Cloud Service - Instance Tracking and Alter Flow/Resume

This is a cool PCS feature, but let's look at who can track what and
who can alter process flow and resume.

Here is my demo process -

In this scenario I have the following roles/users.

PCS admin user: weblogic
App roles as follows -

Now the flow is simple -

1. jstein enters a purchase requisition, kicking off the process.
2. vhugo does the first level approval.

jstein forgets to enter the booking start date - this will raise an error.

Initiator (jstein) does some Tracking -

He sees the instance has been suspended.

He drills down to the details -

He sees the instance has been suspended, but not why.

The Approver (vhugo) does some Tracking -

He sees nothing, nada, nichts!

The Process Owner (istone) does some Tracking -

On logging in, he sees -

There is our suspended instance -

He clicks on Tracking -

He opens the instance -

Note: the owner has Alter Flow / Resume functionality.

He sees the error message -

and naturally can take corrective action.

The PCS Admin (weblogic) does some Tracking -

and sees the same as the process owner -

The process owner Alters Flow / Resumes

Back to istone, he logs in and corrects the error and the process resumes -

  

Looks like we're back in business...

#431 - Process Cloud Services - Decisions, Decisions...

We all love making decisions and PCS makes it even easier for us -

Generate Unique Rules

My rules check whether manual approval is required for an order.

Input is the order total, output is approvalRequired (boolean).

The order total is attached to the following Value Set -

Here is my decision table -

I click on the Tools dropdown - select Generate Unique Rules

Simple yet effective!

#430 Using Postman to test PCS REST services

I installed Postman and it is now available via the Chrome App Launcher -

I execute the REST call to GET /process-definitions

I specify Basic Auth.

Easier to read than output from cURL.

Also easier to deal with adding parameters -

Here I am adding a comment to a task via REST -

Select raw for Body

Then JSON from the dropdown list -

Execute the test. Check the response -

#429 Process Cloud Service -> Decisions

Essentially we are talking about a simplified version of Oracle Business Rules here.
Yes, the rules you know and love from on-prem SOA and BPM.

To quote from the PCS docs -

Business rules enable you to automate policies, computations, reasoning, and task
assignment. Each rule has conditions (if statements) and actions (then statements).
Rules can be individual if/then statements or organized into spreadsheet-like decision
tables, in which rows represent conditions and actions, and columns match condition
values to action alternatives.

So what do we mean by Decision?

Again, the docs -

A decision is a container for if/then rules and decision tables that use the same input and output data objects. A decision exposes these data objects as a reusable service that multiple business processes can invoke.

So what does the Decision Design time UI look like?

As you can see, we have 4 tabs -

Rules - where you create your decision tables / If-Then Rules.
Note: no support here for Verbal Rules.

Value Sets - here you define lists of allowable values or ranges.

Globals - your variables, e.g.

Decision Properties - Again, to quote the PCS docs -

You can add a decision description, add decision-level actions, and view the input and
output data objects.

A decision level action could be something akin to the following -

Here I create the Rules output object.
Then all I need to do is modify it in my rule action(s).

Naturally, other actions are permissible -

If you are looking for a simple lab to try it out, then look no further -
just click here

#428 Integration Cloud Service (ICS) on OPC -> First steps

Simple procedure -

I get an email containing my account details -

Note: I have deleted Temporary Password and Identity Domain.

I click on the link to access the account.

I enter my identity domain details and click Go -

I then enter my username and temporary password -

Now, I change the password.

Specify my timezone.

And, as you can see above, I'm in.
I see the cloud services to which I have subscribed.

I open the ICS console and ergo -