Creating, Approving, Implementing, and Closing RFCs
Take a tour of the standalone eChangeManager workflow and notifications.
Reporting on RFCs
Customising RFC Layout
Hosted ITIL & SOX Compliant IT Change Management Software Incomplete RFC
Incomplete RFC-Giva eChangeManager
Change request incomplete. When a RFC requires more documentation, the Change Manager moves the status to "PENDING" and sets the Waiting Code to a waiting reason such as "Implementation Plan, Backout Plan and/or Test Plan. Giva eChangeManager automatically notifies the implementer. Notes in the Change History field indicate that the RFC needs more work before sending the RFC to the Change Advisory Board (CAB) for discussion and approval.
Request a Live Demo
Assess Your Needs
Try Giva's 30 Day Trial