HI db,
yes, what you describe is exactly what we do currently and that works fine within one application.
But currently we always copy this extender business rule from one application to the other to make it available there. From our perspective a System Extender would be the way to go to also make it obvious to everyone, that this rule is not only used by one application and that one should be really conscious when changing it.
We have the use cases: Logging, probably similar like you do and formatting CVs, where we have quite complex logic in place to ensure they're all formatted according to our corporate style guide. Furthermore, the idea would be to extend this to other topics like our SAP BW connection/running of SAP BW process chains and various other things that could be shared between applications.
Thanks
Markus
Totally makes sense. My understanding is that System Extenders are for managing Azure/Environment. I wonder if you could put your logic into a DLL and then reference that from all applications? Not something we've done, but I know its possible: Organizing and Referencing Business Rules (onestream.com)
Yes, I think that would be possible to achieve this with a DLL. Unfortunately, parts of the code are still evolving and it would be super-useful to get it working in System Extenders. We do use those already on a environment only level for our user management and to retrieve/sync some additional user information from our AD and that works really good.
The idea would be to use System Extenders for these "environment-dependent" topics as we could then still easily change coding instead of having to create and deploy DLLs.
But might be that this is unfortunately not possible as so far we didn't find a way to reference the system extenders from the application business rules
