As part of implementing #739, it was determined that the backend should be determining what the last continuous active date, rather than having the frontend calculate this.
This involves updating the GET provider endpoint to add a field to all license and privilege records continuousActiveDate (name subject to change) which will be a simple date string in iso format which is the oldest date in which the record has been continuously considered active. This field will not be stored in the DB. It will be calculated at call time for every license and privilege record (these calculations do not require any additional API calls, so the in-memory calculation will be fairly performant for most use cases).
Notes
We are creating logic in #770 for generating history events, and we may be able to leverage some of this logic in this solution to return
Questions
Assumptions
Estimate
Tasks
Implementation Notes
As part of implementing #739, it was determined that the backend should be determining what the last continuous active date, rather than having the frontend calculate this.
This involves updating the GET provider endpoint to add a field to all license and privilege records
continuousActiveDate(name subject to change) which will be a simple date string in iso format which is the oldest date in which the record has been continuously considered active. This field will not be stored in the DB. It will be calculated at call time for every license and privilege record (these calculations do not require any additional API calls, so the in-memory calculation will be fairly performant for most use cases).Notes
We are creating logic in #770 for generating history events, and we may be able to leverage some of this logic in this solution to return
Questions
Assumptions
Estimate
Tasks
Implementation Notes