How to enable edit CI's once change is out of new state.

[harigundala]

Hello,

I have a requirement where users should be able to add CIs to a change unless it is closed, and admins should be able to add CIs even after the change is closed.

I’ve tried the following without success:

1. Enabling "Reference Floats" for the task.

2. Using the edit button (but it doesn't save the CIs).

3. Modified the create ACL for the task_ci table as below 

Any suggestions or guidance would be appreciated.

Thank you,

Hari

[Dr Atul G- LNG]

HI @harigundala 

Adding a change after the change is closed serves no purpose and goes against the process, violating the rules. So, please don’t try this, mate.

[harigundala]

Hello @Dr Atul G- LNG 

I'm not able to add CI's once change is out of New state as well. Can we configure in a way that we can add CI's out of the New state but not closed ?

Thank you,

Hari

[Dr Atul G- LNG]

Hi @harigundala 

Yes, you need to check if there is any UI policy defined on the state, such as "Assess," that is making the CI field (on the main form) read-only. However, I would not recommend changing this behavior because once a change moves to the Assess state, it means it is ready for approval. If you add a CI at this stage and an approver has already approved the change, it may be difficult to track later if the change fails and the approver was unaware that a CI was added afterward. Therefore, it is better to add the CI in the New state itself.

[Martin Friedel]

Hello,

if you're using Change Models, you can add a Model State Attribute called 'Allow CI Modification'.

1. Open Change Model table [chg_model]
2. Open related Change Model record
3. In related list Model States open State you want to allow Add CIs in
4. In related list Attributes add an attribute called 'Allow CI Modification'
   Warning: Be aware to add this attribute also to initial state as previous default logic (Allowing adding CI in initial state) will stop working!