Defines supported strategies with which to create new reports and edit existing ones. Choosing the correct report management strategy to meet your business objectives is critical to using Continuum's AMP reporting functionality correctly, so please consult our support documentation for more information.
Append any new modules to a report, creating the report first if it doesn't already exist; do not overwrite any existing reports. Useful for intentionally adding to an existing report, e.g. one that was just created recently, rather than creating a new report.
Overwrite existing reports when a report with the same ID or name already exists, deleting any existing modules in the report in AMP prior to repopulating it with any new modules. This is the recommended strategy for a more manual report generation workflow, e.g. when a developer is creating new reports from their own workstation, or when there is otherwise little reason to retain old reports. While using this report management strategy, make sure to specify active modules by name (via AMPReportingService#setActiveModuleByName) rather than by ID (via AMPReportingService#setActiveModuleById); any modules in the active report—including the active module, assuming it's in the active report—will be deleted from AMP next time AMPReportingService#submitAccessibilityConcernsToAMP is invoked, making the active module ID invalid before any test results can be submitted to the module in AMP it used to reference, which will cause Continuum to throw a NotFoundException.
Always create new reports, guaranteeing uniqueness by appending the current date and time as an ISO 8601 timestamp to the end of each report's name; do not overwrite or append modules to any existing reports. This is the recommended strategy for a continuous integration (CI) workflow, i.e. for a report generation process that's automatically performed periodically, or when you otherwise don't wish to overwrite any previous reports for record keeping purposes.