Control access to process instances

1
0
-1

Hello,

I have a question on controlling access to process instances.

Let's take this organization:
-General Manager
-Office 1 (reporting to General Manager)
-Office 2 (reporting to General Manager)

I have only one process designed and available in the Bonita Portal.

Ho can I make sure that Office 1 can't access instances(running or finished) of processes assigned to Office 2?

Thanks

4 answers

1
0
-1

Right, I think I now have what you're looking for.

The way I would do this is as follows:

"First part of the process" - Global process - a procurement process
In this global process I pull the relevant details for franchise/user in the OUT Connector

I would then assign the "second" part of the process to the local administrator team for actioning. This would be done by creating an appropriate Actor Filter for the which is based on the franchise/user information gathered in the first part of the process (the global procurement process).

So What's important here:

  • the design of the organizational fields for reference (using custom fields?), and
  • the need (in all cases) to explicitly assign the cases to the appropriate franchise rather than letting them float.

We actually do both what you're asking and separating the processes. We have found some states have different laws that effect our processes and because DMN (Decision Management Notation) is not part of Bonita as yet we make things easier by creating separate processes for each state.

In summary then:

  • Process "Start Procurement" - this is a floater which every franchise can start
  • Process "next step/process" - these MUST be explicitly assigned to the franchise in question using an appropriate Actor Filter which you will have to write yourself.

regards
Seán

PS: If this reply answers your question, please mark as resolved.

1
0
-1

hello,

I thought I already answered but can't find it.

Thanks for your feedback but it is not responding my question.

My context is very common, I have the same process that should be instanciated in many organizational units.

Here is an example:
Franchising Business:
We have a procurement process that can be instanciated by every store from the franchising firm. We do not want a franchise to access the processes instances from other stores.

It is not possible to do this natively with Bonitasoft?

1
0
-1

Hello Sean,

sorry for the late asnwer, I just seen now your feedback.

My point is exactly to not do what you are offering.
It is very common practice in company to have the same process not accessible to the whole list of person having the same role.

Let me take a first example: A franchising company:
-All the stores have the same process to interact with head quarter(f.i.: a procurement process).
Every store should have it's own list of processess open, closed available, he should not access the processes instances from other stores.
Are you telling me that Bonitasoft does not provide this feature natively?

Thanks

Johann

1
0
-1

if it is exactly the same process why would you want to?

BPM isn't designed like what you want. Roles do jobs and if they are the same roles and processes then so be it.

You could take the simple route of course, which would do what you want.

I'm imagining the process is a National process so Office 1..X can do it.

Create (for example) process New York and assign New York officials to this process only. then create
process Boston and assign Boston officials to this process only.

This will work.

2 things though.

You will be maintaining 2 processes for changes (bad)
You will be maintaining 2 processes for different locations (good) as they might have different legal (process) requirements.

What do you want to maintain? 1 big humongous process covering all office requirements, or multiple smaller office specific requirements.

I know what I would want to do...

regards
Seán

PS: If this reply answers your question, please mark as resolved.

Notifications