Adding related actions and record actions
Our application requires some master data such as supplier and account, but also some transactional data such as order and delivery. In a real IT infrastructure, this data would be managed by other systems and Appian would integrate them. Since these other systems are missing in our case, we have to manage this data ourselves.
This kind of data management requires separate operations to create, read, update, and delete data. In Appian, this translates to a record to make the data accessible and three record actions to create, update, and delete it.
Tip
The focus of Appian is the implementation of business processes. As a result of this design decision, there is no strong support for data locking mechanisms to prevent users from overwriting data by starting related actions in parallel. My opinion on this is that strict data locking should not be an important design goal for Appian applications. In a process design that is oriented towards...
