GeeKs Blogging @ dotCOM » Applet

Siebel – Symbolic Strings

Nitin Jain — Wed, 12 Aug 2009 05:13:06 +0000

Consider this a brief introductory tutorial on Symbolic Strings in Siebel. Symbolic Strings are from amongst the most commonly used entities in Siebel, especially in Siebel Multi lingual deployments.

They can greatly reduce the job of initializing, deploying, tracking, modifying all the plethora of error/warning messages that you may generally come across in a typical Siebel CRM application.

The Symbolic Strings centralize all the English and non-english language messages at one place in Siebel, where you to manage. You always have the option of doing this independently at all the individual places in Applets, Business Components and the like, but, it is really not recommended.

Symbolic Strings are defined and managed from within Siebel Tools. This Siebel feature was introduced for the first time with Siebel 7.7 (there was a big bunch of innovations that came with this Siebel version for the first time), and has persisted since. So, it could be one serious consideration if you are looking to upgrade from an older Siebel version.

But be careful. Some of the data is not converted to Symbolic Strings automatically during upgrade. This includes, Seed Data, Error Messages, LOVs, lots of non translable attributes, etc. These continue to use the Local based string values.

Migrating to Symbolic Strings in case of upgrade, using the Siebel Conversion and Consolidation process, though could be useful in many ways, is a different topic in itself.

Some of the typical scenarios where Symbolic Strings may be applicable are:
1) Displaying the same string at a number of places in Applets
Assume you have multiple Applets based on the same BC (Sales, Manager, Admin, External) exposing some of the common fields. Why to declare them repeatedly each time (though Siebel still allows you to do that!)? You can just go in to create a Symbolic String. Refer this Symbolic String in the value. Use of the String Override function should be reduced as much as possible!

2) Displaying the same string differently in multiple languages in the application
Either define the different caption for different languages by using the locale option corresponding to the control, else, better still, go in for Symbolic Strings!

Some of the typical advantages of using Siebel Symbolic Strings in your application are:
1) Avoiding redundancy and duplicacy, of course!
2) A centralized place for declaring and updating these user messages.
3) In the process, reducing maintenance, and enhancing value.
4) Reduced development time cycle (the obvious buzzword, TAT!!), and costs.

Do note that some of the other kinds of strings, like LOVs, PDQs, etc. are not covered as a part of the Symbolic Strings functionality. These are defined and used differently in Siebel system.

Related posts:

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

Siebel – Symbolic Strings – Change default ‘X_’ This is a smaill tip I was working on, which...

Siebel – Upgrade Process – Part II This is a continuation from the post, Siebel – Upgrade...

Query on the Long Column or Field A typical problem in any EAI project. Others too!! One...

Siebel – EAI Queue Okay, what are you thinking about? Is it Middlewares in...

Siebel – Popup Update Only

Prachi Sharma — Thu, 25 Jun 2009 03:28:04 +0000

Hi all,

I was working with Siebel Multi Valued Links (MVLs) for some of the configuration requirements in our project. Siebel Configuration is a vast world in itself. I always feel I am learning something new everyday!

We generally use MVLs to fetch data through typical “Links” that we configure in Siebel BCs. We once across an interesting requirement which I am sharing with all of you.

Requirement: To suppress the opening of the MVG Pop up Applet for a particular Multi Valued Field (MVF).

This could be a requirement in a typical scenario where Siebel OOB offers a Multi Valued relationship, but, we have a requirement where it can possibly have a maximum of one record in the relationship. For eg. Requirements say we can have a maximum of one Address per Account, though Siebel OOB solution offers multiple Addresses per Account. There is no need for the user to be opening the MVG Applet and selecting values from it in this case.

While working to try and find solutions to this problem, we noticed that corresponding to the MVL, there is a property by the name of “Popup Update Only”.

To reach this, navigate to,
Siebel Tools Object Explorer -> Business Component -> Multi Value Link

Query for the Link that you would want to modify. Navigate towards the right in the Records window to locate the Property, “Popup Update Only”. Set this to FALSE. This would be set to TRUE in case we need to pop up the MVG Pop Up window to enter values.

Setting this to FALSE, MVG (Multi Value Group) field values can be edited directly from the Parent Applet.

Do let us know in case this helps you some day.

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

Siebel 8 Certification Update All of us want to be certified Siebel experts, don’t...

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

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

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

Siebel – Make MVG Field required – II

Nitin Jain — Tue, 23 Jun 2009 04:47:55 +0000

Hi friends,

This is a follow-up post of the post by Prachi yesterday about making an MVG field Required. You can read the post here. Yes, this truly is an issue in development as the straight OOB methods don’t seem to work at first. However, I personally am quite strongly against scripting in any case anyways!

Nice work, Prachi. But, I feel we may be able to implement the same requirement by simple configuration. Just that it is not so evidently displayed at first.

Try this:
Original Field Name: “Dummy Field”

Create a new calculated field with the following details:

Name: “Dummy Field 2″ (We can actually play with Name/Display Name to make it meaningful)

Calculated Value: [Dummy Field]

Force Active: TRUE

Required: TRUE

You should now see a proper error message whenever a user tries to save a record with NULL values in the field, “Dummy Field”. The error message will, however, point to this new Calculated field. Cheers!

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

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

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

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

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

Siebel – Make MVG Field required

Prachi Sharma — Mon, 22 Jun 2009 05:02:08 +0000

Siebel supports the concept of Multi Valued Fields, or the MVF. These generally relate to fields such as Addresses, or Contacts which may possibly be more than one for a particular Account record. You would generally notice an Inter table which would further store the details.

One of the major problems that pops up is to make these fields Required. This does not work if set at Field level or using the Required User Property for these Multi Value fields.
This can really frustrate the developer.

We can implement this by using the script below. I have tried to set this on a field called, “Dummy Field” for demo:

function BusComp_PreWriteRecord ()
{
var DummyField = this.ActivateField(“Dummy Field”);
DummyField = this.GetFieldValue(“Dummy Field”);

if ((DummyField == “”)||(DummyField == null))
TheApplication().RaiseErrorText(“DummyField is a required field.”);

return (ContinueOperation);
}

Replace Dummy Field name above with your field name, and it should work beautifully.

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

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

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

Query on the Long Column or Field A typical problem in any EAI project. Others too!! One...

Siebel – ActivateField() split wide open In Siebel, we generally tend to use the fields on...

Siebel – Different MiniButton types

Prachi Sharma — Sat, 20 Jun 2009 08:05:31 +0000

You must have come across the so many different types of minibuttons that you can place on your applets. Have you ever gotten confused as to which minibutton to choose for which particular applet?

It’s so nice to be back! Hello to everybody.

I was working on a configuration requirement recently when I needed to add a minibutton on an applet. I noticed that I had many different minibuttons available, and it seemed that all of them perform the same task. I consulted my senior who asked me to just use MinibuttonEdit kind of button. I digged a little deep into it, and, I am sharing here my findings with everybody.

You would find the following different types of minibutton options in Siebel:
MiniButton
MiniButtonEdit
MiniButtonEditNew
MiniButtonNew
MiniButtonQuery

Believe me all of them have different uses. Actually, their visibility on applets is controlled by the selection we make. You can refer the table below for easy understanding:

New Edit Query

MiniButton Y Y Y

MiniButtonEdit N Y N

MiniButtonEditNew Y Y N

MiniButtonNew Y N N

MiniButtonQuery N Y Y

The above selections will ensure that the selected button appears only in the Applet Mode that we want.

Related posts:
Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – DefaultFocus – User Property In Siebel Application, whenever you navigate to a screen, the...

Siebel – About SRF Window – Remove data Okay. This is something those who like to toy with...

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

Siebel – Remove About SRF Window

Nitin Jain — Wed, 20 May 2009 05:35:49 +0000

In my previous post, I had discussed as to how we can control how we can control the data being displayed in the Siebel Client, About SRF window. You can read the article here.

One impromptu question came up from the audience, “What if I want to limit opening of the About SRF window itself in the first place?”. I said, “Nice question!”.

Try out the following steps to disable the About SRF window itself from Siebel Web Client.

Log into Siebel Tools.
Navigate to ‘Application’ in the Object Explorer. In may case, “Siebel Automotive”.
Notice that the Menu property corresponding to this Application reads, “Generic WEB”.
Navigate to ‘Menu’ in the Object Explorer in Siebel Tools.
In the ‘Menu Item’ below the ‘Menu’ in OE, search for the record name as “Help – About SRF”, or the Caption as “About SRF…”.
Set the corresponding property, ‘Inactive’ to TRUE.
Compile into Siebel SRF and Go!

You should no longer see the ‘About SRF’ option in the ‘Help’ menu.

Just as I said with my previous post on hiding data from the About SRF Applet, you can play around with similar other entities as well. Let me know if this helped you. Cheers!

Related posts:
Siebel – About SRF Window – Remove data Okay. This is something those who like to toy with...

Siebel- Close Browser window when logging off In case of standard interactivity applications like eSales , eService,...

Siebel – Popup Update Only Hi all, I was working with Siebel Multi Valued Links...

Siebel – changing Textbox height There are a number of HTML controls available in Siebel....

Siebel – Run Case Insensitive queries This is a nice tip I ran across. All the...

Siebel – About SRF Window – Remove data

Nitin Jain — Tue, 19 May 2009 06:07:58 +0000

Okay. This is something those who like to toy with Siebel may find interesting. I will discuss today, how we can play with the Siebel ‘About SRF’ window when you go Help -> About SRF in Siebel Client Application.

I guess almost all the Siebel users would have seen or used the Siebel ‘About SRF’ window to know about the latest SRF that has been compiled, or other technical information for the application that they just logged into.

However, for a lot of reasons you may want to disable this Siebel feature:
1) Security Reasons
2) Making data available on a Need to Know basis
3) Making available custom information than that in the About SRF window. Or,
4) Just for plain fun!

Either way, a nice to know feature in Siebel.

Remove some data from the About SRF Window

In Siebel Tools, navigate to ‘Applets’ in the Siebel Object Explorer.
Search for the ‘About SRF Applet’ in the List of available applets.
In the ‘Controls’ section below the ‘Applets’ in the Object Explorer tree, select the controls that you no longer want to show on the ‘About SRF Applet’. There would also be corresponding Labels visible as different controls.
Set the property, ‘Inactive’ to TRUE for all these controls and corresponding Label controls.
Compile and go. Tell me what you see!

This concept can also be used to show some customized data onto the Siebel ‘About SRF Applet’ as the requirement may be. Just remember to add the proper controls in the Edit Web Layout section of the Applet.

I am sure that the smartest of the lot will find many more similar applications, related to this implementation. Once you are done playing with this one, drop me a comment telling me how all did you play with this Applet.

Related posts:
Siebel – Remove About SRF Window In my previous post, I had discussed as to how...

Siebel- Close Browser window when logging off In case of standard interactivity applications like eSales , eService,...

Siebel – Autosave Opportunity data – The concept Requirement: System should have capability to automatically save opportunity(RFPs) data...

Siebel – Autosave Opportunity data – Sample Code This is a follow up post on my previous post,...

Siebel – Reading data directly from Siebel SRF SRF or the Siebel Repository File as it is more...

Siebel – changing Textbox height

Prachi Sharma — Mon, 18 May 2009 04:58:16 +0000

There are a number of HTML controls available in Siebel. One such control is the Textbox, or the Textarea. This is generally displayed as a big box on the screen having a height spanning multiple rows.

There was a requirement from my client to modify the number of rows being displayes on the Textbox. He wanted this textarea on the Applet to be 6 rows tall, such that most of the text is directly visible to the Customer Support guy using this view. I will discuss the solution that we implemented to this problem here.

Navigate to the Applet in Siebel Tools, where you need to show this textbox of height equal to 6 rows.
In the Object Explorer, select Controls.
Navigate to the Control which has the Textbox / Textarea.
In the corresponding columns, you will find a property called, “HTML Height”. Set this value as 100.
Compile into the Siebel SRF, and restart Siebel Web Client. You should now see the Textbox with a large height as desired.

Siebel seems to take this value in terms of pixels on the screen. 100 seemed to be reasonable in our case.

Similarly, if you want to change the width of the Textbox, there is another property corresponding to the Textarea control called, “HTML Width”. You can change the width of this textarea to as much as your requirements.

We tried doing this on the Form Applet and it worked.

Related posts:
Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

Siebel – DefaultFocus – User Property In Siebel Application, whenever you navigate to a screen, the...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – About SRF Window – Remove data Okay. This is something those who like to toy with...

Siebel – Remove About SRF Window In my previous post, I had discussed as to how...

Siebel – DefaultFocus – User Property

Prachi Sharma — Sun, 17 May 2009 04:59:26 +0000

In Siebel Application, whenever you navigate to a screen, the default focus of the cursor is set to the first editable field. You may have a requirement to instead set the default focus to a more commonly used field. So, whenever you navigate to that screen, the curson focus will be on the client required field first up, and the user will have to navigate to reach some other field in the applet.

This can be done easily by using a Siebel vanilla Applet level User Property called, DefaultFocus.

In order to use this, simply navigate to the ‘Applets’ object manager in Siebel Tools. Navigate to ‘Applet User Prop’ under the ‘Applets’ Object Manager.

Do a NewRecord and set the following values:
Name : DefaultFocus
Value :

Here, is the name of the column where you want to set the Default focus.

Compile your changes into the Siebel SRF and run. You will now see that the default focus whenever you navigate to the screen, has been set on the required column in the Applet.

This will run for both Form and List Applets. But, somehow this does not run in High Interactivity mode! This works in Standard Interactivity mode only. I hope this article helps somebody someday.

Related posts:
Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – Automatic User Logout Logging out a user automatically, when the user does not...

Siebel – Forcing User Logoff Hi all, Somebody recently asked me if there is a...

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

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

Siebel – millisecond dates on Applet

Prachi Sharma — Sat, 16 May 2009 05:00:34 +0000

I had discussed in my previous posts about invoking a BS in a calculated field for complex calculated calculations, and, about finding out dates accurate to milliseconds. You can read about them from the links below:

Invoking a BS in a calculated field
finding out dates accurate to milliseconds

Today, I will discuss as to how we can show dates on Applets with upto millisecond accuracy. This could be of immense importance in EAI projects as one example, wherein we need to calculate the time spent on each step. Performance debugging could be really enhanced by using this method.

I will extend the concepts introduced previously. We will take the Problem statement to be, “Showing the ‘Created’ time of the Applet, accurate to the closest millisecond”.

For this we would need to create a new custom column of type string in the corresponding table and the Business Component. Whenever a new record is entered in this table, we will populate this new column as well. I will call it “Created_ms”.

I extended the script which I had used in my previous examples like this -

function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{

if (MethodName == “md_getMS_Created”)
{
var d_test01 = new Date();
var d_test03 = d_test01.getMilliseconds();
var d_test02 = d_test01.toString() + ” : ” + d_test03 ;

Outputs.SetProperty ( “out_get_ms_created”, d_test02 );

return (CancelOperation);
}

return (CancelOperation);
}

I have used the methodname, “md_getMS_Created” in this case.
Instead of outputting the value, we can use this script within some other code where we are creating new records. Now, when we expose this column on an Applet, the user will be able to see the time accurate to milliseconds.

I hope this helps somebody some day.

Related posts:
Siebel – getMilliseconds() usage Siebel by default displays all dates in the system accurate...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

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

Siebel – Refresh Applet retaining existing context RefreshRecord() does not work in all cases, does it? This...

Siebel – Number of rows displayed in List Applet

Prachi Sharma — Fri, 08 May 2009 18:16:53 +0000

Siebel Web Client by default shows only the first 7 rows. I guess all of us would have observed that. Today, I will share a Siebel tip as to how we can control increasing or descreasing this default number.

There are two kinds of settings in Siebel to control this:
1) Control the number of default rows being shown. And,
2) The maximum number of rows being shown in one go on the screen. This is when we press the Show More button on the Applet.

Controlling the default number of rows
There is a parameter called “NumberOfListRows” in the “SWE” section of the .cfg file. If you change this value, to say 10, you would see 10 rows by default in the List Applets by default. This is when this setting is not being overridden by some other property in Siebel.

If you want to set the default value of the number of rows to be displayed in only one Applet, you can set the property, “HTML Number of Rows” for that particular applet. This appears as a column in Siebel Tools along with the name of the Applet. Press multiple number of times to reach this particular property in Siebel Tools.

The value will default to 10 in case this property is not set at the indivisual Applet and the CFG file level.

Controlling the Maximum Number of Rows
In the SWE section of the CFG file, you can set the parameter, “NumberOfMaxListRows”. This will control the number of rows to be displayed on the List Applet once the Show More button is pressed and the applet expands.

This value defaults to 20 if not set in the CFG.

These tips are true for 7.x versions of Siebel. I remember one of my friends telling me that there is another option in Siebel 8.0. If somebody knows about that, please add to this post.

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

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel Assets List view – Performance issue / Cannot display records Assets Screen Load is a major problem in Siebel, and...

Siebel – Refresh Applet retaining existing context RefreshRecord() does not work in all cases, does it? This...

Siebel – millisecond dates on Applet I had discussed in my previous posts about invoking a...

Siebel – Custom Applet Title

Prachi Sharma — Wed, 06 May 2009 02:53:18 +0000

There is an Applet title on the top of the Applets. This is normally something simple and static. For eg. Serial Number, Line Items, etc. I will discuss how we can make it dynamic. We will make it dynamic so that it displays something based on the record that is currently selected in the Applet.

I came across this recently when I was trying to practice with the solution suggested by Madhvi in her post on Showing red asterisk on conditionally required fields on this blog.

The Applet title is generally static and constant for an applet. In this article I will show a simple requirement and solution where we change the Title of the Applet on the basis of Account of the record selected. I will take the example of the “Order Entry – Order Form Applet (Sales)” which is the first applet on the Sales Orders screen.

1) Navigate to Siebel Web Client with Order Management functionality available.

2) Navigate to the Sales Order screen using Page Tabs on top or the Sitemap. You should be able to verify the first applet name by going to Help -> About View…

3) Login into corresponding Siebel Tools. Query on the Applets for the applet, “Order Entry – Order Form Applet (Sales)”.

4) Goto the “Controls” section corresponding to the Applet Object Manager. Here, you should see a control by the name of “AppletTitle”.

5) In this record, change the value in the column “Field” to “Account”.

6) Compile and Go. The Applet should now display the name of the Account in the selected record.

This is a dynamic approach because the Title in the Applet will now change from, “Sales Order” to the Account name of the selected record. This will work.

Trying to make it look a little good, we can create a calculated field as below, and use it in the Applet Title above.
‘Sales Order : ‘ + [Account]

This will make it look a little better by showing both the Applet Name and the Account Name. This can be done for any field not just the Account field.

Thanks Madhvi. While trying out your solution, I learnt something new as well.

Related posts:
Siebel – millisecond dates on Applet I had discussed in my previous posts about invoking a...

Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

Siebel – Refresh Applet retaining existing context RefreshRecord() does not work in all cases, does it? This...

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

Siebel – DefaultFocus – User Property In Siebel Application, whenever you navigate to a screen, the...

Siebel – Scrolling between records – UP and DOWN

Nitin Jain — Wed, 29 Apr 2009 03:31:39 +0000

Generally in Siebel Client, we very often have the need to scroll Up and Down among the records. Most of the users would need an easy solution of scrolling UP and DOWN in the records using the normal UP and DOWN arrow keys on the keyboard. Siebel provides an Out of the Box functionality where we use the CTRL + UP or CTRL + DOWN keys to scroll through the records.

I will try to cover here as to how we can customize and modify this OOB functionality such that user can scroll among records using the normal UP and DOWN arrow keys on the keyboard.

The process of scrolling UP and DOWN in the list of records uses the ‘Commands’, “Next Record (SWE)” and “Previous Record (SWE)” in the Tools Object Manager. It is in the corresponding ‘Accelerators’ for the command which tells the system to use CTRL + UP and the CTRL + DOWN keys for this operation. In my case, I inactivated the existing record for ‘Extended’ Browser platform and introduced a New Record in its place. I changed the corresponding values from CTRL + UP to UP, and from CTRL + DOWN to DOWN.

Compiled the changes into the Siebel Client SRF, and I could now scroll between records using only the UP and DOWN arrow keys on the keyboard. No need to use CTRL together with the UP or DOWN key press when scrolling between records.

Related posts:
Siebel – Merge Records Functionality How many times have we realized that there are multiple...

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

Siebel – Merge Records – Checklist I call this Part III, and concluding part of a...

Siebel – SIA BC Utility Service – Loop multiple records This is a vanilla business service which provides an extensive...

Siebel – Automating Merge Records by script – II I call this Part II, as I have already introduced...

Siebel – HTML Code displayed in Error Message

Madhvi Arora — Fri, 24 Apr 2009 03:45:13 +0000

There was a requirement in our project to make Account Field required in Quote entity conditionally. I have already discussed the solution to this and to show the red asterisk in my previous posts below:

Making a field conditionally required
Showing * on a conditionally required field

When user was creating record from list applet and on saving the record he got the right message as “Account is a required field”.
But to our surprise, when record was being created from form applet and now if the user saves the record, he got the following message..

img src=”images/icon_req.gif” alt=”Code Validated” border=”0″ space=”0″ hspace=”0″>Account is a required field.

We always thought that required field message is displayed with the name of the field which is in the BC. But after getting this message, it made me think that this error message takes the reference of the caption for the field in the applet.

This is the expected Siebel behavior to show the full caption of the field that is set to require so if the caption is different than the field name the user will be notified about the field name they see through the user interface.
The workaround to our problem was to either use scripting or do some configuration.
Using scripting was not a good idea, so I used configuration and it worked.

I followed following configuration steps which are described below:
(Note: This is for the case for form applet which uses Grid Layout)

1. Remove caption from the control for the field which is needed to be required.
2. Create a new record in Control in that applet with HTML Type as Label with just the html in the caption to show the asterisk with the name.eg. img src=”images/icon_req.gif” alt=”Code Validated” border=”0″ space=”0″ hspace=”0″>Account.
3. Place this next to the label of the required field so the required field does not need the html in the caption property

Then when the error is displayed you will not need to worry about the html because it’s in a different control.

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

Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

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

Siebel – Autosave Opportunity data – Sample Code This is a follow up post on my previous post,...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – Showing red asterisk on a conditionally required field

Madhvi Arora — Thu, 23 Apr 2009 04:33:28 +0000

In Siebel vanilla Application, we see a red asterisk ( * ) in case the field is Required. However, this asterisk is not shown in case the field is made required conditionally through customization.

We had a similar requirement, to show the red asterisk against a field in the form applet, which was required conditionally. I have already discussed how to make the field read only conditionally in my previous post.

We implemented this by setting the caption of our field on the applet as:
img src=”images/icon_req.gif” alt=”Code Validated” border=”0″ space=”0″ hspace=”0″>Account”

The caption at the Control level in the applet accepts HTML coding for custom display. This worked. Now, we could see a red asterisk ( * ) against our field which was previously implemented conditionally required by using the BC field level User Property “Required”.

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

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

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 – Custom Applet Title There is an Applet title on the top of the...

Siebel Assets List view – Performance issue / Cannot display records

Himanshu Bajpai — Tue, 14 Apr 2009 08:00:57 +0000

Assets Screen Load is a major problem in Siebel, and a major pain area for the concerned developer. I am sure many of you would have come across it in one implementation or the other.

If there are more than 10,000 records in Assets screen, vanilla Siebel Application will not load the screen.

Application will hang for some time and after that it will show an error message similar to the following -

“There were more rows returned than can be shown on the screen. Please ask the System Administrator for support.”

In a typical CRM software, Order Management cycle, we start from an opportunity, and proceed to Quote, Order and finally a billable Asset in that Order. Then Asset to Opportunity, and the cycle repeats itself.

Assets are end results and in all probability, Assets are in million of numbers.

The problem being discussed is that the user has to see All Assets or some cases At least All Asset headers.

Approach 1-

If User can restrict his search, we can go in for a PDQ that return lesser number of records (<10000). This will ensure at least the first load is quick. However, on Blank Query it will again return the same error described above.

Approach 2 (Preferred Approach) -

So, if the developer needs a permanent solution to this problem, he can follow the steps below to show millions of assets without any error-

Login Siebel Tools>

Query for Asset Mgmt – Asset List Applet Applet.

Go To Applet User prop>search for “Disable Buscomp Hierarchy”.If it is set to “FALSE”, make it “TRUE”. After compilation Assets screen will show millions of records without any error. Voila! Problem solved.

This property would be even more helpful for performance if used to show Asset Headers Only.

Please put in your comments. Feel free to add your solution, in case you have come across a different one.

Related posts:
Siebel Admin Mode Flag – II – Issue Log In the last post I described about Admin Mode Flag....

Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

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

Login Failed in Dedicated Web Client : MVF Issue Recently I have met with the Problem in form of...

Siebel – Fetch Active view properties Hi, Working on a typical requirement recently, I came across...

Name:	“Dummy Field 2″ (We can actually play with Name/Display Name to make it meaningful)
Calculated Value:	[Dummy Field]
Force Active:	TRUE
Required:	TRUE

	New	Edit	Query
MiniButton	Y	Y	Y
MiniButtonEdit	N	Y	N
MiniButtonEditNew	Y	Y	N
MiniButtonNew	Y	N	N
MiniButtonQuery	N	Y	Y