Questions?

Quick question... I vaguely recall reading/seeing somewhere that XTRF will removed classic quotes/projects altogether and basically force us to use smart quotes/projects. Can anyone confirm/deny that?

Hi,

I wanted to ask about the possibility if the project manager could assign tasks to translation section head, then translation section head assign each task to the available translator or reviewer in his section?

Is this possible?

Something that I just realized. We frequently clean up the archived quotes and project files on our server. I've noticed that we have a lot of old projects that keep getting re-archived. For awhile I've assumed that it was because PMs were opening and adjusting these files. But I decided to look into it and it turns out that XTRF seems to continually re-archive old canceled projects if there is still an open ("Started") job in the workflow. (This is for Smart Projects, I haven't checked for Classic).

I'm going to start informing our PMs that to cancel your project you also need to make sure all jobs are canceled as well. Has anyone seen this? Is there a reason for this that I don't see or is this a bug/fluke?

Hi everyone,

I just found out that there is the possibility to execute the Macro API with parameters. This would be great as I currently use a sketchy workaround.

My API documentation doesn't say anything about the parameters, and this is what I have found in one of the XTRF documents:

Parameterized Macros Available via API calls
Why? HP REST API didn't officially support executing XTRF Macros. Macros didn't support additional parameters
that could modify their behavior. Support for macro parameters has been added.
What? API call POST /macros/{macroId}/run enables executing a macro operation with parameters.
Where? Home Portal API.
Reference: DEV-7597

Did someone get this to work already? Or can XTRF tell me what needs to be done in order to get the parameters to get over to the macro?

Kind regards,
Dennis Rosenbaum

Hello,

how would you get a list of the job types used in Receivables?

This job type:

I would like to ask if there could be a way to recalculate Payables, the same way that Receivables can be recalculated in classic projects? 

Right now the only way to update Payables to reflect changes in the provider's price profile is to remove and add again Payables. But if there is such functionality for recalculating Receivables (on the project level), why can't there be a possibility to recalculate Payables on a Job level?

Hi XTRF team,

Is the following scenario possible with XTRF / Memsource integration?

1. I create a project in XTRF with just 1 file uploaded and 1 job created

2. It is pushed to Memsource via integration

3. I split the file in Memsource and assign to 2 vendors

4. 2 jobs are created in XTRF and the vendors are assigned?

Thank you

Natalia

It doesn't look like XTRF support 2FA for regular users (like translators, PMs)  based on my search. But I wanted to double check. It would be great if you can share the link to a XTRF.eu website that is confirming it if it does support it. Thank you in advance.

My company is doing a deep dive evaluation on moving to XTRF and trying to kick the tires a bit on the API.
We've attempted posting this question though the "preferred" Stack Overflow channel, but not getting any feedback (and doesn't appear to be getting much traffic), and frankly we don't have a ton of time for waiting too long.
Here's a question one of my devs has posted on SO and we'd like to determine best course of debugging such matters.

thanks in advance for any help on this matter.

We are considering changing the installation and deployment method of XTRF TMS for OnPremises customers. Given that current industry standard is Docker, that would be our target.

However, if we go that route, given our not-so-unlimited capacity, we would deprecate and remove the current Windows and Debian packaging after a few months from introducing Docker.

What do you think about such change?

Jakubowski Marcin
XTR Maintenance Manager