Questions?

I'm curious how xtrf determines what does and does not get included in the APIs.

This is sort of of a loaded question since I've recently ran into a couple of missing items that I was/am totally baffled as to why they aren't available.

One is the inability to get meta information about custom fields. Maybe I'm unique in wanting to use the API in this manner, but when constructing front end tools to interface with xtrf, needing, e.g., information about the options from a select control, or data type from an input, etc., for having the ability to dynamically and confidently render a web application that matches what is actually in xtrf would seem very fundamental. But this is missing entirely. Why?

Today while working from a spec that is requesting a web application to frontend our custom client creation process, one of the fields that was requested to set was the "Individual" option in the standard client data, and is in fact one the few options provided in the xtrf's own "add client" dialog in ui. There is no API support to be able to manipulate this option, so we pulled it and now have to instruct users to go set this field manually if they need this post create, not a great experience.

These are just two recent items, but my question, why is there this disconnect between how the xtrf platform works from the UI vs what's available through the API? It would seem obvious to me that if an option is made available through the UI, it should be added to the API as well as part of the same release version of the xtrf platform.

Am I unique here for how I want to use the xtrf API? I would certainly hope not.

It's as if there's a disconnect between the left and right hands here.

We have clients who regularly request certain language pairs for example FIGS.

So we were wondering if it's possible to create templates which the client can use when requesting quotes in the customer portal.

Thanks!

Hi,

You can add a new client either by adding a client, or from the project creation page (Add project) using the Add Client link. We have a situation where I'd like to add a custom field to the client that I'd like to make compulsory to fill out, and make the entry relatively easy.

My questions are:

- is there a way to make a custom field compulsory, i.e. you cannot enter or save a new client without adding that information? (like in Pipedrive, etc.)

- is there a way to make the data entry easy, i.e. make this field appear on the little form that pops up or the client creation page where only very limited set of data needs to be entered?

Thanks!

Istvan

Hi! We would like our vendors to read the "Instructions from PM"> "Instructions for all jobs" directly in the job email notification. Is there a variable already for that field? Is there a full list of variables available somewhere so that we can check?

Thanks!

The question is self-explanatory :) And such option would be just great... Thank you

Dear All,

is there any setting in XTRF that would make the system considered language variants of one language being the same language actually? We now have for example EN, EN-US, EN-GB variants but in general they all mean English. Still, if the vendor registers only one of the variants, they are not listed as a potential linguists for a job with different variant. This makes the process bit clumsy. Is there a way to fix it?

Thank you

I think we are one of the few companies in the Japanese market using XTRF, but we really would like to have a system-side solution for this. The problem with Japanese Yen is that no decimals are being used. There is no 0.1 yen. (Only in stock markets). Therefore, all invoices, POs, quotes need to be rounded to 1 yen. This is difficult when introducing percentage rates for CAT tools. This will almost always result in a decimal on the total. We have had a solution where only the templates would show rounded totals, but this keeps biting us in the ... We can have rounded total on 1 quote, but the system will store the amounts with decimals. So when we invoice for multiple quotes, the invoice totals will sometimes be different from the total amount of the rounded totals on the quotes. This is giving us some trouble with clients, since they have to go back and forth with their financial departments to correct this 1 yen mistakes.

I do understand there is an option to change the number of decimals in the system, but this is system wide. Since we do projects in USD and EUR as well, this is not really an option. Therefore, it would be really helpful if there was an extra setting for the currencies where we can select the amount of decimals for each currency separately. I am guessing there are some other currencies with the same issue (probably Korean Won and others).

We have been told some of this could be solved with a macro, but I think the above solution would work best.

Either way, I am happy to hear if there are people with similar problems.

Several users have informed us of similar issue. 

When vendor completes the registration process step by step but makes mistake at the services & rates section by making the same entry twice (for example, vendor made an entry for FR>DE simultaneous interpretation with the same specialization as for another entry - FR>DE, EN) they cannot finish the registration because it gives an error when trying to submit: "Oops... An error occurred while we were saving your data. Cannot define the same service option twice with different rates." And he cannot fix it from his side and remove the duplicate entry because the edit option does not work. Also he cannot delete the profile and start over because there is no such option. I tried to add him from my side and then send him a link to confirm registration however it just takes him back to the same view he had previously started to fill but cannot complete. Is there a solution for this apart from creating a new email address solely for XTRF Vendor portal? Nothing else seems to work.

How can we edit the instructions content formatting and add images to it?

Hello:

we are kind of new in XTRF and we are struggling with the rates, specilizations, etc.

Actually, the thing that everytime you add a language combination, XTRF sets the specialization for that language combination to ANY, makes the system to throw results that we don't want while searching for vendors to be assigned to a job.

We don't really see the point of having a specialization in the language combination level when they are already related in the rates' level.

Would anyone be so kind to give us an example on why the relationship between Language combinations and specializations is good for you? Even tough they are already related in the rates' level (list below in the Rates TAB)?

Thanks a lot for your time.

My best regards.

Juan.