Resolving business automation conflicts
Business automation processes may conflict with each other, especially as the application grows in size and complexity. Solution architects review the business automation design, identify areas where these conflicts may occur, and make adjustments to the designs to prevent these.
A typical example would be a business process that relies on a record moving through a sequence of statuses. Individual processes may guide the record’s status, depending on their triggers and logic. As the application grows, so does its processes. The implementation team may lose visibility over the processes controlling the status of the record. In those instances, solution architects define a business automation process that is coherent and consistent throughout. A potential solution could be to implement state-machine business logic that ensures a record is always in the correct status.
Systematically problem-solving automation conflicts
Business...