I am trying to use the UI to set screens and metadata elements by type. I can figure out how to bind an element based on types - but how do you turn off fields and screens that are valid for some types but not others?
Example: organizations. How do I turn off forename, middle name, surname, etc for an entity type of organizations? I can bind the organization name field ad other fields but I want to turn off some fields for this type (and this type only).
As always keep up the good work.
The fields will automatically hide themselves when they are not valid for the type of the currently edited item. It is possible to restrict screens by type, but this is relatively new functionality and only supported at this time via installation profiles. The web-based user interface editor is sorely in need of an overhaul, in part to support this new functionality.
The entity label fields you mention are a special case. They are actually hardcoded into the notion of an entity "label" (aka. name). The fields in the label definition were chosen to support recording of pretty much any name in (hopefully - I'm sure someone will find an exception) any culture. They cannot be hidden like configurable metadata elements. The convention is that you only fill in surname for those entity types with only a single name (Eg. organizations). A means to hide specific label fields on a per-entity type basis has been requested and will be implemented at some point in the future. In the meantime if you follow the convention you'll be fine.
seth
Thanks.
I know others will love to use the UI to do this. It is pretty easy to use and I don't need to use putty to access the profile.
Wondering if I should be using the installation profile over the UI though . . do changes I make in the UI as an admin change the profile?
Changes you make in the UI do not automatically change your profile. The profile is a "canned" configuration, while the UI makes changes to a running configuration.
You can always export a running configuration as a profile using the exportProfile.php script in support/utils though.
You said that this is possible through the installation profile right? I'm trying to get separate UIs set up for each object type, is there a way to do that? or are you referring to the restrict_to_type command?
You can create as many UIs as you like, but you cannot currently create UIs for specific types. Any UI you create is available for all types. What you *can* do however, is to restrict screens within a UI to specific types. This is done via type restrictions for individual screen configurations.
We have not documented screen-level type restrictions because we're still not totally sure if they make sense in general, although we have used them to good effect in a couple of particularly unusual projects.
We are about to finally implement type-specific UIs, as well as push a revised web-based UI editor into SVN. All of this will be in the "clean_up_before_release" branch for a bit, and then merged into trunk after some additional testing.
If you want to see how screen-level type restrictions are done, take a look at the "TABU" profile (install/profiles/tabu.profile).
You must log in to post.
