One-2-One - Records Management Interchange and Integration Options

EDRMS term and disposal data interchange.
One-2-One provides 2 methods to exchange term and disposal data with EDRMS systems. Interchange files from standalone mode, using an Access database for data storage, or via the optional EDRMS integration to a supported EDRMS system. EDRMS Integration is a true integration as it provides for viewing and immediate updating of data with the EDRMS system.

Non-EDRMS Integration installations:
Interchanges data with most popular record management systems, via formatted ASCII transfer files using by the records management import/export modules on the Export / RM ASCII menu.
These modules use format specifications, defined by the particular record management vendors, and may also include the capability to interchange Retention and Disposal information if that capability is defined by the vendor.
The limitations and inconvenience of using these files, such as inability to interchange deletion and renaming changes, is overcome completely by the One-2-One EDRMS Integration option.

EDRMS Integration optioned installations:

Direct Connect is an available option for the supported vendors listed above.

Includes the interchange transfer file capability, as above, plus direct integrated immediate transfer of changes to term and disposal data directly from the One-2-One screen into the chosen supported EDRMS system, via the API or SDK, for that system. The Direct Connect integration option provides true term and disposal data integration, because system verified changes are made immediately into the EDRMS system, as distinct from the delayed and possibly limited process of interchange.
An overview of Direct Connect capabilities for each supported EDRMS vendor may be seen by clicking on the required button to the left.

How safe is EDRMS Integration?
Some clients have asked if One-2-One Direct Connect integration “might potentially corrupt their EDRMS database?”
The answer, borne out by almost 5 years of One-2-One use by a large number of users, is NO, it is quite safe.
One-2-One only ever uses the API/SDK facilities of vendor products. It never makes direct access to the actual underlying database used by the EDRMS system.
An API/SDK is a connection interface, developed by the vendor, providing safe mechanisms to read and write data to the database. Any potential dangerous requests are blocked by this interface thus ensuring the integrity of the EDRMS database is always protected.