If you’ve published multiple version sets of a dynamic view, eaDirect must determine which associated version set to use for live statement retrieval.
When a user retrieves a statement, eaDirect determines which published version set to use according to the following rules:
1. Last version set published on the day the data file was indexed. eaDirect first looks for and uses a version set published the same day the data file was indexed.
If more than one version set was published the day the index was created, eaDirect uses the set with the latest timestamp before midnight (up to and including 11:59:59) on that day. (eaDirect does not remember the time of day the index was created, only the date, therefore the time Indexer ran is not a factor in determining which version set to use; eaDirect always uses the version set published latest in the day.)
2. Most recent version set published before the day the data file was indexed. If eaDirect does not find a version set published the same day the data file was indexed, it looks for the most recent version set published before the date the data file was indexed.
3. Next version set published after the day the data file was indexed. If eaDirect does not find a version set published on or before the date the data file was indexed, it looks for the next version set published after 00:00:00 the next day, looking forward for the first available version set.
Example: One Version Set Published Same Day
If you publish a dynamic web view version set on 8/7 at 10:00 am, and run the Indexer job at 11:00 am, when a user retrieves the 8/7 statement the next day, eaDirect uses the version set published on 8/7 at 10:00 am.
Example: Multiple Version Sets Published on the Same Day
If you publish a version set on 8/7 at 10:00 am, run the Indexer job at 11:00 am, then publish another version set at 3:00, the next day when a user retrieves the 8/7 statement, eaDirect uses the 3:00 version set, since it was the latest set published on the day the index was created. The time of day the Indexer job ran does not determine which version set eaDirect uses; it uses the latest set created on that day.
Examples: Multiple Version Sets Published on Different Days
A. If a user retrieves a statement with an index date of 10/30, and the associated version sets are dated 10/25, 10/26, 10/31 eaDirect uses the 10/26 version set.
B. If a user retrieves a statement with an index date of 10/30, and the only associated version sets are dated 11/01 and 11/08, eaDirect uses the 11/01 set.