Difference between revisions of "Project details, Workflow tab"

Revision as of 13:16, 30 March 2023

Watch our video tutorial on Workflow —

General information

On the Workflow tab of a project, you can build chains of consecutive jobs by linking the existing jobs or by adding predefined job chain templates:

Both methods are described below.

Note: To be able to build chains of consecutive jobs within a project, it is necessary to specify language pair(s) when creating the project.

Chain existing jobs

To build a chain of consecutive jobs by linking the existing jobs, click the "Chain job" button and select the language pair:

It will display the Chain existing jobs page where you can drag and drop the jobs you need to be linked into the highlighted in green New job chain field:

Having done that, click "Create" to add this workflow to the project:

It will bring you to the project workflow tab where you should click on the job ID to open the job page to be started first:

Click "Offer to vendor" on the opened job page to lunch the workflow:

Every next job will be proposed to vendors, and the assigned vendors will receive the corresponding notification:

The very first job in the chain will be started automatically (gets the "Started" status) once the assigned vendor accepts it:

The next jobs in the chain will get "Offer accepted" status (if vendors accept them/confirm their availability) and will be launched/shifted to "Started" status (with a corresponding notification to the vendor) after the previous job is completed:

The output files of the previous job will be automatically transferred to the input files of the next job in the chain.

All the workflow participants will receive corresponding notifications during the process.

If necessary, on the Workflow tab of the project you can also add another job chain, break chains, and update jobs by clicking corresponding buttons.

Back to the table of contents.

Add job chain template

To add a predefined job chain template to the project workflow, click the "New job chain" button:

Then select the job chain template you need from the drop-down list, tick the language pairs you need, and click "Create":

You can tick as many language pairs as you need.

After that, you should assign every job in the chain to your vendors and set deadlines.

To do this, click on the "Update" button:

Then select the vendor, set the deadline and click "Update" to save changes:

On the project workflow tab click on the job ID to open the job page to be started first:

Click "Offer to vendor" on the opened job page to lunch the workflow:

Every next job will be offered to vendors, and the assigned vendors will receive the corresponding notification:

The very first job in the chain will be started automatically (gets the "Started" status) once the assigned vendor accepts it:

The next jobs in the chain will get "Offer accepted" status (if vendors accept them/confirm their availability) and will be launched/shifted to "Started" status (with a corresponding notification to the vendor) after the previous job is completed:

The output files of the previous job will be automatically transferred to the input files of the next job in the chain.

All the workflow participants will receive corresponding notifications during the process.

If necessary, on the Workflow tab of the project you can also add another job chain, break chains, and update jobs by clicking corresponding buttons:

Back to the table of contents.

Job statuses and notifications in a workflow

For more details on job statuses, please check Job statuses page.

• Offered to vendor - a job gets this status after you click the "Offer to vendor" button.

Once you offer the very first job, every next job gets this status:

The vendor of the first job gets the usual job offer notification (the Auto start on vendor acceptance checkbox should be marked for the job to start automatically):

While other vendors in the workflow get availability request for a future job (the Auto start on vendor acceptance checkbox should be unmarked for the jobs to start after the completion of the previous one):

• Offer accepted / offer rejected.

The vendor can accept or reject the job:

Note: If a job doesn't have the "Offer accepted" status, it will not be started after the completion of the previous job:

And you will get the following notification:

If a vendor accepts the job before the completion of the previous one, the job will be started automatically.

• Started.

The accepted job is started automatically unless it is the non-first job of a workflow:

If it is a non-first job of a workflow, then it starts after the previous job is completed:

Vendors of the non-first job get corresponding notifications:

Note: Make sure that vendors are assigned to every job in the workflow. If you offer the first job, but other jobs don't have vendors, you will need to offer and start them manually.

For more details on job statuses, please check Job statuses page.

• Estimated start date

If you set deadlines for your jobs, every time vendors get the availability request, they will be able to see the approximate start date:

If it's a tender as a part of the workflow, vendors will see the estimated start date as well:

Back to the table of contents.

Tenders in workflow

You can create a tender for a job that is a part of the workflow.

More details on tenders please find here: Create job tenders

First claimer tender

If a tender is the first in the job chain, you need to start the tender and offer the second job to the vendor (every next job will be offered to the vendors automatically).

Once the vendor claims to the job, it will be started automatically.

Then the workflow works as always: once the first job is completed, the next vendor will be able to start working (if they accepted the job).

If a tender is not the first in the job chain, you need to open the first job, and start the chain.

Every job except for the tender will be offered to vendors:

You need to start the tender manually.

Note:

• If a vendor claims the tender before the first job is completed, the workflow will work as it should.

• If a vendor claims the tender after the first job is completed, you will need to start the tender job manually.

Selected by manager tender

If a tender is the first in the job chain, you need to start the tender and offer the second job to the vendor (every next job will be offered to the vendors automatically).

Once you assign a vendor to the job, it will be started automatically.

Then the workflow works as always: once the first job is completed, the next vendor will be able to start working (if they accepted the job).

If a tender is not the first in the job chain, you need to open the first job, and start the chain.

Every job except for the tender will be offered to vendors:

You need to start the tender manually.

Note:

• If you assign a vendor to the tender before the first job is completed, the workflow will work as it should.

• If you assign a vendor to the tender after the first job is completed, you will need to start the tender job manually.

Back to the table of contents.