Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
| 73:custom_reference_models [2019/10/16 22:59] – emr | 73:custom_reference_models [2022/04/04 14:24] – emr | ||
|---|---|---|---|
| Line 18: | Line 18: | ||
| Reference models can also be mapped onto other reference models. For example, it may make sense to map evidence tables in the appendices of some standards onto the standard requirements themselves and then trace your processes only onto the evidence tables. The Compliance Traceability report can then use the cross-reference-model-mappings to show compliance to the original standard without having to map to it directly. | Reference models can also be mapped onto other reference models. For example, it may make sense to map evidence tables in the appendices of some standards onto the standard requirements themselves and then trace your processes only onto the evidence tables. The Compliance Traceability report can then use the cross-reference-model-mappings to show compliance to the original standard without having to map to it directly. | ||
| + | |||
| + | ===== Version Management of Reference Models ===== | ||
| + | |||
| + | The standard version management for reference models is not supported, so reference models can only have one version. | ||
| + | |||
| + | If you need to version reference models, the models need to be copied to different workspaces, e.g. " | ||
| + | |||
| + | **When reference models are imported into Stages 7.8 or later, the automatically created version " | ||