Add approver to Standard Change

[Tom L Logan]

I know standard change do not require approval.  But we have one standard change template that we would like to go to an approver.  How do we handle that?  I do not want to change the workflow for Standard Change since I only need one of my standard change templates to be approved.  Any one has an idea how this can be achieved?

[SanjivMeher]

I cant think of a solution without changing the workflow or without creating a new workflow for the one which needs approval

[Tom L Logan]

Creating a new workflow for the one which needs approval is what I am not sure how to proceed.  We have several standard change templates and they use the Standard Change workflow.  I am not sure I to isolate one of the templates and create a different workflow for it.

[scott barnard1]

What advantage does your standard change give you that a normal change built from a template doesn't?

As a rule of thumb the only real difference is that standard changes don't undergo approval but are scheduled and are subject to review.

So I'm guessing that a standard change with an approval is pretty much the same as a normal one?

Change as a module tends to get heavily customised so I guess we just need to understand why it needs to be a standard change template in your environment?

[Tom L Logan]

It is a very repeatable process and certain fields have been prefilled.  It requires Security Manager approval at all times.  We do not want it to be a normal change.