Agree or refuse a change request
Open the approval record and
click Approve to approve the change request or Reject to reject it.
request changes to the planned state if it is approved or to New state
if it is rejected.
Implement a change request
Click Implement to put the change request into action.
request state changes to Implement. The workflow creates two change
tasks: Implement and Post-implementation testing. Check
the change tasks and assign them to a user or group.
Review a change request
Click Review after reviewing the information on the change request.
request is then moved to the Review state. All open change
tasks are put to Cancelled.
Close a change request
Click Close after entering the Close code and Close
notes in the Closure Information section.
The change request is closed.
Cancel a change request
From the context menu, click Cancel Change. Provide a reason for cancelling the change and
request is cancelled and the cause for cancelling the change is added to
the Work Notes field.
can also add approval record to the change request activity log. Click the
activity filter icon and select Approval history from
the list. When there is a change in the approval process, such as an approval,
rejection, or comments, the activity log is updated.
ServiceNow for implementation of Asset Management
asset Management application integrates the physical, technological,
contractual, and financial aspects of information technology assets.
Asset management business practices
have a common set of goals.
inventory that is purchased and used.
the cost of purchasing and managing assets.
the suitable tools for managing assets.
the asset life cycle from planning to disposal.
compliance with relevant standards and regulations.
IT service to end users.
standards and processes for managing assets.
The ServiceNow Knowledge
Management (KM) function enables the sharing of information in knowledge
bases. This knowledge base comprise of articles that offer users with
information such as self-help, troubleshooting, and task resolution.
Knowledge Management has significantly changed with Knowledge v3,
which is enabled by default for all instances opening with the Fuji release.
Knowledge Management supports processes
for creating, categorizing, reviewing, and approving articles. Users can search
and browse articles as well as give feedback.
To support numerous groups, knowledge bases
can be assigned to individual managers. Separate workflows can be used for
publishing and retiring articles, and separate access controls can be used to
control interpretation and contributing.incident.