siebel

by Jan Peterson In recent years and months the term "Customer Experience (CX)" has slowly but gradually started to replace the term "Customer Relationship Management (CRM)". A good starting point to understand CX is the Wikipedia article on  Customer Experience . The article uses a widely accepted definition and states that "Customer experience ( CX ) is the sum of all experiences a customer has with a supplier of goods and/or services , over the duration of their relationship with that supplier." As there are literally hundreds and thousands of articles, blogs and pieces of collateral around CX - just like the official Oracle CX blog  for example - I will focus on highlighting some of the concepts and ideas. Why should companies focus on CX? The core value proposition is simple: Based on the assumption that we live in a commoditised world, the key differentiator for companies is the experience they provide to their customers. It is hard to come up ...

By Jan Peterson During a presentation to the technical team of a customer who is in the progress of updating to Open UI, I showed how easy it is to make all applets collapsible by just adding some code to a postload event handler. We have looked at the general concepts in an earlier post : postload.js I quickly received a follow up question if it is possible to collapse applets automatically in case the applet doesn't have any records. As often in the new world of Open UI, the solution is very easy. Replacing oAppletPModel.SetProperty("defaultAppletDisplayMode", collapsed"); with oAppletPModel.SetProperty("defaultAppletDisplayMode", oAppletPModel.Get("GetNumRows") > 0) ? "expanded" : "collapsed"); does the job :-). A few notes: In the example I updated postload.js. For a production environment it is recommended to have a custom file that subscribes to the postload event ..   The postload event is only triggered if a user nav...

by Jan Peterson In a previous post we already looked at physical renderers for views . Today we look at an example that was in a similar form part of the first pre-beta demos of Open UI (yes - the version that was shown during OOW 2011 :-) ) - a toolbar of buttons where each button represents an applet. In our example, clicking the button will collapse all other applets (which is slightly different to the OOW 2011 demo where the corresponding applet was floating to the top): Click to enlarge The code structure of the PM is essentially the same as in the previous example: Click to enlarge Most of the logic resides in SetRenderer : Click to enlarge First, we create two buttons - one for collapsing all applets and one for expanding all applets. Afterwards, we iterate through all applets and make sure that they are collapsible - a trick we looked at in a previous post . Afterwards we create a button for each applet. The button-text is the label of the applet. As a small gimmick we add the ...

Thanks to Jan again for this guest article *** In prior releases of Open UI most configurations were limited to a single applet. Presentation Models (PMs) and Physical Renderers (PRs) could be reused for different applets but - apart from CSS changes - there was no documented way to provide changes outside of applets or enable configuration that spawned more than a single applet. Most of the time such changes ended up in the (undocumented) postload.js. A feature that didn't make it into the first release of IP2013 but ended up in the first patchset are PMs and PRs for views  (I am pretty sure that I saw this documented in the release notes of patchset 1 - unfortunately I am unable to find the note - please drop me a note with the link if you have the URL at hand). In case you are unfamiliar with the new concepts of patchsets have a look at Latest recommended maintenance pack for Siebel Open UI on Siebel Version 8.1.1.x and Version 8.2.2.x [Document 1535281.1]   which sta...

by fellow author Jan: In a previous post we looked at how applets can be made collapsible by using the Default Applet Display Mode applet user property in Siebel Tools. In the following we look how we can use the same feature in a custom physical renderer (PR) without the need to change the repository (or SRF). How  ClientPMUserProp works Let's investigate what happens when we add a value to the ClientPMUserProp applet user property: First, Siebel passes all values that are in the list of the values of ClientPMUserProp to the client. Next, the values are encapsulated in a property set of type apm which is read in the the  Setup  method of the Open UI proxy file pmodel.js and put into properties of the PM. As we can see the value of the user property Default Applet Display Mode is stored in the PM property defaultAppletDisplayMode. Click to enlarge The PM property defaultAppletDisplayMode is read in the method ShowCollapseExpand of the Open UI proxy file phyrenderer....