One of the primary goals of Dynamic Evidence is to provide an administrative-time alternative to traditionally developed Non-Dynamic Evidence. Within this was another configuration goal, namely that of generating as many Cúram artefacts as possible to reduce the complexity and number of artefacts that Cúram Administrators need to define. Such artefacts include Dynamic UIM Pages (for Create, Read, Modify, etc.), user interface Tab configurations, CER Rule Sets, Property files, Security Identifiers and Groups, CER Propagators, etc.
Initially this was targeted at customers who did not have development installations of Cúram, in that after creation or maintenance of Dynamic Evidence Types, the database would be the 'system of record' for these administrated and generated artefacts; database backups would ensure that this data was persisted.
However, for customers with Cúram development projects, it was necessary to locate and export all such generated artefacts so that they could be source code controlled. Typically the requirement would be to save such configurable artefacts as DMX, CTX, clobs, blobs, etc. using the Cúram Data Manager. This way once the database was recreated (a typical development-time activity in Cúram), any Dynamic Evidence Types would be persisted and would not have to be recreated every time.
To assist in this effort, a Dynamic Evidence Configuration Extractor tool has been provided in Cúram version 6.0 SP2. This tool extracts Dynamic Evidence configuration information from a runtime Cúram database, and writes it to the file system using standard Cúram development artefacts (DMX, CTX, XML blobs and clobs, Tab configuration files, etc.).