What this video covers
This video shows PDF export, AI project translation, and rollback tools.
Video points
- PDF export.
- AI project translation.
- Rollback.
Video chapters
- 0:00 — Export the project map to PDF
- 0:31 — Translate names with AI
- 1:01 — Review the translated project
- 1:15 — Rollback and add more context
Full English transcript
Automatic English captions from the published YouTube video, lightly normalized for product names.
[0:00] Here in tools menu we have two options up to now. like tools export map to PDF. We can convert this map to a PDF. So you can print it and it have been shown to be very useful for showing clients naming and so on. And then we have this one that is translate function that this allows us to convert the project erh language from in this case is in English. We can change it for example for Spanish. using the AI we can give him a context for example outlet in in Spanish there are several ways of of saying it. you can h express say how do you want to translate certain things. So the AI has context and if you go to translate and click translate basically this is going to convert with the AI all the naming
[1:00] once it's finished you can see how all the names are now in the new language. but suppose that you didn't like it the translation you can go to this new arrow roll back translation and it's going to say you if you want to roll back if you click on revert basically it's going to restore all the previous words. So you can test it and give you more context if you want to improve it.
Technical walkthrough summary
This video shows project documentation tools around PDF export, AI translation and rollback. The installer can produce a readable view of the Control4 map and translate project labels before export.
Translation is useful when ETS naming, installer language and client-facing language are not the same. The platform lets the installer review translated names before the .codu package is produced.
Rollback matters because translation and bulk edits should be reversible. The workflow keeps review and recovery inside the platform instead of forcing cleanup after Composer creation.
