Hello Amrendra Kumar,

Please find below details

• When you said "updated section name", what does this mean?
  ---> Alex provided fields of Candidate & Requisition for River Health company. We checked blank section names in DMS for respective company. For matching source field ids updated section field labels in DMS.

• Are you keeping a copy at DMS side for these section name?
  ---> We store these section names at DMS end. While showing fields on template creation it getting used.

• Are you not dynamically picking this up?
  ---> Field labels & section names are configured while configuring client in DMS. (Not clear about dynamically picking) 

• What happens, if client changes the section name or some other client call the same section with different name?
  ---> If client change field section name in there system , they needs to provide updates to DMS (call DMS API manageCustomFields). DMS store fields labels & section name as per clients / company. So for same source field different companies can have different section & label.

Thanks,
RohanK

CC – Samir , Shamooka Mohapatra 

Shamooka Mohapatra, Alexandre - Please see, if we are calling the api if any change on LiFT. Rohan J Khandave, I am wondering how only one section got missed for the client, while other sections were fine.

Hi Rohan J Khandave, we have at least 4 of "Position Description" section field missing on their mapping list. They have raise BETA-810 for following payload

,

Can you please check?

CC: Samir

Hi Amrendra Kumar,

We have analyzed the provided payloads ( From Alex --requisition.json and riverview_payload From Alex.json) and have found that below requisition fields have not been added.

1. { "id": 158, "type": "list", "custom": true, "section": "Pay/Work Rules", "label": "Weekend Qualifier", "mandatory": false, "multiple": true, "datasource": "https://riverview.luceosolutions.com/rest/metadata/list/13", "last_updated": "2019-09-24T10:06:02+0000" }
2.  { "id": 160, "type": "list", "custom": true, "section": "Pay/Work Rules", "label": "Shift Qualifier", "mandatory": false, "multiple": true, "datasource": "https://riverview.luceosolutions.com/rest/metadata/list/15", "last_updated": "2019-09-24T10:06:02+0000" }
3. { "id": 163, "type": "list", "custom": true, "section": "Position Description", "label": "FLSA Job Type", "mandatory": true, "multiple": true, "datasource": "https://riverview.luceosolutions.com/rest/metadata/list/18", "last_updated": "2019-09-24T10:06:02+0000" }
4. { "id": 164, "type": "list", "custom": true, "section": "Position Description", "label": "Work Rule", "mandatory": true, "multiple": true, "datasource": "https://riverview.luceosolutions.com/rest/metadata/list/19", "last_updated": "2019-09-24T10:06:02+0000" }
5. { "id": 169, "type": "list", "custom": true, "section": "Position Description", "label": "\" . TXT_CONTACT_CHOIX_MANAGER . \"", "mandatory": false, "multiple": false, "datasource": "https://riverview.luceosolutions.com/rest/metadata/contact/requisition/169", "last_updated": "2019-09-24T01:54:50+0000" }

 We have added them into the mapping list.

Concern: Custom fields missing from mapping list.

Cause: Requisition Custom mapping having same source field ids as that of Candidate are not getting added into DMS system.

Correction:  While getting the final custom fields data, add check to refer fields for provided requisition custom table. Code changes are in progress.

CC: Rohan J Khandave,Samir

Environment: Prod - ONEIM
API: API: api/manageCustomFields/CBATS

Points verified:
1. API run successfully
2. Able to add new fields.

So, marking jira done.