Does an update require a development code freeze?
Oracle B2C Service
The Golden Rule is to avoid implementing large-scale development projects in parallel to an update. It is much more difficult to change the oil when the vehicle is moving. Common administrative tasks such as creating or editing workspaces, reports and profiles is fine. A handful of custom script edits or Custom Portal edits is also acceptable thanks to File Sync.
There are three important exceptions:
- Avoid touching Configuration Settings or Message Bases during the 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 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.
- Seven days prior to cutover Custom Object deployment is blocked. You can delay cutover if you need to make a critical change to custom objects when you are in an update cycle. See Custom Object deployment error: Deployments are currently disabled 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.