Siebel Open UI: Format All the Lists - Part 1

In an attempt for a real-life scenario of customizing the appearance of all list applets in a Siebel Open UI enabled application, I would like to introduce you to a coding experiment for conditional formatting of list columns.

As usual, let's see what we want to achieve:

Click to enlarge.

As you can see from the above screenshot, the Opportunity List Applet has two columns - Revenue and Probability % - which are conditionally formatted depending on their value. End users are able to use CTRL+click on the column header to display a prompt where they can enter a target value to influence the background color of the cells.

This solution should be applicable to all list applets. In this and the following post, I will lay out the steps to achieve a generic solution for the requirement presented above. The example solution focuses on numeric columns but can be easily applied to other data types as well.

The following are the main ingredients:

• Applet User Properties
• Custom Presentation Model
• Custom Physical Renderer

Today, we'll focus on the first two points:

Using Custom Applet User Properties in Siebel Open UI

As a frequent reader of this blog, you are aware of the ClientPMUserProp applet user property introduced with Innovation Pack 2013. This user property is used by Oracle to define standard applet behavior such as drag and drop to and from list applets or collapsible/expandable headers.

We can also define our own custom user properties and - as they will be forwarded to the Open UI framework - can use them in the browser-side code to control the behavior of our customizations.

To implement the conditional formatting example, I chose to define two custom user properties:

• CF Field List: A comma separated list of business component fields which - should they be exposed as list columns - will be conditionally formatted.
• CF Threshold List: A comma separated list of numeric values which defines the default target values for the respective fields.

To add these user properties to an applet, we have to edit the applet in Siebel Tools and do the following:

1. Open the list of Applet User Properties for the applet.
2. Create three new user property records as follows:

Name	Value
ClientPMUserProp	CF Field List, CF Threshold List
CF Field List	Primary Revenue Amount,Primary Revenue Win Probability
CF Threshold List	500000,50

The above settings apply to any list applet using the Opportunity business component, for example the Opportunity List Applet.

Here is a screenshot documenting the work:

Click to enlarge.

We have to consider that when the ClientPMUserProp user property is already defined for an applet, we must add our new user properties to the list, using commas as the separator. Alternatively, the user property can be sequenced, so we can define multiple instances like ClientPMUserProp1, ClientPMUserProp2 and so forth.

With this technique we can define a list of fields which should be conditionally formatted and the default target value for any list applet. Of course the field names must match exactly those of fields available in the applet's BC.

Ah, and yes, don't forget to compile the applet(s).

Accessing Custom User Properties in a Presentation Model

Any user property defined in the ClientPMUserProp value will be propagated to the property set used to set up the presentation model of the UI object.

As Siebel Bookshelf states, we can currently do this with individual controls, applets or views. To be able to access the values of the custom user properties, we must extend the presentation model and override the Setup method of the custom PM. This is because the Setup method receives a reference to the current object's property set.

The following code shows the Setup method of a custom presentation model extension class, accessing the user properties we created above.

Click to enlarge. Example code for IP 2013 (8.1.1.11)

The screenshot shows the full code with the important lines highlighted.

As you can see, we use a reference to the Oracle-defined set of constants to retrieve the name of the property set containing the applet user properties (SWE_APPLET_PM_PS). This is a recommended practice to avoid issues should Oracle engineering decide to change the naming convention in a future release.

Then we can use the GetProperty method of the property set to retrieve the values of the two custom user properties we created in the first step in Siebel Tools and store them as "local" PM properties so that we can easily access them from the physical renderer.

The custom presentation model must be administered in the manifest as usual and associated with a test list applet (recommended) and later with the DEFAULT LIST APPLET entry (IP 2013 and later). For testing purposes it is recommended to use a single test applet and use SiebelJS.Log() to print the user property values to the browser's JavaScript console.

The Story so far

With the above configurations, we have set the foundation for writing a generic physical renderer extension for list applets which evaluates the user properties and formats the respective list columns accordingly.

Please stay tuned for the second part of this mini-series where we will discuss a possible approach for this solution.

have a nice day

@lex

Siebel Open UI Developer's Handbook - Announcement

It is not without some parental joy that we announce a new Siebel CRM book to be published this winter.

Together with three of the most distinguished Siebel Open UI experts, this humble writer is currently working on putting together useful information and case studies for the upcoming book:

Oracle Siebel Open UI Developer's Handbook

In this book, you will:

• Learn all about the Siebel Open UI Architecture
• Learn to create custom Presentation Models and Physical Renderers
• Learn advanced techniques for Open UI customization
• Understand how to apply custom styles and themes
• Customize and deploy Siebel Mobile Applications
• Integrate Siebel Open UI with external applications
• and more (see below)

As a frequent reader of this blog, you know that the book authors are truly committed to sharing information:

• Duncan Ford
• Alexander Hansal
• Kirk Leibert
• Jan Peterson

We expect the book to be published in Winter 2014/2015 and plan to align it with Siebel CRM Innovation Pack 2014. We are happy to announce as well that you can participate in shaping the book's content and get notified when it is available by filling in a simple form.

Please feel encouraged to grab this opportunity and create a book designed by and for the Siebel developer community.

• Learn more about the book on the publisher's product page.
• View the official press release.
• Fill in the pre-order and feedback form.

have a nice day

@lex

Oracle Launches Customer 2 Cloud Program

In his Siebel Observer publication, Bruce Daley informs us that Oracle changes its policies to allow Siebel support fees to be applied to Cloud products.

***

Oracle Corporation (NYSE: ORCL)  has announced new licensing policies that make it easier to exchange Siebel shelf ware for other CX products. Called the Customer 2 Cloud program, the new policies hope to overcome some of the common financial and technical problems Oracle customers experience in transitioning from Oracle on-premise software to Oracle software-as-a-service Cloud products. The Customer 2 Cloud program allows Oracle HCM and CRM customers to exchange some of their on-premise support budget for new Oracle Cloud products.

"The Customer 2 Cloud program helps organizations get their hands on the latest technology," says Rod Johnson, group vice president, Oracle Applications and Industries Solutions Group. "This program aims to remove the financial and integration challenges that can impact a company's adoption."

Oracle Customer 2 Cloud program is open to Oracle CRM and Oracle HCM customers that are running Oracle's Siebel, Oracle E-Business Suite, Oracle's PeopleSoft and Oracle's JD Edwards EnterpriseOne solutions on-premise. Oracle customers also have the flexibility to shift to a hybrid model with both on-premise and cloud applications.

Customers can convert their existing on-premise support budget to subscribe to Oracle Customer Experience Cloud and Oracle Human Capital Management Cloud services within the same product family. For example, a customer with on-premise seats for Oracle Siebel eService can transfer those seats to Oracle Marketing Cloud.

For more information about the details of the program see http://www.oracle.com/us/corporate/features/customer2cloud/index.html

***

This article was originally published on the Siebel Observer web site.

have a nice day

@lex

Siebel Mobile Web Client Statement of Direction 2014

If you or your customers are using the Siebel Mobile Web Client along with Siebel Remote technology, you should log in to My Oracle Support as soon as your time allows and get the latest Statement of Direction (SOD) document which lays out Oracle's plans for this technology as well as the future roadmap for Siebel Mobile Disconnected Applications.

Image source: Siebel Systems training material

The document is numbered 1663459.1 and can be found here (My Oracle Support account required).

have a nice day

@lex

Siebel CRM Patch Set 7 for Innovation Pack 2013 is Available

Last Saturday, Oracle made the latest patch set 8.1.1.11.7 / 8.2.2.4.7 available for download on My Oracle Support.

Apart from various bugfixes, including the Open UI and Mobile Applications realm, the patch set includes changes to the eScript ST engine which are described in document 1668366.1.

As usual, the patch set comes with a button that says "Read Me" which leads you to the installation guide which also contains descriptions of the resolved issues.

(All links require a valid account for My Oracle Support)

have a nice day

@lex

Siebel Open UI: A Form Apart

Time for another Open UI adventure. In this article, I would like to show you the results of an experiment.

If you watch the Siebel Open UI space attentively, you are sure aware of the introduction of presentation models and physical renderers for views in monthly patch 8.1.1.11.3. And this is exactly what I tried.

What I had in mind was a way to select a record in a list applet of a parent list view (e.g. the "My Accounts" view) and to view details about the record in a form nearby. Of course there is a form applet at the bottom of the view, but what if the end user has clicked the Show More button in the list and needs the information on some other location on her or his screen.

Let's see a screenshot of my experimental solution:

Click to enlarge

 As you can see, the form applet is no longer bound to the bottom of the view. It (or to be more precise, its content) is now displayed in a jQueryUI dialog so the end user is free to move it around, resize it or close it.

What can not be seen on the above screenshot is that the dialog content is refreshed when the user selects a different record in the list.

Another benefit of this solution is that we reuse the existing form applet layout, so we can use Siebel Tools to design the form instead of having to create a form "on the fly". Thus, we save a lot of lines of code.

And here are the steps to implement this (remember, you must apply at least patchset 8.1.1.11.3 for this to work).

1. Create and register a custom view physical renderer extension

Physical renderers (PRs) for views are not really different from PRs for applets. Here is the template I created to get started quickly:

Click to enlarge

If you compare the above code with an applet PR, you'll find that it has the same methods apart from the SetRenderer method.

As fellow Open UI journeyman Jan has pointed out in a previous article, a view PR's Init and Setup method are invoked before the preload event. The SetRenderer method is called after preload but before postload. The EndLife method is called when the user leaves the view.

To register a view PR, you follow the same steps as for any custom file. But of course you choose a view instead of an applet in the manifest administration view. The screenshot below shows my two "victim" views, namely the Quote List View and the Account List View.

Click to enlarge

Both views are now associated with my custom physical renderer file.

2. Implementing the "form in a dialog"

The following code shows the SetRenderer method with my approach to display the form applet of a parent list view in a jQueryUI dialog.

Part 1. Click to enlarge

Part 2. Click to enlarge

The code does the following:

1. Get the applet map of the current view.
2. Loop through the applet map, store business component names and count list and form applets.
3. For the form applet, get the presentation model and the element id.
4. If the view has only one list and only one form applet which are based on the same BC, we have a parent list view and can start creating the dialog.
5. To get the form applet's content, I refer to the table.GridBack selector which represents the main content table of a form applet without the title and buttons.
6. The HTML of the main form is wrapped within a DIV element for easier identification.
7. Now we can use the jQueryUI dialog widget to create the dialog proper.
8. To ensure the dialog content is matching the current record, we attach to the ShowSelection method of the form applet PM.
9. When the ShowSelection method is executed, we can loop through the form applet's controls and populate their identical twins in the dialog with the formatted field values.
10. Finally we set the dialog fields to read-only and hide the original form applet.

Summary

Using a custom physical renderer for a view, we can release content displayed in that view and display it in various ways. The above example showed how to accomplish a "floating form applet" in a parent list view.

And because you were patient with me and imbibed the article until here, you can now download the full code example:

View PR Template
Floating Form PR

have a nice day

@lex

Siebel Open UI: Default Applet Override

One of the lesser known facts about Siebel Open UI - as of Innovation Pack 2013 which introduced database-stored manifest data - is that we can not only register JavaScript files (or web templates) with specific user interface objects but also create default entries for them, so the files will be loaded for each object of the same type. Something we could call a "global override".

Using a global override is superior to using the postload event handler which might soon become bloated with all the stuff you want to achieve on non-specific objects.

Recently, I had some time to investigate this feature a bit more closely. Some of my dear readers might remember the "See-Through Applets" which involves a double-click event handler. When a form applet is double-clicked, the labels are replaced with metadata from the business component layer. Another double click reveals the table and column names where the data is stored. The final solution I presented used a postload event handler.

You can find a detailed description of the see-through applets here and here.

Siebel form applet in "see-through" mode ;-)

So let's see how I adjusted the see-through applet code to work with a global override. The goal was again to enable the functionality on every form applet with a minimum effort.

1. Create a physical renderer extension

The first thing I did was to create a physical renderer extension file. Just the "normal" thing

2. Register the custom file as a default entry

Next, I followed the usual steps to register the file in the Manifest Files view of the Administration - Application screen.

In the Manifest Administration view, the big difference was to query for the seeded DEFAULT FORM APPLET entries in the UI Objects list and copy the existing entry for the Physical Renderer usage type.

Then I proceeded to add an expression and my custom file (as usual). Here is the result:

Click to enlarge

The Open UI framework will read all entries and ensure that the as-delivered files and the custom overrides are loaded whenever a form applet needs to be renderered.

3. Implement the double-click handler

Now I was able to migrate the code which defines the double-click functionality from my custom postload event handler to the new default physical renderer extension's ShowUI method. In fact I could comment out some lines as it was no longer necessary to establish a "connection" to the form applet. Another benefit of staying inside the framework ;-)

The ShowUI method of the override physical renderer. Click to enlarge.

4. Test

I retired (i.e. commented out) the code in the postload event handler and reloaded the browser cache and voilá, the same as before but without extraneous code in the postload event handler.

Summary

"Global overrides" or default entries are a great alternative to clogging your postload event with JavaScript code. At the time of writing, there are various seeded default entries for form, list and tree applets which you should copy to create your custom default entry. Future versions might see other default entries such as for views.

have a nice day

@lex

Looking for a Siebel Job?

In association with Bruce Daley's Siebel Observer publication, the Siebel Essentials blog now supports Siebel job seekers around the world with a simple submission form on the sidebar.

So if you are looking for a Siebel job, please fill in the form on the sidebar or here and submit it. The information you enter will be processed by the Siebel Observer. Bruce asked me to pass on the following message.

Are You for Real? 

Yes I am an actual person and not a brand. I am real and even have been quoted in the Wall Street Journal, the New York Times, and the Financial Times of London about Siebel. Much as I like software bringing people together is something I like even more. Back when I was a kid I was always introducing best friends to one another. After college I introduced a lot of future husbands and wives to each other. Now I am turning my attention to helping people with Siebel skills find openings.

Lately I have been thinking a lot about employment and believe jobs is an issue world wide. This is my attempt to make things easier for people to find the work they need to lead happy, secure, productive lives.  

Help me help you

I truly believe that through grassroots word-of-mouth marketing we've created the best job site for Siebel talent in the world. But that has only happened from people passing on this information to friends, colleagues, and former colleagues who are either actively looking for a new position or are currently employed and looking to move forward in their careers.

I'm always looking for new ways to improve the connections I make and welcome advice on how to make my efforts more effective. Drop me a line if you have any thoughts about how to do this, or the Siebel job market, or anything else I can help you with.

In the meantime use the form found here on Alex's site to help me help you.

All the best,

Bruce Daley
Editor, Siebel Observer

have a nice day

@lex

April Repost: Requirements Analysis

Time for our monthly blast from the past. Below is a five year old article which I believe is timeless, especially in times of Siebel Open UI (scripting). Please enjoy...

(Note: Links have been slightly updated)

***

This is a follow-up post (and the first in a semi-series) on the scriptless Siebel challenge.

Question: Why is so much script code written in Siebel projects?

Possible answers (not a complete list, add your own...):

• Developers are used to write code (we have been coding since Siebel 99, haven't we?).
• Workflow, Business Rules, etc are nice but they are difficult to learn/manage and we don't have time to evaluate solutions.
• Architects and developers don't know that alternatives exist.

As we all agree, the best time to avoid writing custom code in standard enterprise applications is design time. So it's the responsibility of the business analyst or technical architect to design a code-free solution for a given requirement.

Back in the Siebel days (and also today in Oracle days) we spent a lot of time and effort to develop and deliver trainings for business analysts. During these trainings we teach a process based approach to gather and analyse requirements. A business analyst or technical architect involved in a Siebel CRM project needs many skills. Analytical thinking, process orientation and a strong knowledge of the product features is key to a successful design phase.

You might want to read more about business process analysis here and here.

Starting with the high-level process, the business analyst should collect the information and requirements for each step of the process. As the requirements become more detailed, they have to be analyzed whether the standard application ("vanilla", "out-of-the-box") meets those requirements.

We can depict a process for analyzing requirements as follows:

You can minimize the amount of script code dramatically when you apply this simple decision process to any functional requirement.

1. Evaluate whether the requirement can be met by using out-of-the-box (OOB) functionality.
   Examples: Export data to Excel (List Applet), modify the tab layout (User Preferences), save records as a template for others (Quick Fill Templates), predefined queries to name but a few.


2. If there is no OOB solution (a gap situation), there is a high probability that you will find an administrative way to modify the application behavior.
   Examples: Audit Trail, State Model, Activity Templates, Business Rules, Data Validation Manager, Personalization, Runtime Events and everything else you can manage using the administrative screens.


3. There are still many requirements left which you can meet by declaratively configuring the application using Siebel Tools.
   Examples: Create/modify applets, views and screens; set default values; define user properties; create workflows, etc.


4. The (possibly very small) remainder of the requirements can be met by adding the missing functionality by writing script code. The best possible place for your code are business services. Applying industry best practices and using standard business services wherever possible limits the amount of script code that you will have to manage.

have a nice day

@lex

Siebel Open UI: Enabling Drag & Drop in Calendar Views

If you have applied the monthly patch set 8.1.1.11.4 or later, you would expect to be able to manage activities in the Calendar views by dragging and dropping them onto the calendar applet.

However, to achieve this state of bliss there are a view steps to take in the Siebel repository which is not modified by the patchset.

As the attentive Open UI geek you are, you should know that drag and drop functionality is driven by the presence of two applet user properties, namely

ClientPMUserProp = EnableDragAndDropInList
EnableDragAndDropInList = TRUE

Note that the ClientPMUserProp value could be a comma separated list, so we would have to add "EnableDragAndDropInList" at the end, but this is not the case for today's example.

Basically, all we have to do is to add the above two user properties to the list applets in our calendar views (e.g. the LS Pharma HI Activity Calendar View). If there are toggle applets registered for the base applet, we also must edit each toggle applet's user properties list.

In case of our example view, the base applet is the Pharma Calendar Activity List Applet and its toggle siblings Pharma Calendar Account List Applet, Pharma Calendar Affiliated Professionals List Applet and Pharma Calendar Professional List Applet

Using Siebel Tools (of course), we edit these applets and add the aforementioned user properties. After compiling the applets, we can test the functionality in the calendar view (see screenshot above).

Drag and drop an activity (or account/contact from the toggle applets) onto the calendar and (after watching the drag placeholder magically move back to the list) witness the appearance of a new calendar entry. This works in the daily, weekly and monthly calendar mode, as my tests have confirmed.

have a nice day

@lex

Statement of Direction for Siebel Open UI IP 2014

Earlier this month, Oracle has published a statement of direction (SOD) document for Siebel Open UI on the My Oracle Support portal. The document with the Id 1643468.1 lays out the features planned for release with Siebel CRM Innovation Pack 2014 which is intended to be shipped in late fall this year.

The document is especially important for customers and developers who are planning or already implementing features which are not yet available in the current IP 2013 version. 

For information on features like barcode scanning or iHelp and the planned roadmap, please refer the the Open UI Statement of Direction for IP 2014 (and beyond). 

Everyone involved in Siebel Open UI projects is strongly advised to access this document and visit the Open UI Information Center on My Oracle Support frequently in order to stay up to date.

have a nice day

@lex

New Oracle University Course: Siebel Open UI Advanced JavaScript API

Oracle University and this humble writer are proud to announce the availability of a new course which extends the existing Siebel Open UI Foundations offering (which is a prerequisite for the new course).

The new three day course is titled Siebel Open UI Advanced JavaScript API.

Siebel Open UI Advanced JavaScript API course description.

The course will be available as in-class training and live virtual class (LVC) formats and yours truly would be delighted to welcome you to class soon.

The course covers the following areas of Siebel Open UI scripting:

• The architecture and files used in customizations
• Administering customizations
• Writing code to use the Siebel Open UI JSAPI to implement common form and list applet customizations
• Debugging
• Implementing application-wide customizations
• Calling external libraries
• Using Siebel Tools in conjunction with Open UI
• Using the JSAPI with Mobile applications
• Migrating customizations.

See you in class soon ;-)

@lex

Siebel CRM News of the Day

While sifting through the latest alerts, SODs etc on My Oracle Support, I found some interesting news for Siebel folks. While I usually peruse twitter for quick messaging, I believe it is worthwhile to summarize my Sunday evening tweets so that more people get this important pieces of information.

First, all good things come to an end, and even more so for Siebel Management Server, its ADM functionality and the Siebel Management Agent.

Time to say goodbye to Siebel Management Server and Agent. My Oracle Support doc: https://t.co/v2FytD2A2g
— Alexander Hansal (@siebel_ess) April 6, 2014

Second, the good people at Oracle have composed a new Statement of Direction for planned Open UI related enhancements in Siebel CRM Innovation Pack 2014 which is expected for late fall this year.

Siebel Open UI - Statement of Direction - Siebel CRM Innovation Pack 2014: https://t.co/1lboDC9xq0
— Alexander Hansal (@siebel_ess) April 6, 2014

And third, there is a new monthly patchset for IP 2013 - rather early - for April available. But I posted this already.

Siebel IP 2013 April Patchset 8.1.1.11.6 / 8.2.2.4.6 is now available on My Oracle Support https://t.co/E5yDHQgBGl
— Alexander Hansal (@siebel_ess) April 6, 2014

Oh, I nearly forgot there is a new Siebel Open UI Advanced JavaScript API class available on Oracle University.

Coming to an Oracle classroom or your screen soon: Siebel Open UI Advanced JavaScript API. http://t.co/YS0U5fnKWQ
— Alexander Hansal (@siebel_ess) April 6, 2014

Stay tuned for more details.

have a nice day

@lex

Siebel CRM Patchset April 2014

As of Friday last week, Oracle has made the latest monthly patchset - April 2014 - for Siebel CRM Innovation Pack 2013 (IP 2013) available for download on the My Oracle Support portal.

The version numbers are 8.1.1.11.6 and 8.2.2.4.6 respectively.

List of Siebel 8.1.1 patches on My Oracle Support

As is customary for monthly patchsets, the newest one is cumulative and includes all bugfixes and enhancements from previous monthly patchsets.

The installation process if facilitated by Oracle opatch as usual.

To see if you benefit from this patchset, please refer to the installation guide / readme document which lists all the issues addressed - a lot of which are related to Siebel Open UI.

have a nice day

@lex

Siebel Marketing: Campaign Execution Options

One of my favorite Siebel CRM classes is Siebel Marketing Manager. It is a three day course which I have co-designed. Despite the fact it should be upgraded to the latest Siebel version, it is a solid foundation training.

In a recent instance of this class, students inquired about the execution options for campaigns. There are a lot of settings which control the load, launch and delivery behavior of a campaign. You find them when you go to the Design tab for a campaign and navigate to the Execution Options - Advanced view (the technical view name is Campaign Admin Customer Management View).

Now it is not really an established tradition on Siebel Essentials to plagiarize on the Siebel bookshelf but the Siebel Marketing User Guide does a nice job on explaining all these settings.

But I decided to pick some settings which might be of interest to the greater public:

Assignment Options: These settings allow you to control manual or automatic (!) assignment of campaign members using Assignment Managers. The assignment rules must be in one assignment group.

Collaboration Options: Controls whether agents are able to edit certain fields of the campaign members such as the Done flag. In addition, you can control which follow-up buttons are enabled for this campaign.

Delivery Options: When the Use Pregenerated Files flag is set to true, the launch process will use the most recent delivery file (in the List Distribution view), which you probably have pre-generated manually to save time. The Route Contacts and Route Prospects flag control whether to synchronize campaign members to mobile databases. As an older bookshelf version states, Expert Services must be engaged for this.

Load Options: The campaign load process can be controlled through these options. You can choose for example to purge the "Campaign History" (which is the campaign members list) for each new load or create a new wave or use the "most recent good wave". In addition, you can specify which Source Code Format to use and select custom workflow processes to execute before or after the load process or after the launch process. These custom workflow processes must be in the Marketing Custom Workflows group to appear in the pick list.

Email Campaign: These options are only available in version 8.1.1.11 or higher and are visible in the "simple" execution options view (without "Advanced" in the name). They allow using a new feature in the Email Sending Daemon to save copies of all emails to a specified directory.

have a nice day

@lex

Siebel Mobile Applications and jQuery Mobile ThemeRoller

One of the new features introduced with Siebel CRM Innovation Pack 2013 is the ability to use jQuery Mobile ThemeRoller to create custom style sheets for Siebel Mobile Applications (and only for mobile applications, at the time of this writing).

Ever in an experimental mood, I decided to give it a try. Actually the whole bit is documented in the Configuring Siebel Open UI guide in Siebel bookshelf, but as usual you will also find the steps I executed in this post.

Swatches

Before we start, let's talk about "swatches" (and I don't mean the swiss watch brand). A swatch in terms of style sheets is a collection of CSS rules regulating the colors, fonts and icons used in certain areas of web applications.

The following image is taken from the Configuring Siebel Open UI guide and explains the concept nicely.

Image Source: Siebel Bookshelf, Configuring Siebel Open UI guide.

Siebel Mobile Applications use six swatches (A to F) and as per the documentation they control the look and feel of the application as follows:

Swatch	Description
A	Application-level navigation bar
B	List applets
C	Popup applets
D	Grid items
E	Third-level view area
F	Second-level form applets

Using ThemeRoller to create custom swatches

Now that we know about swatches, let's open ThemeRoller and create six swatches...

1. Go to http://themeroller.jquerymobile.com.

2. Use the dropdown list in the version number field to select version 1.3.2. As of IP 2013, Siebel Mobile Applications use jQuery Mobile 1.3.0 and 1.3.2 is the closest currently available.

3. Create six swatches (A to F), using the ThemeRoller UI. This is quite straightforward. I found it useful to take care of the global settings first, then start with a single swatch (delete all others). Using the Duplicate feature, I then created five other swatches based on the first and modified them.

The following screenshot shows some very ostentatious example swatches.

4. Once you're finished, simply hit the Download button and provide a name for the theme to download.

5. Extract the downloaded .zip archive.

6. Open the themes folder which is created as part of the extraction process.

7. Copy the .css files from the themes folder to the PUBLIC/%LANGUAGE%/files/custom folder of the Siebel Developer Web Client and/or Siebel Web Server Extension installation directory.

8. Open the images subfolder in the extracted archive.

9. Copy all files from the images subfolder to the PUBLIC/%LANGUAGE%/images/custom folder of the Siebel instance. (Create the custom folder if necessary).

10. Navigate to the PUBLIC/%LANGUAGE%/files/custom folder and open the file with the .min.css extension using a suitable editor.

11. Replace all occurrences of “images/” with “../../images/custom/”.

12. Save the file.

13. Open the custom mobiletheme.js file which should already exist in the siebel/customscripts folder.

14. Add the following code to the file:

SiebelApp.ThemeManager.addResource(

    "SBL-MOBILE",

    {

        css : {

            custom : "files/custom/mystyle.min.css"

        }

    }

 );

The above code uses the addResource method of the ThemeManager class to add the mystyle.min.css file to the existing SBL-MOBILE theme. Note that the file name could be different, depending on the name you chose in step 4.

15. If not already done, register the custom/mobiletheme.js file in the Manifest Filesview of the Administration - Application screen and add the file to a custom PLATFORM DEPENDENT entry in the Manifest Administration view, providing a valid object expression such as “Mobile”.

16. Launch the mobile application.

17. Verify that the custom style sheet is loaded.

As an alternative to using the addResource method, we can also register a new custom theme.

And here is the result in all it's glory (sorry for the colors but I tried to show the different swatches rather than aim for an award-winning style).

Summary

Using the jQuery Mobile ThemeRoller is a simple approach to quickly create custom mobile themes. 

However, the style sheet produced by ThemeRoller does not cover all aspects of Siebel Mobile Applications such as icons and buttons. The appearance of these artifacts needs manual fine-tuning.

have a nice day

@lex

Siebel Mobile Applications: Create Activities for Outbound Phone Calls

The following is a guest post by Sandra Wamsley, Programmer Analyst at Laerdal Medical. In her article she describes how to use a custom Physical Renderer in Siebel Mobile Applications to capture the event when the user taps the phone icon to make a call as an activity record in the Siebel database. The code samples and manifest configuration described are for Siebel 8.1.1.10 / 8.2.2.3.

***

When we first began developing our Mobile application, an early request came in for the application to automatically create an Activity when an outbound phone call was made through it.

 This was accomplished by having a physical renderer call a business service from within Siebel, which would create the activity. We had to accomplish this on two different business components - Accounts and Contacts - using two different fields.

The physical renderer had to accomplish three things: It had to see that the phone icon had been pressed in the application, get the Id of the Contact or Account that the icon had been pressed on, and invoke the business service, passing it the Contact or Account Id.

We created two physical renderers for our environment, because there were two business components that the business service could be invoked from - Accounts and Contacts. On the Account BC, the PR looks for “MainPhoneNumber” and on the Contact BC it looks for “WorkPhoneNum.”

Below is the code for the physical renderer:

if (typeof(SiebelAppFacade.MobileAccountFormAppletPR) === "undefined") {

 SiebelJS.Namespace("SiebelAppFacade.MobileAccountFormAppletPR");
 SiebelApp.S_App.RegisterConstructorAgainstKey ("MobileAccountFormAppletPR",  "SiebelAppFacade.MobileAccountFormAppletPR");

 SiebelAppFacade.MobileAccountFormAppletPR = (function () {

  function MobileAccountFormAppletPR(pm){
         SiebelAppFacade.MobileAccountFormAppletPR.superclass.constructor.call(this,pm);
 this.GetPM().AddMethod("ShowSelection",recordChanged,{sequence:false,scope:this})
 }

SiebelJS.Extend(MobileAccountFormAppletPR, SiebelAppFacade.JQMFormRenderer);

function recordChanged() {
  var that=this;
  $("#"+this.GetPM().Get("GetControls")["MainPhoneNumber"].GetInputName()+"_tel").on('click',function(){

  SiebelJS.Log(that.GetPM().Get("GetBusComp").GetFieldValue("Id"));

  var svc = SiebelApp.S_App.GetService("Create Activity");
  var iPS = SiebelApp.S_App.NewPropertySet();
  iPS.SetProperty("Account Id",that.GetPM().Get("GetBusComp").GetFieldValue("Id"));
  iPS.SetProperty("Contact Id", "");
  outPS = svc.InvokeMethod("CreateActivity", iPS).childArray[0];
  debugger;
  })
 }
 return MobileAccountFormAppletPR;
 }());
}

This PR was used for Accounts. When the phone icon is clicked to make an outgoing call, the PR gets the Business Component in use to pull the record’s Id (Contact or Account), gets the Business Service (Create Activity), and gives it the Account Id. It also sends a blank string for Contact Id, which we used as an indicator of which PR had been called, but there are many other ways to accomplish this.

The Contact PR was identical, except that it used “WorkPhoneNum” instead of “MainPhoneNumber”, and it sent the Contact Id and a blank string for Account Id.

In addition to the Physical Renderer, we needed to update our Custom Manifest and Manifest Extensions files. In the Custom Manifest XML file, the following two sections were added to the <PLATFORM Name=”Mobile”> section. “MobileAccountFormAppletPR” and “MobileContactFormAppletPR” were the names of the Physical Renderers created earlier.

<KEY Name="MobileAccountFormAppletPR">
<FILE_NAME> 3rdParty/jqmobile/mobiscroll-2.0.full.min.js      </FILE_NAME>
<FILE_NAME> 3rdParty/jqmobile/jquery.mobile.simpledialog.min.js  </FILE_NAME>
<FILE_NAME> siebel/jqmformrenderer.js                            </FILE_NAME>
<FILE_NAME> siebel/custom/MobileAccountFormAppletPR.js           </FILE_NAME>
</KEY>

<KEY Name="MobileContactFormAppletPR">
<FILE_NAME> 3rdParty/jqmobile/mobiscroll-2.0.full.min.js         </FILE_NAME>
<FILE_NAME> 3rdParty/jqmobile/jquery.mobile.simpledialog.min.js  </FILE_NAME>
<FILE_NAME> siebel/jqmformrenderer.js                            </FILE_NAME>
<FILE_NAME> siebel/custom/MobileContactFormAppletPR.js           </FILE_NAME>
</KEY>

In the Manifest Extensions file, we needed to specify which applets should load these PRs. We ended up with five applets that had the option of triggering a phone call, and set the correct PRs from there.

SHCE Account Entry Applet - Mobile = MobileAccountFormAppletPR
SHCE Account Entry Applet ReadOnly - Mobile = MobileAccountFormAppletPR
SHCE Sales Contact Form Applet - Mobile = MobileContactFormAppletPR
SHCE Sales Contact Form Applet ReadOnly - Mobile = MobileContactFormAppletPR
SHCE Contact Form Applet Mobile = MobileContactFormAppletPR

From the JavaScript side of things, that was everything that had to be done. We built a business service to actually create the activity, and once we got them communicating with each other, it worked as intended. Now the user can click the icon to make a phone call, and an activity will be automatically created for them.

***

Many thanks to Sandra for sharing

have a nice day

@lex

Siebel Open UI: Collapsible Applets - Another Revisit

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 navigates to a new view or reloads the current view. If a child applet has no records and the user selects a different parent record which has some records in the child applet, the applet doesn't get automatically expanded. This can be achieved as well but requires some additional logic.
• Not all applets support the "Default Applet Display Mode" user property. An example are most applets on the vanilla home views.

In summary, IP2013 makes it easy to make all applets collapsible and allows to add some additional logic around it.

February Repost: Upgrade Helpers

This is a repost from February 2009, seems that upgrading Siebel CRM doesn't go out of fashion anytime soon, especially with Innovation Pack 2013.

It appears that many of those Siebel consultants are busily upgrading and I think that timeframes are challenging as always ;-)

The following command line utilities are here to help you during the upgrade and save your precious time (you'll need it for other tasks ;-). Please note that the list below is not complete.

1. Log Parser

When Siebel Upgrade Wizard performs the Upgrade Database Schema (upgrep) and Upgrade Physical Schema (upgphys) and any other step against the database, it forwards the command line utilities' log files to a central directory, a subfolder of the Siebel Server's log directory. You can run the logparse executable from the command line and generate a nice and pretty html summary.



The logparse utility is also useful to summarize tasks not related to an upgrade such as a repository migration (notoriously known as dev2prod). You can easily automate it, archive the directory and keep it for later reference.

2. cfgmerge utility

So you merged your repositories? What about the Siebel Enterprise configuration data stored in the Gateway Name Server's siebns.dat file?

On your new Siebel 8.1 production server you will need your custom components as well as the nifty new components from Oracle (such as ADM, BIP etc.). Using cfgmerge on the command line you can create an input file for the srvrmgr command line. You have to edit the file before you run it against the target enterprise.

The utility merges parameter based data for components that exist in both configurations. So if you want to use it for a custom component, you have to create a component with the same name in the target enterprise before you run the utility. The input file will then help you to update the parameter values.

The cfgmerge utility is also suitable for other tasks outside the upgrade process.

3. utleimdiff

This utility is provided to identify differences in EIM tables and their mappings between two repositories (usually Prior Customer Repository and New Customer Repository). During a recent upgrade project, I found that the utility behaves a little odd in 8.1.1. But it's worth to note that it exists.

If you feel that you need more information on a Siebel CRM upgrade and how to do it, please add a comment to this post. Oracle University offers a Siebel Upgrade Workshop on a private event basis.

Have a nice day

@lex