Feature - dont force sync on compliance mappings

When you create a mappings it automatic sync in between source and destination … which is ok because whatever internal control, policy, etc will be sync.

When you remove the mapping the sync stops, but what already was sync stays on the “destination”.

We need to change this:

a- what if you want to see the mappings just as information or guidance without sync?
b- what if you decide to change the existing mapping to something different and you want what was sync not to be left there?

For this reason we need a third column on the mappings:

Field: Automatic Synchronization
Description: eramba will (or not) automatically synchronize Policies, Projects, Controls and Exceptions from the source to the destination.
Options: Yes, No

Careful with:

  • Mapping CSV Imports needs a new column: Select “yes” or “no” if you want source items (internal control, policies, etc) to be automatically synchronised
  • We need bulk-edits for this field alone on the mapping section (complianceManagementMappingRelations). If someone bulk edits this from “Yes” to “No”, you stop doing the sync and what was already sync stays sync. If someone bulk edits this from “No” to “Yes” you start the sync.

github: https://github.com/eramba/eramba_v2/issues/2634