Make Permission model for Developers and IT teams more flexible
330
Views
3
Comments
New
Service Center

The problem i would like solved:

We have recently created different Teams in our Outsystems development structure. 

This has lead to the inability to handle BPT processes (Terminate, suspend, etc.) in Service center, for processes from our own applications.

Since we have dev ops in our scrum team, we need to be able to handle these kind of application related features ourselves.

So the idea is to make the Permission model a bit more flexible so companies can change some permissions in roles to fit the needs of their organization.

Hi Stefano,

Why are you not able to terminate and suspend BPT processes in Service Center?

We are colleagues, so we can take this conversation offline if you want.

What change to the permission model do you have in mind?

Regards,

Daniel

Hi Daniel,

I will try to explain this a bit better. Its ok to have that discussion here, so others can benefit from this knowledge.

At first we i was a developers with full controll and i could terminate BPT processes etc.

But there was a need to create developergroups and my developer account went to a group with the same full controll rights.


Apparantly, when you create developergroups, some rights are restricted. I can understand that. But what i cant understand is why my rights to terminate the BPT process of an application that is under my control is nolonger allowed.



I want to bring this under attention again, as it is becoming an increasingly bigger problem.

If we have a problem, even in Acceptance environment, with a BPT process, we are not able to kill the process or even skip the automatic activity. For this we need to contact the main Admin of the OS environment.


Outsystems, please consider this:

Is BPT a part of Application responsibility, or is it the concern of Full admin?

Take also into account who is doing incident management for an application.


BPT should also be the responsibility of a developergroup admin.