In webtop advance search, is that a way to limit the list of attributes in the "Properties" drop down to only show the custom attributes and some of the sysobject attributes and not all the sysobject attrinutes? Thanks in advance for any suggestion.
Try this : From Composer, go to Attributes tab under Types Artifact and select option 'All attributes including inherited from supertype'. This will show you all the attributes custom as well as OTB.
Then you can check/uncheck 'is searchable' option. This option appears under 'Application Interface Display' when you select an attribute.
Hope this would work for you.
If you're still using DAB, you can do the same thing by clicking on View, List all Attributes and then go into the attributes, click on the Advanced tab and uncheck the "Searchable" check box for the attributes you don't want to see in Advanced Search.
Nidhi,
Thanks, i did not know that. But is thre is way to do this via the configuration file on webtop. I will tell you what issue i see with making changes on the type,
So is there a way to make this change by configuring the advance search component?
Appreciate you response. Thanks again.
Elliott, thanks for the suggestion, this would also work, but see my response to Nidhi. I have noticed that any configuration setting on the type slows the performance (i guess evertime it queries the Database) as compared to component xml files, they get loaded in memory just once. I am not sure though, but i have seen the performance issue and that my assumption. let me know if you have any idea if it is achievable via modifying adv search component.
"...i have noticed that when the dipaly configuration are pulled from the type info, it makes the interface very slow. The performance impact is clearly visible. I had done display of attributes for info and it used to take a 15 to 20 seconds for the indo tab on import screen. Then i changed and moved it to the component xml and it comes up in less than a second."
- What version of Webtop are you using (including SP)? How many attributes are you displaying? I havent encountered this before. The issue with putting information in component xml is that you have to deploy new code any time you want to change the object model. Using display configuration you dont, which is this typically best practice. Also, there are many things that can impact performance. I have my doubts its because of how display configuration is designed.
webtop 6.5.sp3 without any patch...and just ot make it more clear, when i said i noticed the performance difference i did not mean that i noticed it over a long period, it was slow all the time and the momenti moved it to the component xml file it started coming in less than a second...so that started me wondering... there is another application we have which has lots of display configuration stuff, it was developed initially on 5.3 and now upgraded to 6.5, believe me you can literally take a nap before info tab comes up...
I dont side track your original question about advance search, but if you want to start another thread, I would gladly share my experience on that topic.
Thanks. I would definitely like to know, created another thread for that
(display configuration in type VS display changes via component xml),
https://community.emc.com/thread/133112
johney, can you share your thots on the other thread i created as per your request.
Dirty but functional solution:
Take a dump of your custom object to get ALL associated attributes, and remove the ones you want to keep.
Edit webcomponent\library\advancedsearch\advsearch.jsp and find the EXCLUDENAMES tag shown below and add all the UNWANTED attributes to it like this:
<dmfxs:searchattributegroup name='attributesearchcriteria' tooltipnlsid="MSG_PROPERTIES_TIP" excludetypes='time' excludenames='r_version_label,r_content_size,r_full_content_size,a_is_hidden,r_object_type,authors,keywords
,a_application_type,a_status,r_modify_date,r_modifier,r_access_date,a_is_hidden,i_is_deleted,a_retention_date,
a_archive,a_compound_architecture,a_link_resolved,i_reference_cnt,i_has_folder,i_folder_id,r_composite_id,
r_composite_label,r_component_label,r_order_no,r_link_cnt,r_link_high_cnt,r_assembled_from_id,r_frzn_assembly_cnt
,r_has_frzn_assembly,resolution_label,r_is_virtual_doc,i_contents_id,a_content_type,r_page_cnt,r_content_size,
a_full_text,a_storage_type,i_cabinet_id,owner_name,owner_permit,group_name,group_permit,world_permit
,i_antecedent_id,i_chronicle_id,i_latest_flag,r_lock_date,r_lock_machine,log_entry,r_version_label,i_branch_cnt,
i_direct_dsc,r_immutable_flag,r_frozen_flag,r_has_events,acl_domain,acl_name,a_special_app,i_is_reference,
r_creator_name,r_is_public,r_policy_id,r_resume_state,r_current_state,r_alias_set_id,a_effective_date,
a_expiration_date,a_publish_formats,a_effective_label,a_effective_flag,a_category,language_code,
a_is_template,a_controlling_app,r_full_content_size,a_extended_properties,a_is_signed,a_last_review_date,
i_retain_until,r_aspect_name,i_retainer_id,i_partition,i_is_replica,i_vstamp' casevisible='false' width="200" valuewidth="280" logicaloperatorpos="newline">
</dmfxs:searchattributegroup>
