How "Search catalog item" topic block works for virtual agent in different portal .

[chilanka1]

I have two portals(eg: - sp & cd )and for those I have created 2 different virtual agents. All those topics are separated by giving conditions and its working fine ie, topics of portal sp not  coming in cd  . however, the problem is while I am searching catalog item with keywords in the virtual agent of portal sp it is picking the catalog item that present in the portal cd.

there is a topic block " search catalog item" I believe that is making the issue. I have separated catalog items by giving different catalogs and category for items present in each portal .but still catalog items in the portal cd is coming in virtual agent of portal sp. Can anyone help me to solve this issue by giving any condition to the topic block " search catalog item" or if any other idea is there please suggest that.

Thanks in Advance.

[Joe B2]

I had the same requirement when we split some services out. You mentioned you had already split the catalog out which is good.

When selecting the Search Catalogue Item topic block there is an input variable called Catalogs which accepts sys_id(s) for the catalogue you wish to search. In my case I use a script to determine what catalogue should be searched based on the portal and then pass the correct sys_id in this input variable. This will properly limit the search results.

[chilanka1]

Hi Joe ,

I am taking a moment to thanks for the reply. I believe it's a great approach. Actually, I believe you mean "Search fallback topic live" is using the topic block "Search Catalog item " and it takes input "catalog". I edited that input by directly giving "sys id" of the portal.

var portalId = '7c9603791bfae15094aafc09dc4bcbce'; I gave "sys id " directly and 

var suffix = vaVars.portalName;  In this step portalName was calling property from" sys_properties" table I set the property value as my portal suffix and tried still I am getting another portal catalog item. I am not getting where I am wrong. If you have the script, please share or guide me with more details.

(function execute() {

function getCatalogM2M(portalId){

var gr = new GlideRecord('m2m_sp_portal_catalog');

if (gr.isValid()) {

gr.addActiveQuery();

gr.addQuery('sp_portal', portalId);

gr.addQuery('sc_catalog.active', true);

gr.orderBy('order');

gr.orderBy('sc_catalog.active');

}

else {

gr = new GlideRecord('sp_portal');

gr.addQuery('sys_id', portalId);

}

gr.setWorkflow(false)

gr.query();

return gr;

}

var suffix = vaVars.portalName;

if (suffix) {

var catalogs = "";

var gr = new GlideRecord('sp_portal');

gr.addQuery('url_suffix', suffix);

gr.setWorkflow(false)

gr.query();

gr.next();

var portalId = '7c9603791bfae15094aafc09dc4bcbce';

vaVars.portalId = portalId;

var m2mGR = getCatalogM2M(portalId);

if (m2mGR.getRowCount() > 0) {

m2mGR.next();

catalogs += m2mGR.getValue('sc_catalog');

while(m2mGR.next()){

catalogs += ',';

catalogs += m2mGR.getValue('sc_catalog')

}

}

return catalogs;

}

return '';

})()

[Joe B2]

Sorry, I'm not quite sure I understand. The topic block you were looking at was called Search Catalog Item I thought?

This accepts several parameters and the one you need for this is Catalogs (String). You would put the catalog(s) (separated by comma) of any catalogs you wish to search.

In my use case we only have the 2 catalogs, one per portal, so I just hard coded them into the function dependent on the current portal.