
Fields of type code (list) & indicator are supported.
Yes, from 1702 release of the product.
It works only in RUI & html5. In Silverlight only configuration can be done.
Code list restriction should be created without a Business role.
It will work, but it is not a valid test case and such configuration should not be done.
Code list restriction works only in Advance Search, Quick Create screen and in the TI (eg: header).
CLR does not work on “Contacts” advanced search screen.
Yes, CLR works on advanced search.
Yes CLR can be created for custom created extension fields. Note: the field type should be either list/indicator.
No, currently custom BO’s are not supported.
No, this is currently standard limitation.
CLR supports simple data model and not complex data model and normally the facets will be complex data model and hence code list will not be applied.
“Qualification” field as a control field does not work. It’s currently a limitation.
Yes CLR works in mobile device.
Yes CLR works in offline mode.
The most specific CLR will take the priority, means if a CLR will be created with two fields BO and Code to restrict and another CLR with three fields (control field added), then later will get more priority.
Then the values which are common (or intersection) in both configuration will be visible.
In quick create and add row (list modification). It won’t work in TI and advance search OWL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |