Legacy Estimation Config - Calculation Logic

Put Simply Statement:
APIs to connect legacy configuration to new estimation screens

Why it Matters:
Maintaining / modifying the calculation logic to function with legacy ePro config

What’s Needed:

• API modifications

Calculation Logic

There are series of APIs which does the calculation between the save and continue buttons some of them can be reused. If there are any changes in input selections (like drivers, complexity matrix, etc) this needs to saved in existing engagement schema in ePro and the subsequent calculations will be based on the updated values.

There are two options here:

1. We can combine these APIs into a single one which takes updated input and loads the required data in estimate side so that it will less burden on FE. But the con is there will be high processing time which will never meet the SLA and there are chances of API being timeout without completing the job.

2. Second approach would be keep these calculation APIs intact and carefully follow the sequence of execution from the FE. We will be closely helping in the integrations of all the APIs. This approach has less chances of API failure with timeout. The con here is, if we miss any of API the calculation will be impacted.

ALL ELSE WIP

Early ACs:

Other Notes:

Need to consider "in flight estimate resets"