Setting up your custom workflow
Last updated
Last updated
Creating a workflow for a project is made possible by assigning steps and numbering them. The user can define as many annotations, verifications, and other steps as needed for each project to create more complex workflows.
With flexible workflow customization, it is possible to add multiple rounds of verification instead of just one or skip the verification step altogether. The annotation can be divided into several stages, each of which annotates only certain classes. It is also possible to alternate between annotation and verification stages and add buffer stages to store selected files or prioritize certain files.
The project can consist of several stages:
Stage - Annotation
During the annotation process, the user has the option to choose a specific subset of classes to annotate at each stage. While the worker is annotating, only the classes that were selected for annotation in the current stage will be editable, and all other classes will be marked as read-only.
Stage - Verification
When verifying a project, the user has the option to choose specific classes to be verified at that stage. This selection does not impact the functionality of the editor - all editing options remain available during verification. However, it limits which objects and instances will be included in the Progress report as verified.
Stage - Misc (you can assign the Stage name yourself in the settings)
Stage - Final