Technical

Components

Components used:

lwc-limepkg-auto-attach-picker-card

lwc-limepkg-auto-attach-picker-confirmation-dialog

Limitations

Triggers Only for Manual Updates

The code will not trigger changes for other cards if it is mapped to multiple components. This means that if you configure two Auto Attach Pickers for both "person" and "deal" on a card, updating the "deal" field from the "person" field will not trigger the "deal"-component event. It only triggers when the field is manually updated in the web client.

Options Must Match for Updating Option Fields

Option fields must match if you are updating one option field from another. For example, if you're updating a priority based on a category's priority, and the category has options like prio1, 2, 3, 4, 5, then the current object's priority must have the same option keys. There is no support for mapping different options. When clearing values, the default option will be selected.

Configuration Applies Only to the Field Where the Component Is

If you want different behavior for different objects that inherit the component (e.g., if you configure inheritance from "lease" to "object" and "area"), there is no support for configuring different behavior when clearing "object" and "area." However, if you have multiple components, you can configure different behavior for the same card.

Not every component is tested, but the behavior is not hard-coded for anything except hierarchy-picker

When picking other components, they should be supported, but as they are inherited from what you have in your customer solution, not everything is tested. You could add other custom web-components and configure them how you want and use this component on top of it.