In our business we have a requirement to have the EDI data visible to the customer service reps.
To this end we have created a web page modeled after the WmTNWeb -> Analysis -> Transactions that has additional attribute selections in the query. This is working fine for us up to this point.
We now have to start archiving our data to get the old data out of the transaction tables and into the archive tables to improve processing performance.
The problem we have is that once the EDI data is in the archive tables it is no longer available to be queried by the customer service reps.
We have a business requirement to have the EDI data available for 2 years for the customer service reps.
Has anyone created services like “createDocumentQuery” and “documentQuery” in the wm.tn.query folder that can query the archive tables?
Our thought is to create views that are a UNION of the transaction table and matching archive table. Then have a new “documentQuery” service query the new views to be able to get data from both tables.
We would add appropriate indexes to the archive table to improve query response.