Feature - Custom Field types to link to other records

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

2 Likes