As a developer,
I want to extract and save contractAgreementIds for data consumption into the database after each data sync via IRS,
so that the data remains up-to-date and accurate without needing to restart the application.
Hints / Details
Currently, contractAgreementIds are only loaded during application startup.
The extraction and saving process should occur after each data synchronization via IRS.
Ensure that the database is updated correctly with the new contractAgreementIds.
Consider potential performance impacts and handle any possible errors during the extraction and saving process.
Acceptance Criteria
Backend
[ ] The application no longer relies on startup to load contractAgreementIds.
[ ] After each data sync via IRS, the contractAgreementIds are extracted and saved into the database.
[ ] The database reflects the most current contractAgreementIds without requiring a restart.
[ ] Appropriate error handling is implemented for the extraction and saving process.
Frontend
[ ] Execution of action "View parts" all contractAgreementIds will be used for filtering in deep-link
[ ] Filter expression using OR
Implementation
Change GET AssetAsBuild contractAggreementId of type string to contractAggreementIds of type array
contractAggreementIds will be appended
contractAggreementIds are ordered by created date
Out of Scope
Changes to the IRS data sync process itself.
Modifications to the application startup process other than removing the contractAgreementIds loading.
Any user interface updates related to contractAgreementIds.
As a developer, I want to extract and save contractAgreementIds for data consumption into the database after each data sync via IRS, so that the data remains up-to-date and accurate without needing to restart the application.
Hints / Details
Acceptance Criteria
Backend
Frontend
Implementation
Out of Scope