Framework understanding

@loginerror

what is the approach to understand any legacy framework when you dont have any documents like as-in process, to-be process, tdd,sdd or any other
since it was not given by previous developers

Hi @Sakshi_Jain

In the end, all processes are a one long sequence of events. The way to understand it would be to go from the starting point and follow each activity one after another (this could be done either in debug by using the Step Into option, or even without running the process).

I am afraid the IT world is full of these kind of undocumented scenarios and there is no “quick” hack to get past careful evaluation of the process.