Hello

I think your condition should be the reverse:

current_update.PhaseId.IsChanged == false

When the approval is complete, you still need to allow the record to transition into the new phase. Once the transition is complete, you lock it.

Best regards,

Brindusa

Hi Brindusa,

Somehow I missed your update...

I do not really understand what you mean, basically what we want is that when we see the phase change, and it is now in for example the execute fase, we want to disable some fields so they can no longer be editted. Is this what you are suggesting?

${current_update.PhaseId.IsChanged == false && current_update.PhaseId.NewValue == 'Execute'} ?

I could not get it to work with my earlier suggestion so what I did was the following:

Go to Change -> Normal -> Rendering Forms ->

If ${entity.PhaseId == 'ApproveDeployment' || entity.PhaseId == 'Execute' || entity.PhaseId == 'Backout' || entity.PhaseId == 'CMDBUpdate' || entity.PhaseId == 'Review' || entity.PhaseId == 'Close' || entity.PhaseId == 'Abandon'}

Disable scheduled start

And I repeated this for all the fields.

Hello

The only change I made to your original expression was to "reverse" the first condition to check for false rather than true on PhaseId change:

${current_update.PhaseId.IsChanged == false && (entity.PhaseId == 'Execute' || entity.PhaseId == 'CMDBUpdate' || entity.PhaseId == 'Review' || entity.PhaseId == 'Close' || entity.PhaseId == 'Abandon')}

The only change I made to your original expression was to "reverse" the first condition to check for false rather than true on PhaseId change. I tested with both transitioning into one of the phases and trying to modify the field once in one of the listed phases and it seems to work.

As a note, you could as well switch and use the Restrict/allow editing of fields rule. The rule functions both as a rendering rule and as a validation rule (in the user interface it appears under Rendering rules). It restricts or allows editing of selected fields for all actions, UI-based, backend process-based, or API-based. 

Best regards,

Brindusa

Hi Brindusa,

Yes thank you, we ended up going for the Restrict/allow editing of fields because that also does a validation on mass update. For example disable field still leaves the option to do a mass update and still change the field. Also the Restrict/allow editing of fields rule has multple field options so you only need 1 rule for multiple fields instead of 1 rule each field so we went that route: