GeeKs Blogging @ dotCOM » Calculated Function

Siebel – Left, Right and from the Middle

Nitin Jain — Wed, 12 Aug 2009 09:04:28 +0000

Extracting a sub string from a lengthy string in Siebel. What is the best solution you can think up for this typical problem? I know, I know, you and you colleagues have done this thousands of times before. But, have you ever successfully done it without using a single line of scripting?!!

Now, it becomes interesting!

Not that I am saying, it’s entirely possible only by configuration. At the very least I don’t know how it’s possible that way.

Let’s assume a test string:
var strng = “abcdefghijklmnopqrstuvwxyz1234567890″;

Requirement : Take the first 5 characters from the above string in another substring
Solution 1:
var sub_strng = strng.substr( 0,5 );

Output:
abcde

Solution 2 : Using Left() function.
Take it in a Calculated field. Use the expression,
Left( strng, 5 )

Output:
abcde
I have noticed that at times, this does not work within eScript. Should work with VB and in Calculated Expressions.

Requirement : Take the last 5 characters from the above string in another substring
Solution 1:
var sub_strng = strng.substr( (strng.length – 5),5 );

Output:
67890

Solution 2 : Using Right() function.
Take it in a Calculated field. Use the expression,
Right( strng,5 )

Output:
67890
I have noticed that at times, this does not work within eScript. Should work with VB and in Calculated Expressions.

Requirement : Take the middle 5 characters from the above string in another substring (assume ‘cdefg’)
Solution 1:
var sub_strng = strng.substr( 2,5 );

Output:
cdefg

Solution 2 : Using Mid() function.
Take it in a Calculated field. Use the expression,
Mid( strng,2,5 )

Output:
cdefg
I have noticed that at times, this does not work within eScript. Should work with VB and in Calculated Expressions.

Using Calculated Expressions where these are very commonly required, does save scripting at times.

Trust me, this really works!!

Related posts:

Siebel – InvokeServiceMethod() on Calculated Fields InvokeServiceMethod() is used to invoke Business Services and take values...

Siebel – Make MVG Field required – II Hi friends, This is a follow-up post of the post...

Siebel – Make a field Required, conditionally There was a requirement in our project to make Account...

Siebel – Symbolic Strings – Usage Symbolic Strings appear directly in Siebel Tools’ Object Explorer, an...

Siebel – EAI Siebel Adapter Search Spec Hi, I can bet that for anybody who has worked...

Siebel – Make a field Required, conditionally

Madhvi Arora — Wed, 22 Apr 2009 10:51:29 +0000

There was a requirement in our project to make Account Field required in Quote entity conditionally. Had it not been optional, we would have done this by the setting the ‘Required’ property to TRUE for the field in the applet. But, then it would not be conditional, and would always be required.

So, we used an BC field level User Property, ‘Required’. We created an expression which conditionally evaluated to TRUE or FALSE as per our requirement, and we used this against the Required User Property.

Thus, we were able to set the field to required successfully. Though this solved our problem initially, it brought with itself another set of problems which I will discuss in the posts to come.

Related posts:
Siebel – Showing red asterisk on a conditionally required field In Siebel vanilla Application, we see a red asterisk (...

Siebel – Make MVG Field required Siebel supports the concept of Multi Valued Fields, or the...

Siebel – Make MVG Field required – II Hi friends, This is a follow-up post of the post...

Siebel – HTML Code displayed in Error Message There was a requirement in our project to make Account...

Siebel – Admin Mode Flag In my last project,we had a requirement of Admin Views,...

Siebel – LookUpName() and LookUpValue()

Nitin Jain — Fri, 17 Apr 2009 03:47:21 +0000

Hi all,

I was working for a multi lingual implementation recently. This means, the Status on the Order Header was in English if the language selection of logged in user was English, and in Swedish if the language of the logged in user was Swedish.

I came across this problem that at times when the user invoked my custom method on the Orders screen by clicking a button, the Order Status value was passed in his native language – English (ENU) or Swedish (SVE).

The requirement was to
1) read the existing status,
2) do some processing based on as to what the status was, and
3) then reset the Order Status to some new value.

The setting of the Status (3) was not a major issue, as I directly used LookUpValue() function for that which is used very commonly in the Siebel community.

The LookUpValue() function in Siebel queries the S_LST_OF_VAL table in Siebel DB with a combination of TYPE and the LIC (Language Independent Code), and returns the Display Value of that particular LOV.

Step (2) was also not a major issue, achieved through custom workflows.

However, when reading the value in the step (1) to do some processing, it became difficult. The problem was that the Status field could return either of the Swedish or the English value when invoking the custom workflow in step (2). The only option that seemed to be working at the moment was to hard code the values from both the languages, both ENU and SVE. I felt this as a very bad solution. That is when I came across this vanilla Siebel function called LookUpName() which in principle works exactly opposite to LookUpValue().

The function LookUpName() queries on S_LST_OF_VAL table with a combination of TYPE and Display Value (or LIC Code too) and returns the LIC Code in return. This meant, I need not hard code the Order status values in my workflow processing in step (2) for branching. I just started running a LookUpName() on the Order Status received in the beginning, which returned me the LIC code corresponding to that Status.

This LIC code is Language Independent and thus, same in all languages. Thus, I can now do all branching in my custom workflow based on only one LIC code value, and thus it becomes much cleaner!

This also had an added advantage that if the client (CRM owner) decides to implement more languages to this multilingual application, he just needs to apply the corresponding language pack. No changes to script or Workflows are needed.

Please note that I did this using Workflow Output step which meant no Scripting was needed.

Thus, my problem was resolved.

Related posts:
Siebel – LOV Number Limitation Siebel List of Values is probably the most commonly used...

Siebel – Looping multiple records – Update records Hi, We often come across a requirement where we need...

Siebel – SIS OM PMT Service There are lots of vanilla business services available in Siebel...

Siebel – EAI Siebel Adapter – Looping Multiple Records This is a follow-up post on the post, Siebel –...

Siebel – EAI Queue – Usage I had introduced the concept of Siebel EAI Queues in...