JobBulkImportPostActions
This job is used only after a document import through the FileSystem Importer configured in "Bulk mode". That mode imports a large number of documents faster by deferring the application of the configuration to a second step. This job performs that deferred processing.
This job is disabled by default.
Parameters
{
"batch": "",
"actions": [
"copy_source_file",
"synchronize_dynamic_rooms",
"acl",
"fulltext",
"conversion_pdf",
"mark_as_finished"
]
}
By default, the job applies the post-actions on every pending content. The scope can be changed with the following parameters:
-
filter: GQL predicate used as an additional condition, for instance
"standard.status" = 'Approved'. -
query: full GQL query replacing the query on the pending contents, for instance:
select * from documents where standard.status = 'Approved' -
batch: added automatically to the filter or the query to only process the contents imported during a specific batch, for instance
"batch": "BATCH-001".
The actions parameter lists the post-actions to apply on the contents thus determined, for
instance "actions": ["copy_source_file", "fulltext"]:
- copy_source_file or move_source_file: copies or moves the file referenced as source during the import to the file repository of Any. If encryption is enabled, the file is automatically encrypted as defined in the global settings.
- synchronize_dynamic_rooms: synchronizes every dynamic room linked to the specified contents. The synchronization is optimized to only add the missing contents. It neither repairs nor removes the contents of the rooms. For room consistency problems, use the JobRoomsContentConsistency job instead.
- acl: applies the permissions of the ACL list if they are configured.
- fulltext: applies the full-text indexing on the specified contents, as defined by the related flow.
- conversion_pdf: applies the PDF conversion on the specified contents, as defined by the related flow.
- mark_as_finished: removes the "pending" state of the specified contents. To apply once every other action has been run.
To improve performance, depending on the server, the number of threads and the batch size can be controlled:
- nb_threads (5 by default): number of concurrent threads during the update. Can be set per
action with
nb_threads_<action>. - batch_size (default value controlled by the settings): number of contents updated per batch.
Can be set per action with
batch_size_<action>.
The impact of the number of threads and the batch size depends on the action.