So, you’ve added some nifty new attributes to a new or existing object in the ILM Service Database and now you’re trying to add the attribute as part of a filter in perhaps a Dynamic Set definition, you hit submit and you get an Access Denied?
You can find out more information as to why this failed by checking Search Requests and opening up the failed request.
Notice the Filter validation failed for request message. Clicking the Applied Policy tab shows us which policies affected the operation:
If you click the hyperlink for Modify Filter Subject to Administrator Filter Scope you can follow the object all the way to the Workflow responsible for this behavior – Filter Validation Workflow for Administrators. You’ll notice there is an admin and a non-admin filter, and opening the admin version allows us to take a peak at what the filter is doing:
Hopefully the virtual light bulb has gone off now – when you extend the schema you will probably need to add the new attributes to various Filter Scopes so that they can be used in filters, otherwise you will get the Access Denied error.
0 comments:
Post a Comment