- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2023 08:16 PM
Hello,
I'm working on the ITSM implementation course, and I seem to have hit a roadblock with the Change Models task. Any assistance would greatly appreciated. Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2023 08:25 PM
Hi @jamescblue ,
Change Models help to streamline workflow and include Model States. Examples include Normal, Emergency, Standard, Change Registration, etc.
Change Registration is a Change model used to capture change requests in an external system. There are no approvals associated with this model.
I believe this was introduced in Quebec. I believe the primary use case is DevOps
https://www.youtube.com/watch?v=qcON3o2WAzQ
So, Change Registration would be a change model which is used to capture change requests in an external system. There are no approvals associated with this model.
How to Create:
Procedure
- Navigate to All > Change > Administration > Change Models.
- Click New.
- On the form, fill in the fields.
Change Model form Field Description Name Unique name for the Change model. Default Change Model Option for enabling the Change model as a default model on the Change request form. Active Option for enabling that this model is available for selection when creating a Change request. Color Color that appears on the left side of the Change model bar on the Models tab in the Change landing page. Available in 'Create New' Option for enabling that this model is available for selection on the Models tab on the Change landing page. Also, the model will be available to select in the Model field on the Change request form. Description Detailed description of the Change model. Implementation states Implementation state for the Change model. For more information on states, see State model and transitions Record Preset Preset values for all changes using this model. Advanced Security Option to enable role-based access controls and user criteria to tailor the Change creation landing page views. When you enable Advanced Security, Available For, Not Available For, and Can write tabs appear next to Model States tab. Read Roles Option to define the roles to view the Change model. Write Roles Option to define the roles to edit the Change model. - Click the form context menu icon (
The Model States context menu appears. You can select the states for your Change model.
- Click New.
- On the form, fill in the fields.
Model State form Field Description State State that you want to include in your model. Initial State Option to enable this state as the initial state for your model. This field is automatically selected when you add the first state to your model. - To save the state and return to the Change Model form, click Submit.
- To add a transition between the states, click the display/hide hierarchical lists icon (
The Model State Transitions context menu appears.
- Click New.
- On the form, fill in the fields.
Model State form Field Description From State that the Change request is moving from. To State that the Change request is moving to. Automatic Transition Option for enabling automatic transition to the Change request when the defined conditions are met. Selecting this option also prevents you from manually selecting the State field on the Change request form. - Click the form context menu icon (
The Model State Transition Condition context menu appears.
- Click New.
- On the form, fill in the fields.
Model State Transition Condition form Field Description Name Unique name for the condition. State Transition State that you're applying the transition condition to. This field is automatically set with the state that you're applying the condition to. Description Detailed description of the condition. Requires Condition for your transition. You can select a pre-defined condition or select Transition Condition to define a condition. To create pre-defined conditions, see Create predefined conditions. Condition (condition builder) Condition on the Change request that must be fulfilled to enable the transition. Condition (script) Script that must be fulfilled to enable the transition. The script returns a value of True when passed. Active Option to make the condition active. - Click Submit.
- Select Available For tab.
- Select New to add the list of users who can access the Change model
- On the form, fill the fields.
User Criteria record Field Description Name Unique name for the user criteria record. Active Option to make the condition active. Users Option to select the users who can access the Change model. Groups Option to select the groups who can access the Change model. Roles Option to select the role who can access the Change model. Companies Option to select the companies who can access the Change model. Locations Option to select the location of the company who can access the Change model. Departments Option to select the departments who can access the Change model. Match All Option to use the Change model if it meets all conditions in the user criteria. Advanced Option to create a script to meet the condition for user criteria. - Select Submit.
- Manage the users to access the change model by providing the user access in Not Available For, Available For, and Can Write tabs:
- Available For – Provides the access for the change model
- Not Available For – Doesn’t provide the access for the change model
- Can Write – Provides the editable access to the change model
For more information on user access, refer Control user access for a change request.
- Select Submit.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2023 08:25 PM
Hi @jamescblue ,
Change Models help to streamline workflow and include Model States. Examples include Normal, Emergency, Standard, Change Registration, etc.
Change Registration is a Change model used to capture change requests in an external system. There are no approvals associated with this model.
I believe this was introduced in Quebec. I believe the primary use case is DevOps
https://www.youtube.com/watch?v=qcON3o2WAzQ
So, Change Registration would be a change model which is used to capture change requests in an external system. There are no approvals associated with this model.
How to Create:
Procedure
- Navigate to All > Change > Administration > Change Models.
- Click New.
- On the form, fill in the fields.
Change Model form Field Description Name Unique name for the Change model. Default Change Model Option for enabling the Change model as a default model on the Change request form. Active Option for enabling that this model is available for selection when creating a Change request. Color Color that appears on the left side of the Change model bar on the Models tab in the Change landing page. Available in 'Create New' Option for enabling that this model is available for selection on the Models tab on the Change landing page. Also, the model will be available to select in the Model field on the Change request form. Description Detailed description of the Change model. Implementation states Implementation state for the Change model. For more information on states, see State model and transitions Record Preset Preset values for all changes using this model. Advanced Security Option to enable role-based access controls and user criteria to tailor the Change creation landing page views. When you enable Advanced Security, Available For, Not Available For, and Can write tabs appear next to Model States tab. Read Roles Option to define the roles to view the Change model. Write Roles Option to define the roles to edit the Change model. - Click the form context menu icon (
The Model States context menu appears. You can select the states for your Change model.
- Click New.
- On the form, fill in the fields.
Model State form Field Description State State that you want to include in your model. Initial State Option to enable this state as the initial state for your model. This field is automatically selected when you add the first state to your model. - To save the state and return to the Change Model form, click Submit.
- To add a transition between the states, click the display/hide hierarchical lists icon (
The Model State Transitions context menu appears.
- Click New.
- On the form, fill in the fields.
Model State form Field Description From State that the Change request is moving from. To State that the Change request is moving to. Automatic Transition Option for enabling automatic transition to the Change request when the defined conditions are met. Selecting this option also prevents you from manually selecting the State field on the Change request form. - Click the form context menu icon (
The Model State Transition Condition context menu appears.
- Click New.
- On the form, fill in the fields.
Model State Transition Condition form Field Description Name Unique name for the condition. State Transition State that you're applying the transition condition to. This field is automatically set with the state that you're applying the condition to. Description Detailed description of the condition. Requires Condition for your transition. You can select a pre-defined condition or select Transition Condition to define a condition. To create pre-defined conditions, see Create predefined conditions. Condition (condition builder) Condition on the Change request that must be fulfilled to enable the transition. Condition (script) Script that must be fulfilled to enable the transition. The script returns a value of True when passed. Active Option to make the condition active. - Click Submit.
- Select Available For tab.
- Select New to add the list of users who can access the Change model
- On the form, fill the fields.
User Criteria record Field Description Name Unique name for the user criteria record. Active Option to make the condition active. Users Option to select the users who can access the Change model. Groups Option to select the groups who can access the Change model. Roles Option to select the role who can access the Change model. Companies Option to select the companies who can access the Change model. Locations Option to select the location of the company who can access the Change model. Departments Option to select the departments who can access the Change model. Match All Option to use the Change model if it meets all conditions in the user criteria. Advanced Option to create a script to meet the condition for user criteria. - Select Submit.
- Manage the users to access the change model by providing the user access in Not Available For, Available For, and Can Write tabs:
- Available For – Provides the access for the change model
- Not Available For – Doesn’t provide the access for the change model
- Can Write – Provides the editable access to the change model
For more information on user access, refer Control user access for a change request.
- Select Submit.