Revise active according with lifecycle status

[FC_9723361]

In the OIR i set for a user Revise NOT possibile in only Released stase in epmdocument. For other states, for example draft, revise should be possible. But is already obscured

[Catalina]

Hi @FC_9723361 

Thank you for your question! 

I’d like to recommend to bring more details and context to your initial inquiry. 

Please add screenshot(s) to better understand what you are trying to do in your process. 

Please refer to this guideline to make your questions more likely to receive a quick and useful answer. 

This will increase your chances to receive meaningful help from other Community members. 

Furthermore, please consult this Community Search guideline as well, which boosts up your chances of finding a resolution to your topic(s) much faster. 

Thank you for your participation and please let me know if you need further assistance! 

Best regards,

[avillanueva]

Blocking revise can be done in ACLs and also in the Lifecycle definition. Can you post copies of both here? For clarity, you are seeing that its not possible to revise in Draft, but option is greyed out? 

[FC_9723361]

Configuration of ACLs rules on Approved status and Draft status

In draft status Revise icon is missing

[HelesicPetr]

Hi @FC_9723361 

It would be nice to see your OIR configuration.

There are more rules for controlling the revision action then just ACL definition

I am not sure if you can control the revise action directly from the OIR .

- I guess that you have to have correct LifeCycle Template configuration, where the revise transaction is allowed,

- then ACL create has to be granted to the user in the target state where the new revision will be placed

- check the profile configuration if you use profiles.

PetrH

[Hari_Vara]

Hi,

What is your business requirement?

Based on that we can go for an approach.

Usually Revision action is allowed for only "Released" objects. (Subject to the access control the user has) Sometimes, it too can be hidden in UI and only possible by a Change Notice.

There are many ways to achieve what you need (Business Requirement).

Cheers

Hari

[FC_9723361]

My business requirement is:

if the epm document is "Approved" Revise icon should be hidden

if the epm document is in "Draft" Revise icon should be visible.

Now is set in this way by acl rules, but in "draft" status Revise icon is hidden however

[avillanueva]

Tests you can do: Add "&jcaDebug=true" to the end of the URL on the EPMDocument page you are viewing in Draft. You will see a bunch of lady bugs appear. Click the actions drop down and see why the action is being disabled. It should say the validator or filter that disabled it.

Second, in the policy administrator, there is a "View Access Control Lists" where you can see a summary of the ACLS by object and state. See if something is off there, perhaps by user groups or deny rights.

Lastly, we should check the lifecycle template for your EPMDocument. Do you have Revise checked? This is showing its allowed in my In Work state but my ACLs only allows admin to do that.

[FC_9723361]

Hello in attached debug, list acl rules and lifecycle. Seems to be right.

Perhaps in debug we should know what the problem is

[HelesicPetr]

Hi @FC_9723361 

This ACL definition is ok, but you do not know if there are not any others definitions that could involve the results.

So go to the EPMDocument in the draft state, and use a Edit Access Control 

Go to the detail info and check the ACL results and share the screen shot.

PetrH

[FC_9723361]

As you thought revise is not checked in draf

[HelesicPetr]

Hi @FC_9723361 

Go to the detail of the row by the I icon.

You will see where the ACLs are defined.... 

PS> be careful with Deny usage. 

Absolute deny rule on any domain level will not allow to use the revise function even though it is allowed on a lower domain level

Deny rule can be rewritten on the lower domain level but if the Deny rule and Allow rule is on the same level, the Deny rule is applied. 

Keep this rules in your mind.

PetrH

[FC_9723361]

Now revise is able in details, but is always unchecked 

[HelesicPetr]

Hi @FC_9723361 

As I see your ACL rules are set directly on the User

I can not see all the rules defined please slide to the left to see the end of the row

The result is clear. You do not have granted access to the Revise

Check the Lifecycle Access control

it seams that somewhere the access is denied

PetrH

[FC_9723361]

For the author revise is available, but if it is not the author ma only the modifier ? Should be this the problem?

[HelesicPetr · Accepted solution]

Hi @FC_9723361 

I see the root  case.

Your ACL rules define the Deny rules directly on the user. So others rules are rewritten.

The MINUS means Deny. So your ACL definition contains a users level ACL definition that rewrites all upper rules from domains.

Change it and the user will get the Revise rights.

PetrH