When we send a job offer to a vendor, we'd like to put the "quantity" in the mail, because for some reason the average volume is often 0 (which is kind of strange). Is there a variable for quantity in the email templates?
Any update, please?
Hi Pawel,
Not sure how to reply here. This variable is not available for obvious reason - there could be multiple tasks (in assignment), and how to replace this variable with quantity, if there are many tasks? For this, we have average volume.
Strange that average volume is zero. Maybe you can help to find out cases when this value is zero? I can't reproduce - always have a value there, regardless how I create an assignment.
In fact, in most of test projects we created, average volume is 0. This is actually quite random:
This is the case for assignments. For Jobs, average volume is correct.
I just noticed that when creating assignments from this function, average volume is not updated.
This is a pity, because this function automates creation of assignments in multilingual projects.
Confirm! Indeed it creates zero average volume. Already in work to be fixed today. )
Hello Eugene, thank you, we really appreciate your responsiveness.
As you may have noticed on this forum, we are finding a significant number of bugs, including in the basic functions that, in my opinion, should have been spotted during utility tests.
We see the potential of TBM, which is why I am personally committed to its implementation, but as we handle several dozen multilingual projects a day, the complexity and number of bugs in TBM makes it almost unusable at this point.
To be honest, we feel like (free) RWS testers...
We wonder how this tool can be marketed in this state and also how other LSPs that manage multilingual projects do it?
Finally, are you planning a global update, which has passed all test procedures?
Hello Eugene, thank you, we really appreciate your responsiveness.
As you may have noticed on this forum, we are finding a significant number of bugs, including in the basic functions that, in my opinion, should have been spotted during utility tests.
We see the potential of TBM, which is why I am personally committed to its implementation, but as we handle several dozen multilingual projects a day, the complexity and number of bugs in TBM makes it almost unusable at this point.
To be honest, we feel like (free) RWS testers...
We wonder how this tool can be marketed in this state and also how other LSPs that manage multilingual projects do it?
Finally, are you planning a global update, which has passed all test procedures?
Don't think I can answer you something here. We fix about 2-5 bugs a week. It's not much. At the same time, constantly adding new features.
but as we handle several dozen multilingual projects a day, the complexity and number of bugs in TBM makes it almost unusable at this point
May ask to summarize? Because I keep contact with a lot of users who just use it.. no complains, pretty much projects per day. Could be great to know main problems for now? We'll be glad to fix. Indeed you have a lot of threads here, but I think we're answering everywhere.
This one, for example, is already fixed.
Translate
