Pinned topic EDS not working properly for populating Search Template
I have a problem concerning the EDS plugin.
I am running ICN 2.0.1 towards IBM Content Manager 8.4.03.110.
I need to set up EDS to populate two drop-down menus, the value of the second one depending on the value of the first one, in the forms that appear to "Add Document", "Edit Properties" or "Search".
The EDS plugin works fine as far as the "Add Document" and "Edit Properties" forms are concerned, but it seems to not work for the "Search" form.
The drop-downs get correctly populated the first time the search template is opened, but as soon as I change a value in the father drop-down, the form changes slightly (I'll show how in the attached files), and the "child" field does not get populated.
I have tried analyzing the problem a bit, and found out that the JSON passed to the plugin the first time the search template is opened has a different structure from the JSON that is passed upon changing a value in the "father" drop-down.
The attached ZIP file contains:
ARCHCOM_PropertyData.json: The JSON file the EDS servlets use to respond to the plugins requests, with dependencies between attributes correctly defined
addDocumentFormWithOKChildDD.JPG: Sample image of the "Add Document" form, with child drop-down correctly populated based on parent drop-down
searchTemplateFirstOpening.JPG: The search template's appearance upon first opening it
searchTemplateFirstOpenJSONStructure.JPG: The JSON object received by the plugin upon first opening the search template
searchTemplateAfterChangingDDValue.JPG: The search template's appearance after modifying a value in the parent drop-down (notice for example the disappearance of the full-text search bar...)
searchTemplateAfterChangingDDValueJSONStructure.JPG: The JSON object received by the plugin upon changing a value in the father drop-down. As you can see it seems totally unrelated to the search template (it has all "criterias", rather than just the three in the template, doesn't have the full-text search part, etc...)
The fact that the search template changes in aspect makes me think that there is a problem with what the action mapped at "/cm/getDependentAttributeInfo" passes down to the plugin, which, in the case of an attribute with dependencies changed within a search template, should be more similar to what is passed by the action mapped at "/cm/openSearchTemplate".
Re: EDS not working properly for populating Search Template2013-03-27T15:25:19Z in response to SystemAdminHI Alessandro,
The EDS service does have some limitations with dependent properties on the search form. I do not remember the details specifically, but I do know that it does not work quite as well as the edit / add document paths. I'll try to get someone from my team to post a bit more information. We're looking in to some design tweaks to address the issues but when we'd make the changes is something we're still determining.
Not the answer you're looking for I know, but I didn't want you to bang your head against this problem any longer than needed.
Re: EDS not working properly for populating Search Template2013-03-27T22:34:14Z in response to SystemAdminSearch does not support dependent properties. This is a limitation and is mainly related to how search criteria are used by the search form. It wouldn't make sense to enforce dependent properties in many cases as it would unnecessarily restrict what could be searched for. For example, if the criteria are or'ed together, it would be perfectly okay to search for a particular state OR a particular city, even when the city is not within the state. It might be enforcable for certain limited situations, such as and'ed criteria using only equals as operators, but ICN currently has no logic to enforce dependent properties on search in any situation.
Re: EDS not working properly for populating Search Template2013-04-03T12:21:21Z in response to SystemAdminThank you Dana, and Brian.
The fact that criteria should be kept independent in OR searches definitely makes sense, and introducing the dependency for AND searches only would probably not be worthy of the effort...
However, there is still some sort of problem with EDS populated fields and the search templates, because any change in a drop-down value populated by EDS (even with the "hasDependentAttributes" set to "false") causes the full-text search field to disappear, as shown in the screenshots in my opening post.
Re: EDS not working properly for populating Search Template2013-04-03T16:54:19Z in response to SystemAdminHi Alessandro,
This might be a defect that we fixed in the fix pack ( I can't remember). Can you re-test with Fixpack 1 applied? We just released the fixpack yesterday.
Fix Central Location: http://www.ibm.com/support/fixcentral
Fix Central Download Instructions:
Select Enterprise Content Management in the Product Group field.
Select Content Navigator from the next list. in the Product field.
Select 2.0.1 in the Installed Version field.
Select appropriate Platform.
Alessandro.Damiani 0600020W3D58 PostsACCEPTED ANSWER
Re: EDS not working properly for populating Search Template2013-04-16T15:34:11Z in response to damorris
Thank you Dana,
I haven't had a chance to install and try the fix against this particular issue, but I will try asap and post here if the fix pack solves the issue.
DushyanthReddy 270006BWB511 PostsACCEPTED ANSWER
Re: EDS not working properly for populating Search Template2013-05-27T13:40:08Z in response to damorris
Even after installing fix pack for ICN(2.0.1) version ,dependant choice list is not working in search template.
Thanks & Regards,
Dushyanth Reddy B.
Re: EDS not working properly for populating Search Template2013-05-28T11:17:49Z in response to DushyanthReddy
As described above, dependent properties are not supported with search templates. The fix I mentioned to Alessandro has to do with the full text search field disappearing.