Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Migrating document metadata

Updated on June 11, 2021

After the Requirements module is active and ready to use, you must implement the migration process for the documents metadata.

When the application runs in 1G in your production environment, the system collects multiple documents and metadata that the legacy data structures store. The new version of the functionality comes with new data structures that provide flexibility and enable the future evolution of the module.

The migration process ensures that all documents and metadata captured in 1G becomes available for its use in 2G. There are two upgrade strategies supported:

Under this model, the system, as required, steadily migrates the metadata associated with the documents. Every time one journey requires access to the documents of a given customer, the system executes an on-demand migration that copies all the document metadata available for that customer in the legacy data structures into the new ones. The process is transparent to final users, who do not know about the migration happening behind the scenes. The on-demand migration strategy is by default.
Bulk migration
The application provides a set of tools to do bulk migration of document metadata. The tools must be executed right after the activation of the 2G functionality in the production environment. Once it is executed, all the document metadata remains in the new 2G data structures, and the legacy data structures are not accessed anymore.

To determine which migration strategy is the more appropriate for your organization, consider the following factors:

Number of documents per customer
The on-demand migration can easily manage a handful of documents per customer without having a significant impact on the overall performance of the application. Organizations with a large number of documents per customer (in the order of dozens) might observe some delays when performing certain operations (mainly, in the transition between data-capture and enrich, where the majority of the requirement cases are created).
Custom processes using 1G data structures
The on-demand strategy creates a situation where some of the data is in 1G data structures and some in 2G. All out-of-the-box processes are prepared to manage this dual source of document metadata. However, if your organization has any custom process of this nature, it needs to be adapted to deal with the new data arrangement that includes Pega processes and external processes that might receive the data through different data export mechanisms (for example, BIX).

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us