Xplore Siebel Configuration

Notice Please note that the About View popup is used just for testing purposes in the Standard Interactivity Siebel clients. This is intended as help for developers who want to find out the names of views/applets they are working on. Background The About View popup applet provides details of the screen, view, business object, applet, and business components, currently being displayed in the Siebel application window. This technical note describes how to implement this functionality in the Siebel customer facing applications. Implementation The About View dialog box could be invoked through a button in the frame view bar of the Siebel application.  The button will invoke the “AboutView” method (“About View (SWE)” command) that displays the About View dialog box. The following needs to be configured in Siebel Tools: 1. Siebel Customer Facing Application: First the user needs to determine the template used for the frame view bar of the customer facing application...

Pre requistes: Windows Server 2008 OS installed system IP 15 Client installations setup(Can be downloaded from http://edelivery.oracle.com with a valid account) STEPS: Tools Installation Download the installables in the local environment and navigate to to the location:"D:\Siebel\15.0.0.0\Windows\Client\Siebel_Tools\Disk1\install\setup.bat". We use this batch file as it has certain parameters that are set with the installation, we can see that when we open the setup.bat file in notepad. Navigate to Next As we don't want any emails to obtained from oracle regarding updates and all thus unselect the checkbox and navigate to next page We select the option"New installation" and navigate to next page As I have only one directory in my local thus I install in C drive. Its advised that we install in D drive and any other drive other than main directory (eg: C) as the same can be salvaged during memory crash, less prone to mem...

Here is the example of Exposed Calculated fields Today() TimeStamp JulianYear of Today JulianMonth of Today Julian Day of Today Build a date: Calculation: "0"+(JulianMonth([Created])-JulianYear([Created]) * 12)+"/"+"01"+"/"+(JulianYear([Created])-4713) For Month: (JulianMonth([Field])-JulianYear([Field]) * 12) For Year: (JulianYear([Field])-4713)

From Script:                 var inputPropSet; var outputPropSet; var taskUIsvc; inputPropSet = TheApplication().NewPropertySet(); outputPropSet = TheApplication().NewPropertySet(); taskUIsvc = TheApplication().GetService("Task UI Service (SWE)"); inputPropSet.SetProperty("TaskName","<Task Name>"); taskUIsvc.InvokeMethod("LaunchTaskFromScript",inputPropSet,outputPropSet);

Problem: There was a scenario, where I had to Pass the effective date of an Insurance policy to the workflow for further processing whenever the user clicks a button Solution: I used the browser script of that applet and invoked the following script:       if(name == "<button method>")     {     var person = prompt("Please enter the effective date","MM/DD/YYYY");     var datePat = /^(\d{2,2})(\/)(\d{2,2})\2(\d{4}|\d{4})$/;     var matchArray = person.match(datePat); // is the format ok? if (matchArray == null) { alert("Date must be in MM/DD/YYYY format");  } else{ //Month Check var month = matchArray[1]; // parse date into variables var day = matchArray[3]; var year = matchArray[4]; if (month < 1 || month > 12) { // check month range  alert("Month must be between 1 and 12"); } //Day Check if (day < 1 || day > 31) {  alert("Day m...

Solution: Add following lines in the client and tools cfg as required. [EAIFileTransportConfigSubsys] EAIFileTransportFolders = c:\;d:\

Calling a Workflow from user property BC User Property Named method n Value- "Change Plan",  "INVOKESVC", "<The BC In which the User property is defined>", "Workflow Process Manager", "RunProcess", "'ProcessName'", "'<Workflow Name>'", "'RowId'", "[Id]", "'<Process Property>'", "[<Field Name>]", "'<Process Property>'", "'<String Value>'" Note: RowId- This points to the 'Object Id' Process Property of the workflow. [Id]-This points to Id Field in the BC Application RunTime Create a Action Set: With Action Type: BusService Business Service Name: Workflow Process Manager Business Service Method: RunProcess Business Service Context: "ProcessName", "<WorkFlow Name>" The Object Id is defaulted with Id Field