Change fields and their behaviour

2 min

Field Label	Field Type	Field Behaviour	Purpose
Actual end	Date and time	Mandatory when of status "post implementation review" or "completed" on wards.	This is the date and time that the change implementation actually ended.
Actual start	Date and time	Mandatory when of status "post implementation review" or "completed" on wards.	This is the date and time that the change implementation actually started.
Approvals	Multiple reference (Workflow task table)		Shows the approvals that have taken place for a change, as well as who is being requested for approval.
Approver	Multiple reference (User table)	Visible and mandatory when change is being requested for peer review for change types of "minor" and "major".	Determines who gets asked for approval (in addition to the other approvers that are automated) when a minor or major change gets submitted for approval.
Assignee	Reference (User table)	Mandatory when change is being completed. User must be a part of the assignment group, be active and have the itsm_agent role or administrator role. Is automatically cleared if the assignment group changes and they are not a member of the group.	This is the individual responsible for the completion of the change.
Assignment group	Reference (Group table)	Mandatory Group must be selectable, have change listed in the accessible from table field or the accessible from table field must be empty.	This is the group that is responsible for the completion of the change.
Attached knowledge	Reference (Knowledge table)	Read only Automatically set when knowledge is attached from Sofi.	This is used to understand what knowledge was used for a change.
Business justification	String	Mandatory when change is being requested for peer review.	This is the business justification as to why a change should be implemented.
Change type	Choice Values: Emergency Minor Major Pre-approved Unscheduled emergency	Mandatory	These are the change types that a change can follow. Depending on the change type, will depend on the different mandatory fields, approval steps and general workflow of a change.
Classification	Reference (Classification table)	Mandatory Must be selectable and for the change table	This is the classification that can be selected from a change that can help for reporting or otherwise.
Closed at	Date and time	Read only Automatically set	This is automatically set based on the date and time that the change s closed.
Closed by	Date and time	Read only Automatically set	This is automatically set based on the person that closes the change.
Collaborator	Multiple reference (User table)	Users must be active and have the itsm_agent role or administrator role.	These are any users who may be assisting in the completion of the change or want / need to be kept up to date as to the progress of the change This is also used to assist with the "Changes I'm following" menu item.
Completed at	Date and time	Read only Automatically set	This is automatically set based on the date and time that the change is completed.
Completed by	Date and time	Read only Automatically set	This is automatically set based on the person that completes the change.
Completion notes	String	Mandatory when change is being completed.	Used to provide information as to how a change was completed.
Description	String		Extra information that can be provided as part of the change.
Impact	Choice Values: Critical High Medium Low	Mandatory when change is being requested for peer review.	This holds the potential impact of the change if it was to go wrong.
Implementation plan	HTML	Mandatory when change is being requested for peer review, unless it is of change type "unscheduled emergency". Mandatory when it is in the status of "post implementation review" when change is of type "unscheduled emergency"	This is the step by step plan that a user can outline the steps that will be taken when the change is being implemented.
Planned end	Date and time	Mandatory when change is being requested for peer review.	This is the date and time that the change implementation is planned to end.
Planned start	Date and time	Mandatory when change is being requested for peer review.	This is the date and time that the change implementation is planned to start.
Post implementation review	HTML	Mandatory and visible when status is of type "post implementation review" and change is of type "major", "emergency" or "unscheduled emergency".	The details as to how successful or unsuccessful a change was implemented, to be able to take continual learnings from it.
Priority	Choice Values: P1 \| Critical P2 \| High P3 \| Medium P4 \| Low P5 \| Planning	Mandatory	The priority of a change used for reporting purposes, conditional logic purposes and SLA purposes.
Reference Number	Auto sequence (Prefix is CHG)	Read only Automatically set Display value	Used as a unique reference to a change and its display value.
Related configuration items	Multiple reference (CMDB table)		Used to highlight any configuration items related to a change.
Related incidents	Multiple reference (Incident table)		These are the incidents that are related to a change that will be automatically resolved once the change has completed.
Related problems	Multiple reference (Problem table)		These are the problem that are related to a change that will be automatically resolved once the change has completed.
Related requests	Multiple reference (ITSM Request table)		These are the ITSM requests that are related to a change that will be automatically completed once the change has completed.
Remediation plan	HTML	Mandatory when change is being requested for peer review, unless it is of change type "unscheduled emergency" Mandatory when it is in the status of "post implementation review" when change is of type "unscheduled emergency"	This is the step by step plan that a user can outline the steps that will be taken if the change goes wrong and either needs to be backed out, or fixed forward.
Requested by date	Date and time	Mandatory when change is being requested for peer review.	This is the date that the change is requested to have been implemented by.
Reviewer	Multiple reference (User table)	Mandatory upon asking the change for review	These are the users who review a change, prior to asking for approval, to determine if the change is in the correct change type and should be implemented.
Risk	Choice Values: Critical High Medium Low	Mandatory when change is being requested for peer review.	This is the risk that the change may go wrong and / or the risk to the greater organisation.
Service	Reference (Service table)		This is the service that can be selected from a change that can help for reporting or otherwise.
Short description	String	Mandatory	The short description is used as the primary classifier source for Sofi.
Sofi conversation ID	String	Not visible on the form	Used to hold the Sofi conversation ID, which is used by the Sofi continuation point dialog manager element.
Subtasks	Multiple reference (Change task table)		These are the change tasks that have been created from and are related to a change.
Test plan	HTML	Mandatory when change is being requested for peer review, unless it is of change type "unscheduled emergency" Mandatory when it is in the status of "post implementation review" when change is of type "unscheduled emergency"	This is the step by step plan that a user can outline the steps to test the change once it has been implemented, to determine it was implemented successfully.
Work journal	Journal		This is the method to communicate internally about a change.

Other fields hidden from form and un-used

The below are fields that come off one of the tables changes extend from, which it does not use or have on the form. Some will have some behaviours tied to them (due to existing on the Work table), but some will have nothing tied to it. As a result, you can use them, but they will likely have no functionality tied to them. Note that there are other fields, but they are not recommended to be used due to the potential impact.

Field label	Field type	Field behaviour	Purpose
Client journal	Journal		As clients are recommended not to view changes, this field is not visible on the form and is not used.
Follower	Multiple reference (User table)		As clients are recommended not to view changes, this field is not visible on the form and is not used.
Parent	Reference (Work table)	Read only	Not used for any purpose at the moment, but can be used in the future
Requested for	Reference (User table)	Mandatory	As clients are recommended not to view changes, this field is not visible on the form and is not used.
Requestor	Reference (User table)	Mandatory	As clients are recommended not to view changes, this field is not visible on the form and is not used.