Normal Change Templates

[Ricky Singh]

Hello,

While I see there is ability to create standard change templates however the client is looking for the ability to create normal change templates which has the ability to create change tasks on the normal change.

I also see that out of the box while some forms have a related link called "Save as templates" like on the project form if you use that same related link user is able to store all values not only on the project form but also the project tasks as a template. However this is not available on the change form.

Do i need to custom create this or can i use something out of the box to develop the feature.

Thanks in Advance.

Ricky Singh

[New user1212]

Hi, Can you tell me how you created Record Producer for this? I tried to follow your steps, but I don't have the option to create a Normal Change because in Templates there are only options for Standard Change... I think adding these steps would be very helpful for the rest!

[Doug Julian]

Hi, Sorry i missed this question previously and i know this reply is late but wanted to follow up on your question.

In short we did not create any new record producers but opened up the existing one to allow it to work for Normal changes. The existing forms do everything you need except when you submit a "standard change template" it auto selects change type = standard. To bypass this we made 2 changes.

1) on the Standard Change properties (std_change_properties) we removed the Change type from the restricted fields. This will allow both the submitter and the approver in the process to change the type to Normal before submitting. When the template is then used in the future it will auto fill the type as Normal on the change record and it will then use the Normal Change workflow. This can be expanded to other change types if desired (i.e decoms, etc if you have those that run on unique workflows)

2) The rest of the requirements are tied to process and handling of the proposed template: when a user submits a proposal our change management team would then review the proposal and ensure it was a valid candidate. If so they would then determin if it was a Normal or Standard candidate based on impact and organizational requirements. 

Before approving the template 2 specific areas were validated; The Category field and the Change value of "Type". These two fields had to line up (parent = Normal Changes and Type = Normal or standard and standard) The Type controls what type of change is created when the template is used, the Parent/Category determins which catalog section the template is displayed under. 

We have two parent caterogies with a number of child categories simply called Standard Changes & Normal changes both located on the Maintain Categories table (sc_category)

NOTE: Categories is very fliexible in how you decide to implement it as you could in theory have just 1 master category of "changes" or something, and pile everything under that category both standard and normal, or you can get as detailed as you like. This is all tied to the presentation of the templates to the end user and wont directly impact the change process itself.

[New user1212]

and also how did you create categories for this template for normal change? 

[ParkHyunSun]

Hi, Could you let me know which UI Action is modified?

Thank you.

[Doug Julian]

The UI Action we modified was the one displayed on the change record (show below) This is an out of box UI Action. We updated the name to make it more gernalized so it fit both Standard and Normal. Additionally we updated the condition to allow it to show up on both more change types. The condition can be movidied to fit your use case.

----------------------------------------------------------------

----------------------------------------------------------------
SYSID 2c087b1f936002003b7a7a75e57ffb8f