Disabling Adaptive Learning in the Knowledge Management Environment Record does not prevent adaptive learning records from being created in the kmadaptive learning table. This problem only occurs when using Smart Search/Smart Analytics and IDOL for Knowledge Management. The problem does not occur when using the SOLR Search Engine.

There is a defect within the IDOLAssistantUseSolution ScriptLibrary record.

The following steps below will disable Adaptive Learning for Smart Search:

1. Login to Service Manager

2. Go to System Administration > Ongoing Maintenance > Environment Records > Knowledge Managment Environment Record

3. Uncheck (i.e. set to false) Use Adaptive Learning to Enhance Search Results

4. Save

5. Logout then back into Service Manager

6. Go to Database Manager and access the ScriptLibrary table

7. Inside ScriptLibrary access the following script: IDOLAssistantUseSolution

8. Find this section of code:

function useSolution(record, solution, library, reference, keyword) {
var mapping = funcs.filename(record);
logger.debug(‘applying solution ‘ + solution + ‘ onto ‘ + record);

KMSearch.useSolution(mapping, solution, record);

var database = library.kbname;
// XXX: reference has to encode twice …
reference = encodeURIComponent(reference);
updateRanking(database, reference);
IDOLGlobalSearchAdaptiveLearning.appendPhrase(library, solution, keyword);
return record;
}

9. Comment the following line: IDOLGlobalSearchAdaptiveLearning.appendPhrase(library, solution, keyword);

10. The function should now look like this:

function useSolution(record, solution, library, reference, keyword) {
var mapping = funcs.filename(record);
logger.debug(‘applying solution ‘ + solution + ‘ onto ‘ + record);

KMSearch.useSolution(mapping, solution, record);

var database = library.kbname;
// XXX: reference has to encode twice …
reference = encodeURIComponent(reference);
updateRanking(database, reference);
// IDOLGlobalSearchAdaptiveLearning.appendPhrase(library, solution, keyword);
return record;
}

11. Save, Compile

12. Adaptive Learning is now disabled for Smart Search

1. Copy the unload file (eg unload_file.unl) into the <SM INST>\RUN directory

2. Open the terminal and navigate to Go to the <SM INST>\RUN directory

3. Execute the command:

For Microsoft Windows: sm -bg file.load <unload_file.unl> NULL NULL winnt

For UNIX: sm -bg file.load <unload_file.unl> NULL NULL unix

Where <unload_file.unl> is the name of the file to be loaded

4. A message will indicate the load succeeded.

1. In SurveyParameterMapping, there is not predefined mappingValue for Mob

So add one in global list (List Name: SurveyPredefinedParameters) {“{$EMAIL}”,”{$NAME}”,”{$LANGUAGE}”,”{$WEBURL}”,”{$ESSURL}”,”{$EXURL}”,”{$EXTSID}”,”{$SURVEYURL}”,”{$MOBURL}”}

{“Recipient Email”,”Recipient Name”,”Language”,”Web URL”,”ESS URL”,”External URL”,”External Survey ID”,”InternalSurvey URL”,”MOB URL”}

2. Then add Mob URL for Interaction module for the particular Connector ID. In this example adding the parameters for Internal Connector.

Add mobURL in Survey Connector (for interaction parameters) as highlighted in below snapshot.

3. ScriptLibrary: Survey_TaskProducer, add below line at Line: 117:

paramMap[“$MOBURL”] = url.mob;

4. ScriptLibrary: Survey_Utilities. Add below lines:

Line 134: var url = {“web”:””, “ess”:””, “mob”:””};

Line 172: url.mob = lib.urlCreator.getMobilityURLFromQuery(record_id);

5. System Information Definition:

Add a testing value for “mobility.url” field:

http://mob-url.google.com

6. Schedule the Survey Interation record: S00003

7. Enable the SMSurvey in SMIS:

8. Make sure the Repeat Interval of Survey_Service_Agent within a few minutes:

9. Make sure the Repeat Interval of SMSurvey1 within a few minutes:

10. Now close any one of interaction record:

11. Check the record generated in eventout table:

Now we can see that the mobility.url has been displayed in the email message.

In Forms Designer there is a Property named “Output Conversion”. When used it can change the display of data in the GUI (i.e. display just the date of a record instead of the full date/time). However, the parameter will not extend to exporting the data of the Service Manager record to Excel or Text.

This property is used by RAD subroutines that mask the display of data on an output field, or check and validate the entry of data into an input field. If specified, the routine is called at runtime to convert the contents of the field before it is displayed on the screen. This only works within the client and does not extend to the export of data feature.

Note that at the time of this writing Enhancement Request QCCR1E137853 exists within Development to look into extending the capabilities of this Property to the Export To Text/Excel feature