The bulk submission of a set of objects involves triggering their validation workflows (leaving them in pending status) or the automatic approval of changes where applicable (leaving them in approved status). The Objects > Actions on objects > Submit section explains in detail the difference between both options, which applies object by object in this bulk action.
When submitting for validation, the triggered workflows can be creation or modification workflows and only objects in draft status are submitted.
When this option is selected, the workspace objects are filtered to show only those corresponding to the chosen subtype that pass their form validations (i.e. that have all mandatory attributes filled in, for example), but from this list only those where the user has creation and modification permission in their organisational unit and whose status is draft can be marked for submission.
In addition, next to each object a text is displayed indicating, in the case of a modified object, whether the change triggers versioning or not.
If the text reads “Versioning reason”, clicking on it opens a window showing the same window that appears when the user submits an edited object from the object view.
When confirming the submission from the workspace, Anjana shows the user a window to select an expiration date for all objects that are going to be deprecated by the versioning. If any object to be deprecated already has the expiration date filled in, its value will be overridden by the value specified here.
Once the date has been selected and confirmed, if the user has only one role that grants them permission to submit the objects, the validation workflows for the objects will be triggered with that role.
If the user has multiple roles granting that permission, Anjana asks which role they wish to use to submit the objects for validation before triggering the workflows.
When the user confirms the submission, a window appears with the auto-generated job name that Anjana has created, which the user can modify if desired, and in this same window the user is given the option to remove the objects from their workspace after submission.
Upon confirming the job name, the progress of the process is shown to the user and, when finished, they can access the details.
When accessing the job result on the job detail screen, the objects can be seen with their current status, the date the workflow was triggered, and the job status for that object.
The triggering of the object workflows or their automatic validations are audited and the corresponding snapshots of the objects are saved.