1. Enabling Change Requests

1.1 Change Request Activation

In the Admin Console > Object Management > Change Request Management, select the object for which you want to enable change requests and toggle the switch to enable it.

1.2 Generation of Change Request Object

A change is an action from state A to state B, but you need an actual entity to record and carry that change. Therefore, a Change Request is also an entity object. When you enable Change Requests for a given object, the system automatically creates a Change Request entity object for that object.

1.2.1 Change Request Name

• Rule for Change Request object label: Original Object Name + “Change Request”
  • Example: If you enable Change Request for Sales Order, the Change Request object label will be “Sales Order Change Request”
• Rule for Change Request object API Name: APIName + “ChangeObj”
  • Example: If you enable Change Request for Sales Order, the Change Request object API name will be “SalesOrderChangeObj”

(Note: The standard term “Sales Order” replaces the original Chinese term where applicable.)

1.2.2 Change Request Fields

• A Change Request object includes: all fields from the source object (including custom fields) + Record Type + change-related fields
  • Change-related fields include: Version Number, Changed By, Change Date, Approval Time, etc.

1.2.3 Change Request Buttons

• After enabling Change Requests, the original object’s Edit button is disabled and replaced by a Change button. Subsequent edits must be performed via the Change button on the Change Request.
• When a user clicks the Change button, the system validates whether there is an active Change Request currently in approval. A source record can have only one in-progress Change Request at a time.