POST: Does not save the new job flag fields

[SathyaJayabal]

1. Use Post to create a JOB with job flag fields.

Job is created and the response has the correct data for the job flag fields

2. User GET to view the job created in step 1

The job flag fields have the default values and not the values used in step 1.

[LieutenantRoger]

Suspect this is an issue with the zap syncing system. @SathyaJayabal will work with @nkumar-topcoder @sushilshinde to work through the syncing process of the zap system next Week.

[SathyaJayabal]

@LieutenantRoger , check out this scenario please.

1. Patch details for the new flags with some values.
2. Now patch the job and update any other field, example , start date
3. All the new fields data is now default values.

I guess for the POST case, same thing is happening
When user creates job with flag details it gets created correctly
When RCRM patches the external id of the job, these flag details are going back to default.
So the issue is with the PATCH. PATCH any other field is resetting the flag field values to default.

[LieutenantRoger]

@SathyaJayabal I think I have fixed this one and the dev env has been deployed.

[SathyaJayabal]

@LieutenantRoger , verified on dev

[sandhiyakavi]

Verified on Prod Env through FE