Inventory Batch Preprocessing Settings and Behavior in Job API
The `meta` object allows for the inclusion of additional metadata when creating a Job. The currently supported key within `meta` is `preprocessing`, which can influence whether the Batch Preprocessing Process (BPP) is utilized based on the account's settings.The behavior of the `meta.preprocessing` key is governed by the`fc.enable.batch.preprocessing` configuration setting. Below is a table outlining the expected behavior:
`fc.enable.batch.preprocessing `value
`meta.preprocessing` Value
Additional Info in Job Payload
Result
true
"preprocessing": "skip"
BPP should not be used
Do not use BPP
true
"preprocessing": "enabled"
BPP should be used
Use BPP
true
"meta": null or "meta": {}
BPP should be used
Use BPP
true
Omitted or previously created Jobs
BPP should be used
Use BPP
false
Any value
BPP should not be used (overridden)
Do not use BPP
When `fc.enable.batch.preprocessing` is `true`:
"preprocessing": "skip"
Action: BPP should not be used.
"preprocessing": "enabled" ( any value other than "skip" )
Action: BPP should be used.
"meta": null or "meta": {}
Action: BPP should be used.
Jobs without `meta`
Action: BPP should be used.
When `fc.enable.batch.preprocessing` is `false`:
Regardless of the `meta.preprocessing` value (including `null` or omitted)
Ensure that when setting `meta.preprocessing`, only the supported values (`"skip"` or `"any value not skip"`) are used to avoid unexpected behavior.
A job-level override will affect only the batches containing inventory data created under the specific job, and this impact will remain in effect until the job expires.
The URL is using the Job ID returned by the last API call, for example `199` as per the previous response: `POST/{{fluent.account.host}}/api/v4.1/job/199/batch`.