During an add or update transaction, the job is composed in one of two ways, depending on the current status of the job.
If the job already exists and is active, the existing data is retrieved from the Job Pipeline. If it’s a new job, pre-defined job values are retrieved from the user’s profile. In both cases, the new job data from the request is applied second; the new data overwrites the existing.
Empty and non-existent parameters are handled in the same way: they do not overwrite existing values.
For example, submitting these parameters
| 1 | title_en: | "Spicy Rib Cook II" |
| 2 | location_city: | "Oakland" |
| 3 | location_stateprovince: | "" |
to update this existing job
| 1 | title_en: | "Spicy Rib Cook" |
| description_en: |
"Prepare very spicy, but delicious, ribs." | |
| 2 | location_city: | "San Francisco" |
| 3 | location_stateprovince: | "US-CA" |
would result in this new job.
| 1 | title_en: | "Spicy Rib Cook II" |
| description_en: |
"Prepare very spicy, but delicious, ribs." | |
| 2 | location_city: | "Oakland" |
| 3 | location_stateprovince: | "US-CA" |