Request for Change process
You use the request for change (RFC) process to request changes to your environments — for example, to request promotions from the development/tailoring environment to the QA environment, and from the QA environment to the production environment.
This section defines the RFC requirements and related steps. The primary audience is the project manager who must complete the RFC in order to plan, manage, and track the change project. The BMC SaaS Operations team uses the RFC to track all approved changes for each customer.
The following topics are provided:
- Change Management scope
- Comparison of service requests and change requests
- Change Management definitions
- Normal, standard, and emergency changes
- Change request process
- Change documentation
- RFC status codes
For more information about the scope of the change management process and specific rules, see BMC Helix Change Management policy.
Hotfix deployments are recommended by the BMC Customer Support team. To ensure a timely investigation and response, please open a Case on Support Central > Case Management for a hotfix and/or patch request, not a request for change (RFC).