Change Request back to draft

[juliekirkeeide]

Does anyone allow users to send Change Request back to draft at will?   So, rather than sending it back to Draft only based on a rejection, allow a user to click a 'reset' button or somehow manually send it back to Draft?

[HugoFirst]

1. Description is the only field we do this on ( for the change task ).   But the technique could be used for any given field, and on any kind of record.

2. We don't send email for this type of edit.   But there is a review of the change requests each week where people can discuss what was changed and why.     The change task has a history that allows one to see the previous description   and compare that to the new value if there is any doubt about the modification.

Our intention is to allow technicians some freedom to improvise during the implementation of the change, without backing out of a change or pursuing new approvals.   Prior to this change, technicians improvised when necessary, but the improvisations were often not documented and got lost.   Note that If someone abuses this capability, it becomes apparent in the change review.

[dave1964]

Hi Steve,

Would it be possible for you to share your UI Actions for this change as we are being asked a similar question by our Change manager and are having some difficulty getting it right?

Regards

Dave

[HugoFirst]

Our scheme starts with 2 custom variables on the sc_task table, one to unlock the description field and a second to indicate that a change was actually made.

Then we have 4 UI actions, note that all four have "Reverse if False" set to true.

> "show/hide unlock description" has a condition to hide the 2 variables if the change_request.state is draft.

> "lock/unlock description field" has a condition of change_request.state is draft OR u_description_unlocked is true.

    This UI policy will set the description's   READ ONLY to false if the conditions are true.

> "oclc-set description revised to readonly" - will always run and it set's the custom field "description revised" to readonly.

> "oclc-set description unlocked readonly" has a condition of (Description revised is true ) and it sets u_description_unlocked READONLY to true

Does this help?

[Dave105]

Many thanks Steve for the helpful notes and the quick response.

Marked as Helpful and Liked

Regards

Dave