Bulk submission of a set of objects triggers their validation workflows (leaving them in pending status) or the automatic approval of the changes if 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 workflows that are triggered can be creation or modification workflows, and only objects in draft status are submitted.
When this option is selected, the objects in the workspace are filtered to show only those corresponding to the chosen subtype and that meet their form validations (for example, having all mandatory attributes completed), but from this list only those objects whose organizational unit the user has creation and modification permission for, and whose status is draft, can be marked for submission.
In addition, next to each object a text appears indicating, in the case of a modified object, whether the change triggers versioning or not.
If the text indicates "Versioning reason", clicking on it opens a window showing the same window that appears to the user when submitting an edited object from the object view.
When confirming the submission from the workspace, Anjana shows the user a window to choose an expiration date for all the objects that will be deprecated by the versioning. If any object to be deprecated already has an expiration date filled in, that value will be ignored and the value indicated here will prevail.
Once the date has been chosen and confirmed, if the user has only one role that grants them permission to submit the objects, the objects' validation workflows will be triggered with that role.
If the user has several roles that grant them that permission, Anjana asks which one they want to use to submit the objects for validation in order to trigger the workflows.
When the user confirms the submission, a window appears with the name that Anjana automatically generates for the job, which the user can modify if desired, and in this same window, the user is given the option to delete the objects from their workspace after submission.
After confirming the job name, the progress of the process is shown to the user and, once finished, they can access the details.
When accessing the job result, on the job detail screen, you can see the objects with their current status, the date the workflow was launched, and the job status for that object.
The launching of the objects' workflows or their automatic validations is audited, and the corresponding snapshots of the objects are saved.