Question - Mapping processes to critical assets and third parties

We are considering some new relationships in eramba to address the need to link “Processes” (not just Business Units) to Assets and Third Parties.

Current relationships:

Proposed relationships:

The idea is that Business Units can be linked to Third Parties. Since many people needs also to select processes, we will allow such relationships as we do in Business Risks where the user selects Business Units and we let them choose Processes that relate to those selected Business Units.

The summary of the change:

Field Descriptions:

  • BU: Select one or more Business Units that relate to this item
  • Process: Select one or more Process related to the Business Unit you selected on the field above

Notes:

  • The user must select first a business unit, then we display the related business units processes alone
  • CSV Imports must be updated on Assets, Third Parties module
  • Views must include the columns “Business Units” and “Processes” to be included and shown by default
  • The Process needs a naming convention $ProcessName ($BU name)
  • Please handle the edition of the fields carefully:
    • Addition of a BU: if the user has a BU already selected with 3 process and then “Adds” a BU on the dropdown (having two selected), do not refresh the “Process” field by removing what was already selected. Leave there what was selected and let the user choose more options.
    • Removing a BU: if the user removes a BU that was selected, simply remove the Process related to that previously selected BU, do not empty the “Process” field completely.
  • New installs and existing installs get these fields displayed by default, they can hide them if they want using customisation (those optional fields)

The business risk module includes some MTO, RTO stuff. Do not use any of that in Assets and Third Parties. We will update the Risk module later on.

github: https://github.com/eramba/eramba/issues/4876