...
You can download a Combined metrics report which will group together all the Metrics from the projects you have selected for that report. However, there is currently no report that would show you the character count for specific projects.
How to generate a PO (Purchase Order) that would exclude XTM Cloud jobs with full TM leveraging?
Sometimes, it might happen that in a newly created XTM Cloud project containing multiple jobs one of the jobs will receive full TM leveraging (ICE matches), which usually makes all the segments in XTM Workbench auto-propagated and a that specific job finished in an instant.
...
The vendor assigned to this job makes use of such rate card factors as, for example, minimum charge or fixed price per project/language, which might only generate redundant costs.
...
Therefore, you might want to exclude such XTM Cloud jobs from the costs of a generated Purchase Order (PO).
XTM Cloud offers two convenient ways to achieve that:
The first way is to create and assign the so-called dummy user (or dummy assignee) who does not have any rate cards configured, or has one with all values to “0”, to this specific workflow step (Project Editor → Workflow).
...
To mark a particular user as a dummy user, go to the user’s settings → General → General info, and select the Dummy user for cost generation checkbox.
...
When you do so, this user will be suggested as an assignee whose rate cards can be used for project cost calculation. Their name will be displayed in the Dummy assignee dropdown list in the Project Editor → Costs tab.
...
| Info |
|---|
Keep in mind that once you have assigned such dummy user to a fully leveraged workflow step, you do not necessarily have to use the Dummy assignee field, and you can generate costs straightaway. This is because the steps with full TM leveraging will be charged in accordance with the dummy assignee’s rating. If, however, you would like to use the mentioned field, you should first unassign the affected vendor from a particular workflow step and leave it as it is. Then, going back to the Estimates → Costs tab select a relevant dummy user from the dropdown and make sure to select where no assignment. In this way, you will also ensure that those empty workflow steps will be charged in accordance with the dummy assignee’s rating. |
The second way is to mark the problematic workflow steps as non-chargeable. To do so, take the following steps:
As a user with administrative role, go to Configuration → Data → Estimates → Cost settings → Cost settings, and select the Show Chargeable checkbox in Workflow Editor checkbox, to enable manual selection of chargeable workflow steps directly in the workflow editor.
...
Next, go to your XTM Cloud project and go to a specific source file, to which workflow you want to make changes, since you can perform workflow adjustments at the level of individual file [Project Editor → Workflow → (select a target language) → (select a file) → (click on the context menu) → Change workflow / due dates].
...
In the Workflow Editor for this particular file, you can decide which workflow step will be subject to charge, by selecting the Chargeable checkbox under a relevant step.
...
In this way, you will ensure that the workflow steps in question will not be incorporated in the PO costs.