Copy fields from parent request to amendment request

Australia Employee Service Management

Release

australia

ft:locale

pt-BR

ft:publication_title

Australia Employee Service Management

ft:clusterId

emplsm

bundleId

emplsm

workflow

Employee

Copy fields from parent request to amendment request

Versão de lançamento: Australia

Atualizado 12 de mar. de 2026

2 min. de leitura

Configure the ContractManagementExt extension point to automatically copy fields to contract request from the linked parent request and parent contract.

Por Que e Quando Desempenhar Esta Tarefa

As an admin, you can configure fields for which the values from the contract repository record will be automatically copied to the amendment request. Configure common fields between the contract repository record and the amendment request so that the contract fulfiller can update them as per the requested amendments. Example: If you configure end date and payment terms to be available and automatically copied from the contract repository, the fulfiller can modify value for these fields as part of the amendment request.

Antes de Iniciar

Role required: admin

Procedimento

Navigate to All > System Extension Points > Scripted Extension Points.
In the API Name field, enter sn_cm_core.ContractManagementExt.
Select the record.
In the Related Links section, select Create implementation.
On the Script Include form, fill in the fields.

For a description of the field values, see Scripted Extension Point form fields.

In the Script field, update the copyDataFromBUToCMR function to configure the fields that you want to copy from the parent record to the contract request.

For example, if you want to copy the Account and End date fields from a parent record to contract request, you can use the following:


/**
	 * @param {GlideRecord} parentRequestGr - GlideRecord of BU request record
	 * @param {GlideRecord} contractGr - GlideRecord of signed contract record. This will be available only for amendments. 
        * For new contract request, this will be null.
   * Make sure to check for null before using contractGr
	 * @param {String} requestType - Helps to identify if the request is `amendment` or `cmr`
	 * @param {String} application - Id of application. Helps to identify to which Business unit or appplication the contract request belongs to
	 * @returns {Object} - Key value pairs of fieldName and its value in data sub-object
   * contractGr will be provided only in case of amendment request type.
   * Based on the request type, can add required mapppings for CMR record.
   * For New contract request, mapping can be done from parentRequestGr to ContractRequest record
   * For Amendment, mapping can be done from parentRequestGr and contractGr to ContractRequest record
	 * Example- { data: {'account': 'xyz_sys_id', 'end_date': '2025-12-07'} }
	 */
	copyDataFromBUToCMR: function(parentRequestGr, requestType, contractGr,  application) {
            data: {
                      'account': parentRequestGr.getValue('account'),
                      'end_date': parentRequestGr.getValue('contract_end_date'),
            	},

    type: 'ContractManagementExt'
};

Nota:

The data type of the parent contract repository record field and the contract request field must match.

Select Update.
In the Extension Point form, select Update.

Resultado

When a contract request is initiated, the configured fields are automatically populated with the corresponding values from the associated contract repository record selected while initiating an amendment request.