Currently, translation objects for all screens in the Software Factory are generated at the same time. This is undesirable if you want to execute this task directly after creating/modifying a specific type of object, as you suggest in this idea.

Therefore, we made it possible to execute this task by type or object in the 2025.1 release. As a result, translation objects are only generated for the screen you are currently on. This change reduces unnecessary data traffic and improves performance.

This approach allows for implementing this idea, generating translation objects directly and precisely when needed.

In the 2025.1 release, we have already applied this in one scenario: translation objects are now generated immediately after a variant is created, so you no longer need to do this manually. Also see:

Status update, progress so far: 

We have now reached the point where translation objects are generated after adding or modifying a translatable object via the CRUD buttons (using handlers). This will be available in the 2025.2 platform version.

The expectation is that we will soon continue by generating translation objects after adding or modifying a translatable object via create/copy tasks (this is already being done for the rename tasks).

---

Generating translation objects by an insert/update trigger is out of scope, as this would interfere with the branching and merging mechanism. This will mainly manifest when you add or rename translatable objects via the dynamic model, rather than using the CRUD buttons or the create/copy/rename tasks. However, this will automatically be corrected, as the task 'Generate translation objects' is still executed with each definition generation.

We now also extended this functionality to tasks and enrichments that create or copy translatable objects. Rename tasks were not affected, as this functionality was already implemented for them. This will be available in the 2025.2 platform version.