I’m working on a large project that has evolved over time and is composed of several independent subprojects, each developed by a different team. While these applications have their own distinct purposes, they are interconnected and together form part of a complete workflow.
For context, an example would be:
• Application A manages the creation of a request to build a building.
• Application B is responsible for drafting the project with the architects.
• Application C handles the necessary permissions for the construction.
• Application D manages the hiring of staff to carry out the construction.
In total, there are about ten independent applications that together form a single functional process. The challenge we’re facing now is the creation of a “parent” application that centralizes and visualizes the information from these applications, providing a global view of the project’s status and details of each phase.
My concern is how to approach this “parent” application in a way that doesn’t overly depend on future changes in the “child” applications. For example, if in the parent BPM I query data from Application A to display in a table, but later new fields are added or the structure of the data changes, it could cause issues in the parent application without us realizing it. Additionally, since the development teams are separate, it’s difficult to ensure that every change in a child application is properly coordinated with the parent application, especially as the child applications will be constantly evolving.
My question is: what would be the best approach to structure this parent application to avoid dependency issues with the child applications, particularly when they undergo modifications or evolution? Are there best practices that could help mitigate these risks in a BPM environment like Appian?
Discussion posts and replies are publicly visible
One approach could be that
1) Every milestone steps from the child applications gets recorded in one table and then a report can be generated to provide an overview
2) You can create task reports for all the child applications so that you get other view of all the pending task and other such information from them.
Others might be able to add different approach as well