Option B is a bit strange. Handling data validation errors within the Save service? Doesn't that just move the problem around instead of solving it? Shouldn't we be validating the data before it even gets to the Save service?
Option B is a bit strange. Handling data validation errors within the Save service? Doesn't that just move the problem around instead of solving it? Shouldn't we be validating the data before it even gets to the Save service?
Option D is intriguing. Applying an alternative merge result could be useful if the shared business object is being updated in multiple places. But I wonder how that would work in practice.
It's definitely a useful feature to have, especially in complex systems where the shared business object is accessed and updated by multiple components.
Yes, having an alternative merge result could prevent conflicts and ensure that the data remains consistent across all instances of the shared business object.
I'm not sure about Option E. Saving a specific version of the shared business object? Sounds like a recipe for disaster if you ask me. How would you even know which version is the correct one?
Option C is the obvious choice here. The Save service is used to validate or manipulate the data before it's saved to the shared business object. That's the whole point of having a custom service, isn't it?
I think option E could also be useful in certain scenarios. Saving a specific version of the shared business object can be important for tracking changes.
Virgina
3 months agoVannessa
3 months agoFletcher
2 months agoReed
2 months agoEvangelina
3 months agoDonte
3 months agoNelida
2 months agoMy
2 months agoDelisa
3 months agoTammi
3 months agoPortia
4 months agoRima
3 months agoChantay
3 months agoElza
3 months agoRozella
3 months agoAlline
3 months agoJina
4 months agoBrandon
4 months agoShad
4 months agoOlen
4 months ago