Does an update require a development code freeze?
Oracle B2C Service
The Golden Rule is to avoid working on or deploying large-scale development projects in production during an update. It is much more difficult to change the oil when the vehicle is moving. Common production administrative tasks such as creating or editing workspaces, reports or profiles is fine. Business as usual agent activity should continue in production. A handful of production custom script edits or Custom Portal edits is also manageable thanks to File Sync.
There are two important exceptions where production changes can be lost at cutover:
- Avoid touching Configuration Settings or Message Bases during the entire update. Please read Why are we unable to create new message base or configuration settings? closely if you have no option but to create or update standard or custom records.
- Avoid touching Add-Ins during the update. It is critical you keep the production and upgrade Add-In synced if an exception occurs. For example, say you update the production Add-In; call it Add-In v2. You must then overwrite the equivalent upgrade site Add-In with v2.
- Custom Object deployment is not allowed within seven days of cutover. You can delay cutover if you must make a Custom Object change during an update. See Custom Object deployment error: Deployments are currently disabled for details.
- A custom field deployment within seven days of cutover can result in cutover delay. See What is a presite? for details.
- Production Asian Language Dictionary edits will be lost unless the same edits are applied to the upgrade site. An alternative is to export your production Asian Language Dictionary shortly before cutover and then import it post cutover.