The idea is that users can import their compliance analysis relationships:
The user must provide on the CSV:
- the compliance package name
- the unique hash of the item (see Feature - Compliance Correlation / Mapping - #3 by b.stephenson)
- and then all options available under “edit” on compliance analysis
Warning: you might run on the situation where an import is taking place on items which already have relationships (the user edited a compliance item and now wants to fix things with an import), ideally the import would “overwrite” but if this goes against the model logic then deny imports on such rows
Warning 2: imports must affect all “mapped” items