Plunet gives you the option to use custom fields and text modules in your orders. Because each user can set up different things in those fields, instead of configuring every detail in BeLazy, there are some fields you can simply link to an order template. Every single order that BeLazy creates in Plunet is based on an order template.
Most BeLazy users rely on a single blank order template. If you don’t already have one, here’s how to set it up:
Log in to Plunet, go to Orders > Templates, select New > Translation project template, make sure Order template is chosen, then click the + icon and save.
Since BeLazy can’t display template names, you’ll need the template ID instead. To find it, check your Last selected templates in Plunet, click on the template name, and look at the end of the URL. For example, if it shows “=5,” the template ID is 5; this is the number you’ll use in BeLazy.
Keep in mind that an order template is different from a workflow template. Most companies only use one order template, but if needed, you can create exceptions for specific customers, project types, or other criteria.
You are probably better off creating order templates for BeLazy rather than reusing the existing ones, because most Plunet users include languages in the order template. While BeLazy works with these, each order created using an order template with languages included will contain all the languages, and if there is a new language pair you receive, it cannot be added. Therefore we discourage users from using order templates with languages. Order templates should be primarily used to fill out all the order-level metadata (Plunet properties and text modules).
Note: When you are setting up BeLazy for the first time, it is enough to create an empty order template and use that one. You can return to the automation configuration later once you have mastered BeLazy logic and refine the settings.