difference between standard change and standard proposal change

[Kanna12]

Hello Team!

Can any one help the difference between difference between standard change and standard proposal change?

1. If we want to create standard change, was that mandatory to create  an template and need to go through standard proposal approval process? That how SN does work for Standard change?
Was that standard procedure to use in organization?

2. Why can't we create standard change request directly like how we create normal and emergency?

I tried to get the answers for above questions but i can't find any fruitful information.

Can any one please help me here!

[Community Alums · Accepted solution]

Hi @Kanna12 ,

The Standard Change Template Proposal process includes:

• completing a Proposal for a Standard Change Template
• requset approval for the proposal
• connecting with a Change Manager to schedule a visit to CAB
• reviewing Proposal for the Standard Change Template with CAB
• approval by CAB for the Standard Change Template Proposal

The Proposal for a Standard Change Template is two parts.

The first part is about the proposal, why it's needed what justifications you have for having it approved.

• Select a Category for the template (the location where the template is located).
  If you don't see an appropriate category, call a Change Manager for help or to create a new category.
• Enter a title (appears in the template location, Category, meaningful so that the correct template can be used)
• Enter description of the template
• Provide sample changes which help to justify the work being a Standard Change (low risk, highly successful)
•  

The second part is the Change Template content.

• All proposals must have a Service
• Assignment group (only this group can use the template)
• Short description of the change (can be changed when using a template)
• Description (can not be changed when using template)
• Change Plan (can be changed when using a template)
• Risk Assessment (can not be changed when using template)
• Risk Assessment questions (sets Risk/Impact level, should be 4 or 5, see excel worksheet)
  (can not be changed when using template)

In the ServiceNow system, a standard change is a low-risk change that's pre-approved. When a user submits a request for a standard change, it doesn't need approval by a live person—the system creates and assigns the change automatically.

Users request standard changes through a service catalog. The base system comes with a few standard changes, like rebooting a Windows server. As shown in our example below, a user with the itil role searches the service catalog for reboot Windows server...

Your organization can define additional standard changes to suit your operations. To create a new standard change, you'll create a standard change proposal. You need the itil or change manager role to do this.   The procedure is different for each role, as described below.

To create a standard change proposal as a user with the change manager role:

1. Navigate to Change > Standard Change > My Proposals.
2. Click New.

The Standard Change Proposal form lets you specify the details of the change itself and the accompanying change request template for evaluation by the change management team.

To create a standard change proposal as a user with the itil role:

1. Navigate to Change > Standard Change > Standard Change Catalog.
2. Click Template Management.
3. Click Propose a new Standard Change Template.

Note that the form may differ from that shown below depending on the form view of the logged-in user.

For either procedure, when you complete the form and request approval, the system submits the proposal to the change management team for review. Once the proposal is approved, the system automatically adds the new standard change template to the catalog. That's it—now the change can be created and assigned quickly from the catalog without the need for review and approval by the change management team.

Ready to get stared with standard change? Check out this video on our NOWSupport YouTube channel:

Also, Normal Change Templates vs. Standard Change Approvals

[Community Alums · Accepted solution]

Hi @Kanna12 ,

The Standard Change Template Proposal process includes:

• completing a Proposal for a Standard Change Template
• requset approval for the proposal
• connecting with a Change Manager to schedule a visit to CAB
• reviewing Proposal for the Standard Change Template with CAB
• approval by CAB for the Standard Change Template Proposal

The Proposal for a Standard Change Template is two parts.

The first part is about the proposal, why it's needed what justifications you have for having it approved.

• Select a Category for the template (the location where the template is located).
  If you don't see an appropriate category, call a Change Manager for help or to create a new category.
• Enter a title (appears in the template location, Category, meaningful so that the correct template can be used)
• Enter description of the template
• Provide sample changes which help to justify the work being a Standard Change (low risk, highly successful)
•  

The second part is the Change Template content.

• All proposals must have a Service
• Assignment group (only this group can use the template)
• Short description of the change (can be changed when using a template)
• Description (can not be changed when using template)
• Change Plan (can be changed when using a template)
• Risk Assessment (can not be changed when using template)
• Risk Assessment questions (sets Risk/Impact level, should be 4 or 5, see excel worksheet)
  (can not be changed when using template)

In the ServiceNow system, a standard change is a low-risk change that's pre-approved. When a user submits a request for a standard change, it doesn't need approval by a live person—the system creates and assigns the change automatically.

Users request standard changes through a service catalog. The base system comes with a few standard changes, like rebooting a Windows server. As shown in our example below, a user with the itil role searches the service catalog for reboot Windows server...

Your organization can define additional standard changes to suit your operations. To create a new standard change, you'll create a standard change proposal. You need the itil or change manager role to do this.   The procedure is different for each role, as described below.

To create a standard change proposal as a user with the change manager role:

1. Navigate to Change > Standard Change > My Proposals.
2. Click New.

The Standard Change Proposal form lets you specify the details of the change itself and the accompanying change request template for evaluation by the change management team.

To create a standard change proposal as a user with the itil role:

1. Navigate to Change > Standard Change > Standard Change Catalog.
2. Click Template Management.
3. Click Propose a new Standard Change Template.

Note that the form may differ from that shown below depending on the form view of the logged-in user.

For either procedure, when you complete the form and request approval, the system submits the proposal to the change management team for review. Once the proposal is approved, the system automatically adds the new standard change template to the catalog. That's it—now the change can be created and assigned quickly from the catalog without the need for review and approval by the change management team.

Ready to get stared with standard change? Check out this video on our NOWSupport YouTube channel:

Also, Normal Change Templates vs. Standard Change Approvals

[Kanna12]

Thank you for you information. Which reduce a lot of background work.

I tried in my organization environment and personal environment.
In Personal instance it is working fine as expected.

1. In my organizational instance i create templet and able to see the template in catalog. But people  who having change management role and itil role , change write r role they are not able to see. It showing "non Authorized".

Only admin can see the standard catalog.

2. When i open the standard template in catalog in my organization instance , it taking me into change management page and automatically creating change request before submitting. I didn't see the submit button in the form page and when i check the UI Action submit functionality not there. I think it's given by the SN itself. But i am not sure why it is not showing.

But in personal developer instance i am able to see the submit button.

could you please help me here, 
Much appreciated!

[Dr Atul G- LNG · Accepted solution]

Hi @Kanna12 

1. In my organizational instance i create templet and able to see the template in catalog. But people  who having change management role and itil role , change write r role they are not able to see. It showing "non Authorized".

Only admin can see the standard catalog.

Atul: Please check is any specific role / ACL has been defined for other user.

2. When i open the standard template in catalog in my organization instance , it taking me into change management page and automatically creating change request before submitting. I didn't see the submit button in the form page and when i check the UI Action submit functionality not there. I think it's given by the SN itself. But i am not sure why it is not showing.

Atul: Please share some screenshot, also look like your instance is customised one. 

https://youtu.be/JF9GgcoqMac

[Kanna12]

@Dr Atul G- LNG ,

 How you are redirecting Standard chnage page to Standard catelog?
How it is redirecting back to standard page again?
Please hel me here.

I am very confused here!