Previous Next JavaScript must be enabled to correctly display this content

## 9.20 Steps to create common-extended folder for extending configJSON.js file

This topic provides the systematic instructions to perform the basic operations on common-extended folder for extending configJSON.js file.

For creating common-extended folder for extending configJSON.js file to do the following:

1. Create a folder inside extended-components\js\components.
2. Folder structure \common-extended\js\util.
3. Next we will add a file configJSON.js in the created folder.
4. The code inside this configJSON.js would be like-

       define(['cmn-util/configJSON'], function (baseobj) {
       baseobj.applicationObject.entityIdByProcessCode['CUSTOM'] = {'ccName': 'fsgbu-
       ob-remo-deposit-ct-process-flow', 'Name': 'RD Amount Block', 'shortName': 'RD
       Amount Block'};
       });

5. Some understanding of the code: -
   - Including the base object by giving the path of configJSON.js base file.
   - Then for example adding the entry for custom process as shown above.
   - The extended configJSON file would be loaded from base commonFunction.js
6. Insertion of the below script into PRODUCT_EXTENDED_LEDGER table

       Insert into PRODUCT_EXTENDED_LEDGER
       (ID,CCA_NAME,CCA_TYPE,PARENT_CCA_NAME,PRODUCT_NAME)  select nvl(new_uuid
       ,'common-extended','config',null,'EXTENDED_COMPONENTS'from
       PRODUCT_EXTENDED_LEDGER;

Parent topic: Extensibility Use Cases for OBX