CA Service Management

We have a situation where we have customised the detail forms for incidents and changes by restricting the search for the requester and affected user. We have done this by populating the 'additional search arguments' box (extraURL="ADDITIONAL_WHERE..." in the htmpl file).

Before making this change, the search form came up when we clicked on the search link on the detail form. After making the change, the search results come up.

Our customer would like to see the search form rather than the results. CA's opinion is that the product is working as designed. Is there any customisation we can do to change what happens?

another way is to create your own factory at the cnt object level to restrict the where and overwrite the factory in the lookup field.

<PDM_MACRO name=dtlLookup  hdr="Assignee" attr=assignee evt="onBlur=\\\"detailSyncEditForms(this)\\\""

factory=z_myFactory>

example of such factory from CA:

    FACTORY cst {
RESTRICT "type = 2305" { type = 2305} ;

        DOMSET cst_list "combo_name,phone_number,contact_num,organization,location" "" DYNAMIC;

        STANDARD_LISTS {
            SORT_BY "combo_name,phone_number,contact_num,organization=organization.name,location=location.name";
            WHERE "delete_flag = 0" ;
            MLIST OFF ;
            RLIST OFF ;
        };

        REL_ATTR id ;
        COMMON_NAME combo_name ;
        FUNCTION_GROUP "contact" ;
    } ;

Hope this help

/J

Thanks for that suggestion. In our situation we are using the additional search arguments to remove one particular contact type from the search, while allowing the possibility of blanking out the additional search arguments to include it again. However, we might be able to come up with a solution involving a dropdown which drives a choice between two factories, one including everything and one excluding that particular contact type.

Hi,

you can try to pass flag using extraURL: extraURL="KEEP.zSomeFlag=1".

And then using <PDM_IF $args.KEEP.zSomeFlag == 1> statement include your search arguments directly to the list form (example could be found in list_cnt.htmpl), as I remember this will not cause instant search and will show initial list page.

Regards,

cdtj

Yep cdtj approach is another good one

/J

The problem is that we need type ahead (auto suggest) to work and to exclude contacts with one particular contact type, and it seems that we can only do that by using an additional WHERE clause which excludes that contact type.

Mike........

Were you able to sort this out?

If so, would you mind posting the solution to this thread for the benefit of the rest of the community.