Here’s a look at some of the new functionality in BeLazy.
The vendor portal API use case allows you to send translatable data to BeLazy and create a translation project that can then go into Plunet, BeLazy, or your proprietary business management system (BMS). It introduces the concept of workspaces and projects. You can find a detailed description here and a blog entry here.
We have introduced a new functionality that allows you to use BeLazy with auto-approve without opening the interface and still not lose projects: email notifications. BeLazy now sends you emails every time you receive your first red flag. If you get this email, open BeLazy, resolve all the red flags, and then you'll get another one if a new issue arises.
We have added a new menu called concepts to https://api.belazy.cat. It explains how to implement functionalities that are typically used, and also lists the values that are specific to certain connectors but not all.
We have improved the way languages are mapped and relaxed some of the stringent mapping requirements that prevented project creation.
Now you can auto-approve projects that are for certain end clients (e.g. only approve Microsoft jobs from this connection) and are in certain CAT tools (e.g. don’t auto-approve projects in SDL Trados).
We have identified some use cases where the connector did not include deadline and volume even if this data was there and we have improved the connector.
Simply too many… we have resolved all the known bugs, so if you had a problem earlier, make sure to recheck!