Add support to apply type restrictions on relationship bundles. (not to be confused with applying type restrictions or relationship type restrictions on the "related" item). This would be just like applying type restrictions on a metadata element, only on a relationship bundle.
This would greatly reduce screen/UI redundancy. Currently, we have to set up multiple, type-restricted "screens" in cases where the UI placement is identical with the sole exception of a relationship bundle that is broken out by type or relationship-type.
Code implementing this is in develop. The way it works is that every bundle now has type restriction settings. These are by default blank, which lets the bundle display for all types. If you set a restriction then that restriction overrides any other in the negative sense: if you set a bundle to not display for a type then it'll never display for that type no matter what other restrictions are in place.
This is working great in the UI. But for the profile syntax, is there a way we can use the object type's list item identifier rather than the internal item_id?
It looks like right now you can encode it at this:
But not this:
Added support in installer for specifying bundle-level type restriction.
Specification is placed as an attribute in the <placement> tag, as in:
<placement code="ca_attribute_description" bundleTypeRestrictions="document,video">
where "document" and "video" are two types for the record the editor is bound to
Actually "typeRestrictions" is more consistent. The syntax is now:
<placement code="ca_attribute_description" typeRestrictions="document,video">
Thanks, this is awesome!