siebel

Remember the 'see-through' applets example? If not (and if you're too lazy to click the link), it demonstrates how we can display field-level metadata with a simple double-click on a form applet. Now, whenever I demonstrate this to my students and customers, they really like it. But then always comes the question, what if an unsuspecting end user double-clicks by accident? Of course, we don't want to confuse end users (and the helpdesk staff) with an applet that looks like this: Click to enlarge. So how can we restrict Open UI functionality to certain users or groups such as super users or analysts? One possible answer to this questions is found in the Manifest Expressions view. Let's assume - for the sake of simplicity - that you have assigned positions like 'Siebel Administrator' or 'Open UI Administrator' to some of your fellow employees. With the following custom manifest expression you can easily provide conditional logic to load certain JavaS

Welcome to part 1 of our 'back to school' series on Siebel Open UI. Today we are taking a helicopter ride to get the 'big picture' of the components that contribute to the Siebel Open UI architecture. As indicated in the kick-off post for this series, we keep the tone nice and easy, just in case you are new to Open UI and just started your career as an Open UI developer. But nonetheless, we will dispense some hooks and bait for the seasoned veteran ;-) Let's start with a listing of all the ingredients that make up a good Siebel Open UI discussion: Siebel Repository Manifest Data Web Templates Siebel Web Engine Object Manager Web Server JavaScript Cascading Style Sheets Browser As you might discern, the list is somehow sorted in reverse order. As this is an architectural discussion, we'll start with the foundation rather than the roof. So here we go: 1. The Siebel Repository If you want to define a Siebel view, you need applets. Where are they defined? Of course

Honestly, it has been a while since this time of the year meant 'back to school' for me. However, in my life - personally and professionally - school has never ended (and hopefully never will, just keep on learning). This is essentially true when you make a living with enterprise IT systems such as Siebel CRM. As we all know, Siebel CRM reached a new evolutionary step with Siebel Open UI. On this blog, we have been spreading the news about Open UI from the beginning and as we are getting close to the 100th post on this topic, it seems worthwhile to pause, take a step back and look at the big picture. A big picture... In the following weeks we will look at several aspects of Siebel Open UI from a 'back to school' perspective. The main topics of the series are as follows: Understand the Open UI architecture What Open UI does for you (and what not) Why you should learn CSS and JavaScript now To script or not to script? Guess what! A 'Hello World' physical renderer

Time for another 'blast from the past'. From August 2008, the below article covers the all-time favorite query language that is SQL, but not the SQL you think of now. *** Romeo and Julia(n)? About the Siebel Query Language First of all, it abbreviates to SQL which is kind of funny, of course it has nothing to do with SQL. Just like you can get more out of a spreadsheet application like Excel when you are familiar with its internal functions and syntax, you can get much more out of Siebel CRM if you are familiar with the Siebel Query Language. Where is it used? The answer to this question is very interesting, it is used almost everywhere when you define expressions. It is available in both Siebel Tools and the Siebel Web Client and since version 8.0 both the developement environment and the Web Client (that one since 7.0) sport an expression designer. Expression Designer in the Siebel Web Client click to enlarge Expression Designer in Siebel Tools (since 8.0) Here is a probably

If you follow the evolution of Siebel CRM (and this blog), you sure haven't missed Open UI . The latest patch set for IP 2013 bears the number 10 which makes it only 2 months to go for a full year since the last Innovation Pack. Sure you know that IP 2014 is in the making and there will be a lot to tell the round table as soon as it is generally available. In the meantime, we witness that IP 2013 and Open UI get some good coverage inside and outside Oracle. Today I would like to point out some interesting blogs, articles and news on Open UI - just as it happened. Kudos to all people who are willing to sacrifice some of their private time to share these valuable tidbits of information to make Open UI a success. Blogs of Note I am glad that the blogosphere is steadily picking up Open UI. You should bookmark Oracle's Jeroen Burgers blog " Oracle Implementation Advisor ". He recently published great articles such as on smooth view transitions and worked with fellow blog

Last week, Oracle made the latest patch set 8.1.1.11.10 / 8.2.2.4.10 available for download on  My Oracle Support . As with other patch sets, this one contains a lot of bugfixes for HI, SI and Open UI applications and is of course cumulative. As usual, the patch set comes with a "Read Me" link which leads you to the   accompanying detail information  which also contains descriptions of the resolved issues. (All links require a valid account for My Oracle Support) have a nice day @lex

This humble writer is currently in the student seat and enriching his training portfolio with Oracle Sales Cloud: Incentive Compensation  (formerly known as Fusion Incentive Compensation). As usual, I like to start a learning path with a H.U.G. (Hopefully Useful Graphic). Here it is without further ado. In the diagram we can discern many entities which compose the data model for Oracle Sales Cloud Incentive Compensation. Let's quickly describe each of them: Compensation Plan : This is the overall container. Most importantly, we assign participants (commission/bonus recipients) directly or indirectly - using roles - to the compensation plan. Plan Component : A compensation plan contains at least one plan component. This reusable entity defines the overall logic of the calculation. The logic is defined within the following reusable entities. Performance Measure : This reusable entity allows us to define the basis for the bonus or commission payment. For example, this is where we defi

Inspired by a nice instance of the Oracle BI 11g Build Repositories class I delivered last week as an LVC, I decided to share a little trick with you. What if we could verify the name of the logical table source in Answers (aka "Analysis Editor")? For example, when you create multiple table source for aggregates or partitioned data, it is important to verify your implementation. I found the following procedure to be quite helpful with that. Create a new logical column that displays the name of the logical table source. Within your logical dimension or fact, create a new logical column and map it (physically) in each table source. As the expression use a string identifying the logical table source. Just as in the screenshot below. Click to enlarge. In the above example I specified 'LTS2 F2 Revenue Aggregate' (the exact name of the LTS) as the constant value for the new column. This specific LTS is mapped to an aggregate fact table at the quarter level. In the other l