I have a chassis with LAN ports and WAN ports. By selecting a LAN port, the WAN port resource list must be filtered so that only WAN ports belonging to the same chassis are available.
To achieve this my WAN port resources have a resource capability Chassis ID. With DTR the Chassis ID value will be transferred from the LAN port to the WAN port so that the WAN port resources gets filtered.
My question is where I need to store the Chassis ID value on my LAN port resource? Do I need to add it as a capability - even when it won't be used as capability for the LAN port resources - so that a user sees that both resource types are familiar? Do I need to add it as a property? Will one method perform less well than the other?
Hi Jens,
Since in your use case, the value you wish to store doesn't describe a capability of your resource (and as such will not have a direct impact when the system needs to validate if you can book this specific resource) I believe the value should be saved in a property.