Policy Validation [states transition]
Hi all,
I've some policies configured in a state of my lifecycle. I put the validation check at the transition to another state, to verify if was sucessfull, warning or error.
In my case it is not allowed to pass to another state if the policy result is error (Policy X is not Error), but the transition only occurs if the policy is OK, if it is Warn the transition is not done.
Anyone can explain me how policies works within a lifecycle validation and configuration?
I've some policies configured in a state of my lifecycle. I put the validation check at the transition to another state, to verify if was sucessfull, warning or error.
In my case it is not allowed to pass to another state if the policy result is error (Policy X is not Error), but the transition only occurs if the policy is OK, if it is Warn the transition is not done.
Anyone can explain me how policies works within a lifecycle validation and configuration?
7 answers
Hi Ben,
Even you were on 7.5 or 7.5.0.1 the issue would happens. For my case this issue was fixed on 7.5.0.2.
I've never used a default policy that return a Warning result, always OK or Failure, so I guess this issue only happens when a Warning is returned. As I've mencioned, if is possible to upgrade to 7.5.0.2, maybe you've your problem might be solved.
Even you were on 7.5 or 7.5.0.1 the issue would happens. For my case this issue was fixed on 7.5.0.2.
I've never used a default policy that return a Warning result, always OK or Failure, so I guess this issue only happens when a Warning is returned. As I've mencioned, if is possible to upgrade to 7.5.0.2, maybe you've your problem might be solved.
I am facing the same issue. We would like to generate a warning from a custom policy that will alert the user, but not prevent them from promoting the asset. Documentation seems to imply a warning is different to an error but so far it seems the only difference is the icon displayed with the message.
Is this a bug with RAM or an intentional feature?
Is this a bug with RAM or an intentional feature?
Hi all,
I've some policies configured in a state of my lifecycle. I put the validation check at the transition to another state, to verify if was sucessfull, warning or error.
In my case it is not allowed to pass to another state if the policy result is error (Policy X is not Error), but the transition only occurs if the policy is OK, if it is Warn the transition is not done.
Anyone can explain me how policies works within a lifecycle validation and configuration?