Limitations in Archived view
The Archived view in OneView is designed to allow visibility into data stored in Data Fabric. It offers a similar visual representation and interaction model as the standard Message Timeline view, with a few limitations based on the archived nature of the data.
These features are limited or unavailable:
- Payload visibility: Payload is available only if a route was created to send it to Data Lake and it was not purged from Data Lake.
- Group by Document ID: This feature is not available in the Archived view.
- Sort by Document ID: Sorting based on Document ID is not supported.
- Notifications: Notifications feature is not available in Archived view.
- Content-based properties: Properties like Document ID, Accounting Entity, and Location derived from content are not available.
- Count Instances: This is shown only if a route was created to send payload to Data Lake.
- Message Status Indicators: Message Status Indicators are not available in list of messages and summary panel.
- Count instances in Batch: Count Instances in Batch is not available in Archived view.
- Resubmit No Route Messages: Messages that have no route defined cannot be resubmitted from Archived view.
- Performance: The Archived view may take slightly longer to load compared to the Message Timeline due to the amount of data being retrieved, the search criteria used, and the performance of Compass queries.
- Timeline depth: The Archived view initially displays only one level of timeline in case of horizontal and 5 levels in case of vertical. You can click to load the next 1 level at a time.
- Although you can access the latest data in the Archived view, we encourage you to use the Message Timeline for an optimized experience when the data is still within the retention period.
- If you have not opted to send your connect data to Data Fabric, there will be no information in the Archived view to retrieve.