Feature - Custom Field types to link to other records

Forum - Software
1

I think it would be extremely helpful and introduce a lot of flexibility if we were able to create custom fields that allowed us to select from a list of specific record types to link them together.

For example, there’s a post I just commented on in Asset Management about being able to link Processes to Assets. Similarly, we would find it very useful to be able to link Third Parties to Assets.

I imagine it working like this. You create a custom field like normal, then in the ‘Type’ selector there would be ‘Existing Record’ and ‘Existing Record - Multiple Select’.

To choose which record you want, there can be a simple tree-type menu that shows primary record type (Asset, Third Party, Process, Policy, Risk, etc). By default the Name field of the other record would be displayed, just like when linking existing records that are built-in.

For further flexibility, once a primary record type has been linked, there would be an option for additional Custom Field types in the ‘Type’ selector: ‘Linked Record Field’. If you chose that Type, a menu of existing fields inside the primary record would be displayed (Name, Owner, Description, various Custom Fields, etc)

image
image1137×713 13.2 KB

2

hello !

u mean being able to define custom fields that link to other sections? so if you want to link assets to process (which does not exist) , you go to assets and add a custom fields that “lists” processes?

if that is, the issue is on the roadmap since Aug 2019 (int ref: https://github.com/eramba/eramba_v2/issues/2305)

its on the long roadmap, at some will happen but it will take a long time

if you mean something different you will need to explain it again : )

regards!!

1 Like
3

Yes, I believe that’s exactly what I’m talking about. Thanks!

1 Like
4

We will work on this in the coming months:

This feature needs a separate “Button” of sorts to be accessed, this would be called “Module Relationship” or something like that:

image

When you open this feature, you choose what which “destination” module you wish to associate the module with. you also choose if the relationship is one-to-one or many-to-one.

For example if you are in the asset mgt/asset module you choose the “organisation/liability” module and “many-to-one” then on the liability module, when you add or edit, a field “Assets” will be shown and you can select one or more items.

Once the association setting is saved, on the “organisation/liability” module, under customisation, you will see there the “asset module” field, you can move it up, down, rename, make it mandatory, etc.

To remove the field from the “liability” module, you need to delete the relationship on the “origin” module. If that is done the data stored (association) should not be removed.

If you edit a liability, you will see the a field that will list the “assets”, you can select one or more items depending on how the relationship settings where configured.

On the liability module, filters will display the field as just another “Custom” field, where items are shown as “Items” (so you can use short cuts). This will let users visualise and query data.

Important considerations:

  • you could relate one module with itself, for example on the libaility module you relate teh liablity module … so you can relate liabilities in between them
  • not every module can be “Origin” or “Destination”. For example you can not associate “Asset / Reviews” , or “Awareness Programs / Notifications”. I think only parent items can be associated, we will need to limit by configuration which modules can act as “Origin” / “Destination”

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

1 Like
5

Questions that arise:

UI

  • Do we want to add a new button called “Relationship”? Or should it be an option within the existing custom field?

image
image2786×1222 165 KB

Module

  • Would it be possible to create more than one field related to other modules?
    • Field 1: Asset Risk → Projects
    • Field 2: Asset Risk → Projects
  • If I create a field that links to another module, should a corresponding field be automatically created on the other side? For example:
    • Asset Risk → Projects
    • Projects → Asset Risk
  • If yes, should this field be hidden by default or visible in the form/filter view?
6

Nope

This could be an optional settings, which by default for now will be disabled and can not be enabled

this is answered as well