The Requirements module manages the documents and metadata that are stored by default in internal tables in the Pega database. Some organizations, however, might need to integrate with their corporate Document Management System (DMS) or Web Storage providers to share those storage responsibilities.

The Requirement module supports three different configurations to facilitate integration with providers.

Physical documents and metadata stored in Pega

Default implementation provided by Requirements application, where both document metadata and the physical document are stored in the Pega database. No integration is required to support this scenario.

The configuration comes out of the box, and no changes are required.

Physical documents stored in DMS and metadata stored in Pega

Under this configuration, the document metadata is maintained in the Pega database tables, while the physical document is stored in Document Management Systems (DMS). The integration with the external system is established through the out-of-the-box Pega capabilities to store documents in DMS using CMIS. The capabilities support Web Storage providers as well, for example, Box, S3.

The configuration can be easily configured using Pega platform capabilities and does not require changes in the Requirements module. For more information, see instructions available at File and content storage.

Physical documents stored in DMS and metadata stored in both Pega and DMS

The model extends the previous configuration by implementing a data propagation mechanism that transfers the metadata captured through the Pega application into the DMS system. The metadata synchronization process ensures that all metadata maintained internally by the Pega module is made available to the enterprise through the DMS application.

The configuration requires, in addition to the configuration for the previous one, the implementation of certain rules.

• Document and requirements metadata