manalang

Latest Updates: peoplecode RSS

• 

  manalang 05:52:00 pm on February 1, 2006 | Comments | # |
  Tags: ajax, monkeygrease, oracle, peoplecode, peoplesoft, peopletools, programming

  In the past week I’ve been playing around with PeopleSoft’s built-in search engine (Verity) to come up with a better search experience for users. Riding on the wave of Google Suggest a lot of people have implemented a “live” search feature on their sites. So, I decided to sprinkle a little AJAX on top of PeopleSoft and build the same feature for Enterprise 8.4 and above. Check it out…

  The most unbelievable thing about how I implemented live search on PeopleSoft is that I didn’t customize any delivered code. None. This was possible because of Monkeygrease. Monkeygrease allows me to “inject” JavaScript/CSS/HTML into a page before it’s delivered to the browser. On the back end, I created a simple PeopleSoft iScript to carry out the search and return the results in a <ul> tag… I thought about using JSON, but then that would have added more complexity to the JavaScript.

  Here’s the iScript:

  [WEBLIB_CSS_LSCR.ISCRIPT1.FieldFormula]
  Function FormatPath(&Path As string) Returns string
     Local number &i, &begin, &end;
     Local string &stringToSearch, &stringToCut;
     &stringToSearch = &Path;
     &begin = Find("{", &stringToSearch);
     While &begin > 0
        &end = Find("}", &stringToSearch);
        &stringToCut = Substring(&stringToSearch, &begin, &end - &begin + 1);
        &stringToSearch = Substitute(&stringToSearch, &stringToCut, "");
        &begin = Find("{", &stringToSearch);
        If &i = 1000 Then /* Safety break */
           Break;
        Else
           &i = &i + 1;
        End-If;
     End-While;
     Return Substitute(&stringToSearch, ".", " > ");
  End-Function;
  
  Function IScript_doSearch()
     Local string &q, &node, &partialUrl, &fullUrl, &resultsHtml;
     Local number &resCounter;
     Local ApiObject &portal, &query, &results, &result, &cref;
     Local Request &Request = %Request;
     Local Response &Response = %Response;
  
     REM If no query text avail, return nothing;
     &q = &Request.GetParameter("q");
     If &q = "" Then
        Return;
     End-If;
  
     &portal = %Session.GetPortalRegistry();
     &portal.Open(%Portal);
     &query = &portal.GetSearchQuery();
     &query.Language = %Language;
     &query.QueryText = &q | "*";
     &query.RequestedFields = "CONTENT_PROVIDER,URL,SCORE";
     &query.SortSpecifications = "SCORE desc";
     &results = &query.Execute(1, 20);
  
     If &results  Null Then
        &result = &results.First();
     Else
        &result = Null;
     End-If;
  
     &resCounter = 1;
     While &result  Null
        &node = &result.SearchFields.ItemByName("CONTENT_PROVIDER").Value;
        &partialUrl = &result.SearchFields.ItemByName("URL").Value;
        &fullUrl = &portal.GetAbsoluteContentURL(&node, &partialUrl);
        &cref = &portal.FindCrefByURL(&fullUrl);
        If &cref  Null Then
           If &cref.Authorized And
                 &cref.isVisible And
                 (&cref.URLType = "UPGE" Or
                    &cref.URLType = "UEXT" Or
                    &cref.URLType = "USCR" Or
                    &cref.URLType = "UGEN") Then
              &resultsHtml = &resultsHtml | GetHTMLText(HTML.CSS_LIVE_SEARCH_RESULT, &cref.Label, &cref.AbsolutePortalURL, FormatPath(&cref.Path), &cref.Description);
              If &resCounter = 8 Then
                 Break;
              End-If;
              &resCounter = &resCounter + 1;
           End-If;
        End-If;
        &result = &results.Next();
     End-While;
     &portal.close();
  
     If &resultsHtml  "" Then
        &Response.Write(GetHTMLText(HTML.CSS_LIVE_SEARCH, &resultsHtml));
     End-If;
  End-Function;

  There are two functions in this iScript, FormatPath and IScript_doSearch. FormatPath just formats the path location of the search result item (where it’s stored in the portal registry). The IScript_doSearch is what calls the Verity API to carry out the search. In this function, I filter each result through the portal registry to see if the user has access to the item. This iScript performs amazingly well.

  The iScript above references some HTML objects… here they are:

  [HTML Object: CSS_LIVE_SEARCH]
  <ul>
  %bind(:1)
  </ul>

  [HTML Object: CSS_LIVE_SEARCH_RESULT]
  <li>
  <a href="%bind(:2)" title="%bind(:4)" target="_top">%Bind(:1)</a>
  <div>%bind(:3)</div>
  </li>

  The the only other things I needed to do was code up the JavaScript and CSS to insert into the page. You can view those here: live-search.js and live-search.css. I then “injected” these files via this Monkeygrease rule:

  <rule enabled="true" name="Live Search" url-pattern="(/psp/?([^/]*)?/?([^/]*)?/?([^/]*)?/(h/|s/WEBLIB_EO_PE_LN\.ISCRIPT1\.FieldFormula\.IScript_EPPLN_INFRAME)|/psc/?([^/]*)?/?([^/]*)?/?([^/]*)?/s/WEBLIB_PT_NAV\.ISCRIPT1\.FieldFormula\.IScript_PT_NAV_INFRAME_TITLE).*" insert-at="head-end">
      <![CDATA[
      <script type="text/javascript" src="http://some.server.com/monkeygrease/lib/prototype.js"></script>
      <link rel="stylesheet" href="http://some.server.com/monkeygrease/live-search.css" type="text/css" media="screen" />
      <script type="text/javascript" language="javascript" src="http://some.server.com/monkeygrease/live-search.js"></script>
      ]]>
  </rule>

  As you can see from these Monkeygrease rules, the prototype.js library is required. I used this library to simplify the code… and it did just that.

   

• manalang 06:27:11 pm on September 9, 2005 | Comments | # |
  Tags: java, oracle, peoplecode, peoplesoft, peopletools

  I’ve been working on some new tricks for my session at Oracle Open World. A lot of the things I’ve come up with incorporate Web 2.0 buzz word compliant features into the PeopleSoft Portal… stuff like Ajax/DHTML rich client type of features. I’ve also been trying to come up with simple, no-fuss, high-value customizations that our customers can easily implement on their own. One of them is adding Markdown text filtering to the PeopleSoft Portal.

  Markdown is a…

  “…text-to-HTML conversion tool for web writers. Markdown allows you to write using an easy-to-read, easy-to-write plain text format, then convert it to structurally valid XHTML (or HTML).”

  With Markdown, we can write this:

  * Bullet 1
  * Bullet 2
  * Bullet 3

  to get this:

  <ul>
  	<li>Bullet 1</li>
  	<li>Bullet 2</li>
  	<li>Bullet 3</li>
  </ul>
  

  This is one of the many things you can do with Markdown. For more examples, visit the Markdown Syntax page.

  Markdown is nothing new and has actually been around for since 2003. It was created by the “Mac Pundit” Jon Gruber. I classify Markdown (and other text filtering tools like it… i.e., Textile) as a middle-of-the-road solution between editing HTML by hand and using a WYSIWYG editor. Markdown makes it easy to generate HTML by writting plain-text documents with an intuitively simple text formatting syntax.

  So what value does this bring to your PeopleSoft application? Well, in the case of the PeopleSoft Portal, you can have editors edit content without having to know HTML. Earlier releases of the portal did not include a WYSIWYG HTML editor like version 8.9 does, so Markdown is a good alternative for your content authors/editors.

  Let’s look at an example

  Before we start, to allow for simple and easy integration of Markdown within PeopleSoft, we should use the MarkdownJ library. MarkdownJ is a Java port of Markdown. PeopleSoft can natively call Java within PeopleCode and so utilizing MarkdownJ makes our life a lot easier. To use MarkdownJ, you’ll need the MarkdownJ jar file and Apache Ant. After you’ve downloaded Apache Ant, extract the contents then look for the ant.jar file under the lib directory. Copy both the markdown.jar and ant.jar to your PS_HOME/class directory on your PeopleSoft appserver. You’ll need to cycle your appserver in order to load them into the JVM’s memory.

  Once you have the libraries placed on the appserver, all it takes to call MarkdownJ from within PeopleCode is this:

  Local JavaObject &markdown = CreateJavaObject("com.petebevin.markdown.MarkdownProcessor");
  Local string &transformedText = &markdown.markdown(&someText);
  

  You can take this little bit of code and apply it to any text based process you want. In our example, however, we’ll look at applying Markdown to Pagelet Wizard.

  Pagelet Wizard is PeopleSoft’s tool for creating pagelets (or the more widely used term, portlets). It’s a simple three step process:

  # Acquire data (Data Types/Sources)
  # Transform data (Data Transformations)
  # Publish pagelet/portlet

  Pagelet Wizard comes with several data types/sources out of the box. One of these is called the HTML data type. With this data type, a user can create a portlet by simply writting HTML within Pagelet Wizard then publishing the contents to a portlet. We’re going to clone the HTML data type as a “Text” data type. To do this, go to

  Portal Administration > Pagelets > Pagelet Wizard > Define Data Types > Add

  Define your Data Type according to the graphic below:

  

  One thing you won’t be able to specify in the picture above is the CSS_MARKDOWN display format. We’ll have to come back to that later. Data Types define the source of the data you want to acquire for your portlet. When you create a new Tata Type, you’ll need to specify the PeopleCode application class you want to use that will source the data. In this case, our data type is similar to the HTML data type in that we’re sourcing the data directly from user input within Pagelet Wizard in the form of a text area. So, we’re going to just refer to the app class for the HTML data source.

  Next, we need to define a Transform Type. Navigate to:

  Portal Administration > Pagelets > Pagelet Wizard > Define Transform Types > Add

  Again, create a new Transformation Type with the following properties:

  

  A Transformation Type defines a transformation processor. In this case, our transformation processor is MarkdownJ. A Transformation Type requires an app class that will take your Data Type output and convert it to the format you want. In this case, we will have to roll up our sleeves and write a little PeopleCode. For your convenience, here’s a project you can import into your database. And just for reference, here’s what the code in the app class looks like (I cloned the PTPPB_PAGELET:Transformer:PassthroughTransformer class to build the Markdown transformer):

  import PTPPB_PAGELET:UTILITY:*;
  import PTPPB_PAGELET:Transformer:*;
  import PTPPB_PAGELET:*;
  
  /**
    * Transformer that performs a Markdown transform.
    */
  class MarkdownTransformer extends PTPPB_PAGELET:Transformer:Transformer
     method MarkdownTransformer(&ID_param As string);
     method execute(&pageletID As string) Returns string;
     method Clone() Returns PTPPB_PAGELET:Transformer:Transformer;
  end-class;
  
  /**
    * Constructor.
    *
    * @param id_param ID of this object.  Should be unique.
    */
  method MarkdownTransformer
     /+ &ID_param as String +/
     %Super = create PTPPB_PAGELET:Transformer:Transformer(&ID_param);
  end-method;
  
  /**
    * Calls MarkdownJ to process Markdown filtering
    *
    * @param pageletID ID of the pagelet being executed.
    */
  method execute
     /+ &pageletID as String +/
     /+ Returns String +/
     /+ Extends/implements PTPPB_PAGELET:Transformer:Transformer.execute +/
     Local JavaObject &markdown = CreateJavaObject("com.petebevin.markdown.MarkdownProcessor");
     Local string &transformedText = &markdown.markdown(%This.DataToTransform.Value);
     Return &transformedText;
  end-method;
  
  /**
    * Make an exact copy of this object.
    *
    * @return Text Exact copy of this object
    */
  method Clone
     /+ Returns PTPPB_PAGELET:Transformer:Transformer +/
     /+ Extends/implements PTPPB_PAGELET:Transformer:Transformer.Clone +/
     Return create PTPPB_PAGELET:Transformer:PassthroughTransformer(%This.ID);
  end-method;
  

  Lastly, you’ll need to define a new Display Format. Navigate to:

  Portal Administration > Pagelets > Pagelet Wizard > Define Display Formats > Add

  

  A Display Format is a subclass of a Transformation Type. For example, an XSL Transformation Type can have a number of Display Types. A few delivered Display Types for XSL are chart, list, table, etc. In our case, we will only have one Display Type with Markdown.

  Once you’ve define the Transformation Type and the Display Format, go back into your Markup Data Type page and add the Markup Display Format. The list of Display Formats in the Data Type page allows you to apply other Display Format/Transformation Types to a data source.

  Once you’ve done all of that, you can now create a new text based pagelet by selecting the “Text” Data Type. When you get to step 4, select Markdown. At step 5 you’ll see your text after the Markdown transformation is applied.