When the Interactive Reporting document file is reopened, Interactive Reporting Studio reads the link information, connects to the repository, checks to see if the object exists, and checks if it has the same version number stored in the document. If the object in the repository has been modified, it will have a new version number, which indicates that Interactive Reporting Studio should update the old version saved in the Interactive Reporting document. For ADR to work properly, you must save a modified object with the original object name and model type, and save it in the same user-owned repository. Data models and standard queries (with or without reports) are synchronized using ADR.
The document repository tables are detailed in the following sections:
BRIOGRP2 Document Repository Table
Note: | The following tables, which were created in Interactive Reporting version 6.6 and prior, are no longer used nor will they be referenced by any aspect of Interactive Reporting Studio: BRIOOCE2, BRIODMQ2, BRIOUSR2, BRIOSVR2, and BRIOUNIQ. |
This table lists the details of the BRIOCAT2 table, which records a description of the repository objects and local documents loaded in the document repository
Table 237. BRIOCAT2 Table
Column | Datatype | Description |
|---|---|---|
UNIQUE_ID | NUM | Unique identifier for a stored Repository object. |
OWNER | CHAR | Creator of the object. |
APP_VERSION | CHAR | Version used to upload the object. |
CREATE_DATE | DATE | Most recent date of upload for the object. |
ROW_SIZE | NUM | Number of rows occupied by the stored object in the BRIOOBJ2 table. |
READY | CHAR | Indicates whether previous upload of the stored object was completed successfully. |
FILE_NAME | CHAR | Descriptive name of the stored object. |
FILE_TYPE | CHAR | File type of the stored object, such as data model, locked query, locked report, LAN-based, folder. |
DESCRIPTION | CHAR | Description of the object. |
VERSION | CHAR | Latest version number of the object, used for ADR. |
TOTAL_SIZE | NUM | Total size of the stored object in bytes. |
This table lists the details of the BRIOOBJ2 table, which stores the actual objects loaded in the document repository.
This table lists the details of details of the BRIOBRG2 table, which stores the associations between registered documents and repository groups.
Automatic Document Refresh (ADR) in Interactive Reporting Web Client enables the end-user to merge and synchronize locally saved Interactive Reporting documents (BQY) as soon as they connect to the repository with the latest version of the repository document. This feature is only for documents opened for the first time.
When a locally saved document is opened, a connection dialog for the Interactive Reporting database connection file (.oce) in the repository prompts the user to connect to the repository. The version information in the Interactive Reporting document is compared with the current version information for the document in the repository. If ADR has been enabled for the document, you are prompted to update to the latest version. The user can proceed with the refresh or not. After the document has been refreshed, the refreshed data cannot be undone. If the flag ADR is disabled for the document, the document refresh is not available and the locally saved document is opened as is.
The ADR synchronizing procedure is controlled at the system level and at the document level. Interactive Reporting Web Client ADR always refreshes the whole document. All the documents are published and stored in the repository with some ADR control flags enabled or disabled. Unlike in Interactive Reporting Studio, in Interactive Reporting Web Client there is no concept of Model Type.
Control flags determine if an Interactive Reporting document is eligible for ADR. These flags include:
ADR Global Flag—This flag controls the availability of the ADR feature. For a new installation of Interactive Reporting, this flag defaults to enabled. For an upgrade installation, this flag is disabled. You system administration can enable or disable this feature as needed.
ADR BQY Metadata—This flag is enabled or disabled when an Interactive Reporting document is published to the repository. If the flag is enabled, then only this particular document is allowed for ADR. For simple ADR, this flag is always enabled. ADR for job output defaults to a disabled flag when an Interactive Reporting document is published by a job action. In this case, a user can enable this flag by modifying the properties of the Interactive Reporting document. This flag is always disabled for a job output collection.
The following table shows how ADR behaves with documents in different scenarios.
Table 241. Simple ADR Behavior
Interactive Reporting document section in Repository version | Interactive Reporting section in local Interactive Reporting document | Action in Merged Interactive document |
|---|---|---|
Section does not exist. | Section does not exist. | No action |
Section does not exist. | Section exists. | Add from local document. |
Section exists. | Section does not exist. | Add from Repository document. |
Section exists. | Section exists. | Write Repository version. |