SUP synchronization as transactional operation
can you please clarify how SUP can manage the atomic behaviour of operations in a synchronization? (SUP 2.1.3 native RBS android app)
How can we achieve the transactional effect of sending operation replay requests to SUP from various MBO's and having those operations to either succeed and execute all or rollback all in case of failure? (against SAP backend)
If we put all MBO's are in the same sync group, will that be enough to synchronize as transactional data?
Do the MBO's need to have relationships between them?
Two paths must be accountable:
Device -> SUP and SUP -> SAP
Can both be controlled and make the operations (creates and updates) happen in an "all or nothing" approach?