Why the association rules are useful ?
When your teams work on an engine, you want to offer a list of forms that can be produced on this motor. To propose this list, you can either associate documents manually with the site, or create an association rule.
How to create documents / assets association rules ?
Thanks to the association rules between documents and assets, you can configure rules allowing to automatically associate documents with certain types of assets, according to document attributes and asset attributes.
Example: All the equipment whose "Family" = Boiler and "Type of energy_asset" = Gas are associated with the Documents whose asset concerned = Boiler and Type of energy_doc = Gas:
Thus, the operator, on his app, will have a 360 ° view of his fleet since he will see all of his asset and their associated documents.
Be careful : Each attribute must have a unique name, even if it does not have the same typology (Document, asset, Intervention or User). Thus, if an attribute is common between several libraries, for example Documents and assets, it is advisable to put different names.
Example : In the example above, "Energy type" is found in Documents and in Assets. We have therefore added a suffix with the typology of the attribute to dissociate them.
To go further
- Make sure that the association rules are consistent with each other so as not to have conflicts in the rules.
- For the moment, the association rules do not work when the offline mode is activated.