UC should spin up a new sandbox to use as a hot fix environment. Once the bug is

corrected, the change should beapplied to production and downstream environments.

The fix should be made in the developer environment where the project work was done.

Once the fix has been made, it should go through a full deployment/testing process and

adhere to the normal projectcadence.

Since the issue was found in production, it should be treated as a change request and go

into the backlog as an enhancement.

Correcting the bug in UAT is ideal. Since UAT is a full copy, it will be the fastest

location to fix and test the resolution.

The first task of the new sprint must be the deployment approval. After that, the other tasks of the sprint can be performed in the environments and Git.

Using Git, create a release branch from the develop branch. All fixes must be made in the release branch. After deployment, merge release with develop.

Commit upcoming changes to the features branch without merging into the develop branch. Deploy from the develop branch and then merge new sprint features into the develop branch.

Migrate the current code to the UAT sandbox. Begin new sprint development in the Dev sandbox. Make fixes in the UAT environment and deploy UAT for production after business approval.

In change sets, external objects are included in the custom object component.

In the Metadata API, the External Object metadata type represents external objects.

In change sets, external objects are included in the External Object component.

In the Metadata API, the Custom Object metadata type represents external objects.