23-12-21 10:26 AM
28-12-21 08:20 AM
Ok, no response yet. I probably was not very clear in my original post. Lemme rephrase the question:
Assume we have an external supplier supplying us with BP objects for one of our many applications. These objects are widely used in many processes and also in several of our own objects.
Suddenly, it is discovered that these objects will no longer work with a new version of BP. As a result, our processes using these objects to access the application will no longer work. Luckily, our supplier reacts swiftly, finds a solution and delivers new versions of all their objects to us. The day is saved! (or is it...)
Most of the changes made by the supplier are changes in the input parameters on several pages in each of the changed objects. So now we have to find a way to implement these input parameter changes into our own objects and processes. As you are aware, every parameter change has to be handled otherwise our processes will no longer function.
When listing every modification made by the supplier that involved an changed input parameter, and following each of these changes all the way up to the process, we end up with hundreds of places where action must be taken to keep our processes working. So we need a list in order to split up this massive job and assign a chunk of it to each developer, we can call this list the To Do list.
Question:
How would you create the To Do list for this project in a handy format (eg. XL)?