siebel

After reading the title of this post, you might have got some idea what the scenario I am going to talk about today. This is the scenario where I have two buttons exposed on the UI and both having the same Method Invoked = "ShowPopup". Here below is the snapshot: 1. Create SR : this button is being used for displaying “Create

After reading my earlier post on sending emails in HTML format, two readers Rishikesh and VP asked, if it is possible sending email using dynamic email template and with the attachments. After reading the complete requirement, I thought its worth a separate post. So, here is the solution - 1. Lets assume we have an email template based on Quote business component as per below screen shot:

A one liner solution for requirement to find out the date difference between two different dates in eScript: function Service_PreInvokeMethod (MethodName, Inputs, Outputs) { var Date1 = new Date("12/22/2012"); var Date2 = new Date("12/23/2012"); TheApplication().RaiseErrorText( "Date1 =" + Date1 + "\n Date2 = " + Date2 + "\n Date Difference in Days = " + (Date2.getTime() - Date1

I am back with a very basic requirement which might looks very easy, but the solution might not be that easy to implement. Requirement: I have a Service Request form applet where I have following fields exposed on the UI: Severity - LOV field values: a) 1-Critical b) 2-High c) 3-Medium d) 4-Low Commit Date - Date Time field Depending upon the Severity, being set by the user, system

Recently I got the chance to work on a EAI requirement which requires the use of business service: "EAI Transaction Service" This post might help you if you are hearing this business service for the first time. First of all, let me tell you what was the requirement for which I used this business service and later will tell you how it works. Requirement We have integration between a

Siebel provides various ways of achieving the same solution, but you need to do the analysis beforehand to pick the right one. Recently I got one basic requirement that: As soon as the Opportunity Sales Stage gets "Approved", all the Activities (Child of Opportunity) status should automatically set to "Approved". Any Siebel Geek can offer multiple ways to achieve this solution: 1. Write a small

I am pretty sure you will find this post very interesting, if you ever get a requirement to send a email in HTML format and email should have the details of the child records(dynamic data) as well.XSLT (XSL Transformation) can do wonders for this kind of requirement where the basic idea is to get data in XML hierarchy from Siebel (which you can easily do via EAI Siebel Adapter and convert it into

Today I am going to discuss one interesting requirement where you are required to make all the Child Business components read only as soon as the Parent business component becomes read-only.Actual scenario goes like this: As per the business requirement, we need to have the Opportunity business component read-only when Sales Stage is Approved. For this simple requirement we configure the BC User

In continuation of the previous post, I found another good way to achieve the requirement of sending email in HTML format and moreover you are required to replace the field values dynamically from business component. So the extra information you need to provide to Outbound Communication Manager is the ROW_ID of the record in context.Suppose, here below is the Email Template need to send in HTML

If you get a requirement to send an email from Siebel, the very simple way is to make use of OOB business service, i.e "Outbound Communications Manager" with the method "SendMessage". Following input parameters would be enough for this purpose: a) MsgToList b) MsgSubject c) MsgBody d) CommProfile Here below is the working example for the same: var inp = TheApplication().NewPropertySet();

One of the interesting requirements I heard recently to put a check on the business component to accept only those records which has the unique value in specified fields. Actual requirement goes this way: “Opportunity Product” is the child business component of “Opportunity” Business Component. System should not allow adding the Opportunity Product record with the same “Product” associated with

The very first expression that any Siebelized person would have after reading the title of this post would be, "hey, what is that?? Join and Link are two different objects in Siebel. Join used for building 1-1 and M-1 relationship and link is being used for building 1-M and M-M relationship. So how come you can build a link via join??".......I knowwww and I am there with you what you just thought

Any Siebel application, which you might have worked on OR currently working on, come with its own landing page. This is something where user will land once logs into the application, in other words the Home Page of the application. This is completely OOB and already configured in Siebel Tools. I just did a query in Siebel tools and found there are around 56 applications which comes with their own

Here is something interesting I found today while working on a requirement in which we need to capture the timestamp of the record when a field get updated.So the exact requirement was : Capture the timestamp of the record when the Status of the Service Request changes to Approved. The field used for this purpose named as "SR Approved On".Now this requirement seems very simple and the very first