Part 2 : Extensibility of IBM Content Navigator framework with plugins that suit your needs ...

Reason for this post ?? .. Well a client had a nagging UX with ICN search feature, and was looking for a solution.

Each of the 4-5 sub classes of a parent class had a unique choice list field. When a search is performed on the parent class (including the sub classes), the client had to add 4-5 columns in the Results Display to be able to view the choice list metadata of each subclass.
This wasn't an ideal UX, a better solution was to show all those unique choice list values from the various sub classes into one column, with a custom column header to indicate that they are from the choice list of the sub classes.

Below picture is probably worthier than the above 503 characters :D

Without Custom ICN Plugin

With all that being said, I obviously got it working else this blog would have been a moot point ;) .

Design:
1. Implement a ICN Response filter for "/p8/search"
2. Check if results display has more than one Sub type
3. Create a new column with a custom header (For eg: PlantSubType)
4. Loop through the search results, gather the choice list value from the subclass, and put it into the
       new column created (PlantSubType)
5. Remove the now redundant choice list metadata from the sub classes.

With Custom ICN Plugin

Key thing here is to understand the data being exchanged between client and server and figure out a way to manipulate it.

Snippets of JSON with and without the custom ICN plugin:

Introduce new Column

Copy data over into New Column

Code Snippet:

...  
...
JSONArray magazineColumnsArray = (JSONArray) jsonResponse.get("magazineColumns");
JSONObject magazineColumns = (JSONObject) magazineColumnsArray.get(1);
...
JSONArray listOfCells = (JSONArray) cellsArray.get(0);
JSONObject newCell = new JSONObject();
newCell.put("field", "PlantSubType");
newCell.put("name", "Plant Sub Type");
...
JSONArray tempAttribute;
for (int i = 0; i < rowsArray.size(); i++) {
...
   tempAttribute = (JSONArray) currRowAttributes.get("DesignType");
   currRowAttributes.put("PlantSubType", tempAttribute);
...
}

P.S:  "BUT", well there is always a "but" isn't it, the client didn't get to have this awesome piece of code, since we were out by then ... how about this for a sales pitch ;) ..

Accessing Case Information from within ICM Case Manager Widget Code

Requirement:

                ICM Case Manager widget developers often find the need to access Solution and/or Case information and its artifacts, to be able to make decisions and act upon them.

Solution:

               The solution involves accessing the cache object of the workItem object which gets passed onto a widget. From the cache object we can extract various artifacts like case ID, case name, Solution prefix, case properties and so on …

Sample Code:

// summary:
// Handler for receiving the event icm.SendWorkItem.
// payload: The received payload.
handleICM_SendWorkItemEvent: function(payload){
 if(!payload){
  console.log(" payload not received, returning");
  return;
 }
 console.log("Entering handleICM_SendWorkItemEvent ");
 
 // Defining a callback function 
 var callback = function(workitem) {

 var caseObject = workitem.getCase();
 if (caseObject != null) {
  caseObject.retrieveAttributes(lang.hitch(this, function(caseObj) {
  // get Case ID from case object
  var caseId = caseObj.caseIdentifier; 
      
  /* get CaseType object from case Editable. 
     This caseTypeObject has information about the 
     specific case type (and its artifacts) within a solution
  */
  var caseEditable = caseObj.createEditable()
  var caseTypeObject = caseEditable.getCaseType(); 
      
  // get Case Type name from caseTypeObject
  var caseType = caseTypeObject.name;
      
  // get solution prefix from caseTypeObject
  var prefix = caseTypeObject.solution.prefix;
      
  /* get Case properties using provider, symbolicName.Here provider 
     is F_CaseFolder which is the location where all 
     Case properties are saved.
  */
  var customerId=caseEditable.getProperty("F_CaseFolder",
      prefix+"_CustomerID").value;
     
  this.randomMethod(caseEditable, caseType, prefix, customerId);
  }));
 }
 };
 
 if (payload.workItemEditable) {
   payload.workItemEditable.
  retrieveCachedAttributes(lang.hitch(this, callback));
 }

}

Widgets can handle events like receiving case information, workitem and so on.
The above example code shows the method which handles one such event (SendWorkItemEvent). Callback and dojo functions are used to get the necessary information. Code has inline comments explaining things in detail.