Discontinued features in XTRF 7
Hi,
We just read about the changes planned for the new version and I am more curious about what we won`t find there anymore, because here we always had the biggest surprises.
I copied here the list and please briefly tell us what happens with each of them...and maybe why:
- Old Document Templates Engine (BIRT2)
- Quote Registration Form (the old one)
- FTP Access
- SOAP API
- Support for versions older than 2014 of SDL Trados and memoQ
- Insecure HTTP access no longer supported
Thanks a lot,
Dan Daniel
Answer
Old Document Templates Engine (BIRT2)
BIRT 2 templating engine was replaced with BIRT 4 in XTRF 4.0 (long time ago). It is no longer maintained, so we also decided to drop support for it. Most document templates on your XTRF instances already use BIRT 4. Any obsolete BIRT 2 templates will be automatically upgraded to be compliant with BIRT 4 when installing XTRF 7.
Quote Registration Form (the old one)
Old Quote Registration Form was replaced with the new Quote Request Form in XTRF 5.0 (long time ago) and is no longer maintained.
FTP Access
FTP is considered unsecure (no SSL support) and requires dedicated software. That's why XTRF offers a much more secure and powerful browser-based solution: Vendor Portal and Client Portal. They both allow files exchange within projects, quotes, jobs and job offers.
SOAP API
SOAP API was replaced by REST APIs long time ago and is no longer maintained. All API users are encouraged to use Home Portal API and Client Portal API – both following RESTful approach.
Support for versions older than 2014 of SDL Trados and memoQ
These CAT Tool versions are no longer supported by SDL and Kilgray.
Unsecure HTTP access no longer supported
Vulnerable information (secrets, user passwords, translation files, financial reports etc.) should not be transferred unencrypted over the network (especially a wireless one). A world standard is to use secure HTTPS protocol for any website and gradually remove support for unsecure HTTP. XTRF supports HTTPS for a long time and drop of HTTP support is a move towards increased security of our Clients' data.
Mikołaj, if we still have our customized BIRT 2 templates, do I understand it right - you will upgrade them for us when performing the update?
Thank you for posting this! Following because I'd also like clarificationon what Svitlana asked.
If your document templates are still in BIRT 2 and it was us who prepared them, then we will update them.
Please plan well ahead of time to get the templates running in BIRT 4 before you decide to upgrade to XTRF 7.
Contact our service desk to proceed.
Thanks for this, really good to know. Have to say though, we are disappointed to see the support for FTP go. First of all, SFTP is possible and can be secure, second the method of having our PMs log out and login to the Vendor Portal in order to upload files larger than 1GB is very, VERY cumbersome. Further, we have had issues with uploads larger than 1GB through the vendor portal, and normally resort to FTP in such cases. Hopefully either file management is improved by letting project managers upload large files from the home portal, or some other file management solution. It's always been a little bit tough to understand why a PM can't upload a file just as large as a client or a vendor without logging into a separate portal.
I agree that the file management is cumbersome particularly for large files. We'd love to see this improved.
Customer support service by UserEcho
Old Document Templates Engine (BIRT2)
BIRT 2 templating engine was replaced with BIRT 4 in XTRF 4.0 (long time ago). It is no longer maintained, so we also decided to drop support for it. Most document templates on your XTRF instances already use BIRT 4. Any obsolete BIRT 2 templates will be automatically upgraded to be compliant with BIRT 4 when installing XTRF 7.
Quote Registration Form (the old one)
Old Quote Registration Form was replaced with the new Quote Request Form in XTRF 5.0 (long time ago) and is no longer maintained.
FTP Access
FTP is considered unsecure (no SSL support) and requires dedicated software. That's why XTRF offers a much more secure and powerful browser-based solution: Vendor Portal and Client Portal. They both allow files exchange within projects, quotes, jobs and job offers.
SOAP API
SOAP API was replaced by REST APIs long time ago and is no longer maintained. All API users are encouraged to use Home Portal API and Client Portal API – both following RESTful approach.
Support for versions older than 2014 of SDL Trados and memoQ
These CAT Tool versions are no longer supported by SDL and Kilgray.
Unsecure HTTP access no longer supported
Vulnerable information (secrets, user passwords, translation files, financial reports etc.) should not be transferred unencrypted over the network (especially a wireless one). A world standard is to use secure HTTPS protocol for any website and gradually remove support for unsecure HTTP. XTRF supports HTTPS for a long time and drop of HTTP support is a move towards increased security of our Clients' data.