I work in financial domain and hence the requirement. Although I have not explored the complete CUBA paltform yet, but just curious to know if Cuba Platform supports out of the box functionality for implementing Maker/Checker for entities.
To elaborate more on Maker/Checker - It’s basically a functionality expected in almost all the entities that whenever a CRUD operation is performed on the Entity, it should not persist the changes like Insert new record/update or delete but rather store in some intermediary table or same table with a status of Unauthorised state. Once the changes have been authorized by another user of the system, it should persist in final table or update the status as Authorised. Also, to add more, a maker of an entity can’t be checker. Like one user who creates a record by creating an entity instance should not be allowed to authorised the creation. It has to be a different user.
More information can be found on search engine with terminologies such as Maker/Checker and 4 Eye principle.
My issue is if I start to implement this functionality for like 50 to 100 of entities in my project which I’m planning to implement in Cuba platform it will impact the development timeliness more than business logic. So wanted to hear from the experts and Cuba platform users their views around it such as suggestion to reduce this effort by having some global configuration in the platform or design approach to be followed before starting with the project.