I have a process like this. I want to use transaction constraints on three write record nodes. Is there some easy way I can implement my require.
another question is what the functional of sync records.
I have read this document. https://docs.appian.com/suite/help/25.2/Sync_Records_Smart_Service.html But I don't understand the node's function and what scenario will use this node. I think when I use the write records, the data has already update into the database and sync automatically, why I need this node.
Discussion posts and replies are publicly visible
For transaction constraints, its good to define the relationships between tables efficiently in database as well as during record type relationship configuration. You can allow the related records to be added/updated / deleted with the base records using single Write records node. You won't need three nodes and Appian will commit the transaction only if all the operations are performed without any errors.
I suggest to go through the below documents thoroughly to understand this :
docs.appian.com/.../Write_Records_Smart_Service.html
https://docs.appian.com/suite/help/25.2/record-type-relationships.html#allow-writes-and-deletes
Anyway if you want the transaction to be applied via code and logic let me know and I can share a workaround for that.
For sync records smart service - there are use cases when we want to sync the record deliberately to refresh data. E.g. some data manipulation is done via a store procedure call in process model and then you need to re-sync record data. Some other example use cases are mentioned here https://docs.appian.com/suite/help/25.2/Sync_Records_Smart_Service.html#examples