Why does my model require base model "Enrichtments" for certains tasks of the SF?
Upgraded to 2025.2 and encountered issues with the Task “Assign rights” under the roles:
Another location was in our Base model which we use for the translations of de GUI objects for our 33 languages. The option to use the task “Translate using AI” seemed handy.
The error appearing was the following:
As this is a functionality of the SF, the though went to the direction of the base models of the SF itself, as the SF is developed in the SF.
It turn out that I was wrong and my own Model requires the base model “Enrichtments” for these task to work. (Thanks to Thinkwise support to figure this out).
Why make it so that the developer Model requires these for even a fundamental feature as assigning rights to roles? Why is this not part of the SF side of the model?
In a work model I can accept it a bit more, but to require this in our base model just to use the AI method for translations, I kind of see it as polluting the model. I can remove it again afterwards, but that is working around the issue.
I am curious what made it seems logical to not make these things part of the SF model itself.
Page 1 / 1
Hi Mark,
The Software Factory makes use of its own capabilities and thus requires some model objects that exist in base models. When you generate the definition of your model, these model objects are automatically added and make it possible to use these kinds of tasks.
I do agree we should add an upgrade script to automatically merge the base models into your work models to ensure these takss work immediately after upgrading, rather than after a definition generation.
@Mark Jongeling What is still unclear to me is why this is not contained in the SF functionality itself.
Like for example the translations by AI. I was expecting the task to be a process flow that uses an LLM Instruction action, which uses a Generative AI provider set in the IAM of the SF itself. The only configuration I need to do as a customer, is set it to the AI provider and AI model which we have registered.
That does exist even:
So, expecting the task to supply the parameters with the values of the selected translation and process the translation.
This it won’t do, because it needs external model objects which come out of the “Enrichtments” base model.
Perhaps you can shed some light on the confusion there?
@Mark_Plaggenborg, we chose to use Enrichments for this, so developers could deviate from the enrichment that we provide, by modifying the Enrichment code. Whilst not recommended to do in ENRICHMENTS MAIN, you can create a branch and modify the underlying enrichment to your liking. Perhaps you want to alter the prompt that is sent along with the translations, to further help the AI to translate objects.
Similarly for AI code review, this way you can add or alter the rules that the AI should check on.
Enrichments also add the benefit of suggesting model updates, allowing you as a developer to chose which updates should be processed. For Role rights for example, the Review changes shows the suggested model updates, and you can tweak where necessary.
If we would create this fully in the Software Factory model itself, the functionality is fully in our hands and developers are (generally) not able to change/influence anything. Also improving or fixing the process by a Platform improvement is a lot harder.
So we chose to use Enrichments over a dedicated process maintained by us.
