SWE API Commands can be used to perform operations such as login, GoToView and query in the Siebel application. (Replace "callcenter_enu" by the name of the Siebel application that you use.)

• Start the Siebel application.

http://<machine_name>/callcenter_enu/start.swe?SWECmd=Start

• Login to the Siebel application.

http://<machine_name>/callcenter_enu/start.swe?SWECmd=ExecuteLogin&SWEUserName=<username>&SWEPassword=<password>

NOTE: ExecuteLogin is required from 8.0.0.12 onwards in order to obtain a valid Secure Random Number (SRN) for this SWE session. The SRN feature has been added to improve session security. SWE API solutions that attempt to hook into an existing Siebel session will not work with SRN-secured sessions. 

• Navigate to a specific screen in the Siebel application.

http://<machine_name>/callcenter_enu/start.swe?SWECmd=GotoPageTab&SWEScreen=Service+Request+Screen&SWERF=1

NOTE: The SWERF SWE Argument for ReloadFrames is required for the GotoPageTab command to work. Using this command will display the default view specified for the screen.

• Navigate to a specific view in the Siebel application.

http://<machine_name>/callcenter_enu/start.swe?SWECmd=GotoView&SWEView=Contact+List+View&SWEApplet=Contact+List+Applet

NOTE: If you want the user to explicitly login before navigating to the view then use the SWE Argument SWEBU=1 . This will make the user explicitly login before accessing the view. If SWEBU parameter is not specified then anonymous users will also be able to access the view using the above URL provided this view is part of the anonymous user's responsibility.

• Log in to the Siebel application and navigate to a specific view.

http://<machine_name>/callcenter_enu/start.swe?SWECmd=ExecuteLogin&SWEUserName=<username>&SWEPassword=<password>&SWEAC=SWECmd=GotoView&SWEView=Contact+List+View&SWEApplet=Contact+List+Applet

NOTE:  The SWEAC command allows users to string two SWE commands in a single request. For example, the above URL does a SWECmd=ExecuteLogin, and then a SWEAC=GotoView. You cannot reference more than two SWE Commands using SWEAC.

• Navigate to a specific record in the applet. The following URL command will navigate to a contact record whose row id is 12-2DPY4N:

http://<machine_name>/callcenter_enu/start.swe?SWECmd=GotoView&SWEView=Contact+List+View&SWERF=1&SWEBU=1&SWEApplet0=Contact+List+Applet&SWERowId0=12-2DPY4N

• Drilldown on a specific field in an applet. In the following URL, SWEField indicates the drilldown field. If you want to drill down into a specific record, then specify the SWERowId parameter of the row you want to drill down to. When the SWERowId parameter is not supplied in a drill down, then SWE returns the first record in the list:

http://<machine_name>/callcenter_enu/start.swe?SWECmd=InvokeMethod&SWEApplet=Contact+List+Applet&SWEView=Contact+List+View&SWERowId=12-2DPY4N&SWENeedContext=true&SWEReqRowId=1&SWEMethod=Drilldown&SWEField=Last+Name&SWERF=1

• To invoke a business service. In the following URL, SWEService is the name of the business service, SWEMethod is the name of the business service method and Viewname, BusObject is an input argument to the business service.

http://<machine_name>/callcenter_enu/start.swe?SWECmd=InvokeMethod&SWEMethod=Test&SWEService=MyBusinessService&ViewName=Contact+List+View&BusObject=Contact&BusComp=Contact&Id=1-24AKL&SWERF=1

NOTE: SWEMethods such as NewQuery and ExecuteQuery mentioned in the Portal Framework Guide are not supported through the SWE API when specified as a URL. They are reserved for use in the sXML interface. The alternate approach to accomplish this requirement would be to write a business service to perform the necessary query operation and call this business service using bookmark url. 

Drill down to a specific product in product catalog. This requirement can be achieved by using the following commands:

• SWEPostnApplet=<The applet of the destinated view>
• SWEPostnRowId=<The row Id to position>
• SWEView=<The view to navigate to>
• SWECmd=GotoView

http://machine/esales/start.swe?SWECmd=GotoView&amp;SWEPostnApplet=Product+Form+Applet+(eSales)&amp;SWEView=Product+Detail+-+Features+View+(eSales)&amp;SWEPostnRowId=1-CRB

In order to display photo image / picture for a contact, the same configuration as in Immigaration Contacts screen should be done.

In Contacts screen, drilldown on a contact and navigate to "Photographs" view tab. In this view, you can add number of photo images to the contact and set one as primary, which needs to be displayed. This photo set as primary can be viewed in "Immigration Info" view tab.

The applet "PUB Immigration Contact Photograph Form Applet" is used to display the image. You could use this applet in the view, where you want to display the photo of the contact.

However, it is not possible to display the photo in Contact Form applet, because the applet needs a special class (CSSFrameFile) to read the file and display the image.

How can one achieve the requirement to provide a button named "Upload File", and when user clicks it, a file browse window should open, allowing user to select a file and perform an upload of this file in its original format to Siebel File System?

There are 2 options to show the File Open dialog box. The first one is to create a HTML page containing the "HTML File Control" and invoke this HTML page from within Siebel application using "theApplication().ShowModalDialog" browser method. 

Here are the suggested steps:
(1) Create a HTML page named "FileImport.htm" with the following code for example:

<!--

<HTML> 
<HEAD> 
<script language=JavaScript> 
function returnFileValue() 
{ 
var filectrl = document.getElementById("myfile"); 
window.returnValue = filectrl.value; 
} 
</Script> 
</HEAD> 
<BODY onunload=returnFileValue();> 
<Input type=file id=myfile> 
</BODY> 
</HTML>

--!>

This HTML page will contain a file control and user can use it to select the file. Note that "returnValue" property will return the value of the selected file to the caller.

(2) Name the file to "FileImport.htm" and place the HTML page in \Client\PUBLIC\ and \siebsrvr\WEBMASTER\ folders.

(3) In the applet, add a button that invokes "FilePopup" method and enable the button in server "WebApplet_PreCanInvokeMethod" event.

(4) Add in the following code in browser "Applet_PreInvokeMethod" event of the applet to invoke the HTML page:
 

Option 2 is to use "SAFRCFileDlg.FileOpen" or "UserAccounts.CommonDialog" COM objects to show the File Open dialog box. This can be performed directly in Siebel browser script event. As this is provided by a third party, it is not within the scope of our support, please do a search on Google to find out more details on them.

As for uploading the file to Siebel File System in the original format, an external server script (such as ASP, etc) is needed to do so.

The user should have access to Opportunity Quote View depending of the Opportunity Sales Stage : if Sales Stage is A then the view is not available, if the Sales Stage is B, the view is available. 

On the parent BC (Opportunity) used the ChangeRecord event to set the profile attribute as below:

function BusComp_ChangeRecord ()
{
this.ActivateField("Sales Stage");
TheApplication().SetProfileAttr("MySalesStage",this.GetFieldValue("Sales Stage"));
}

In the Client, navigated to the Personalization administration screen and entered a conditional expression GetProfileAttr('MySalesStage') = "01 - Prospecting" for the 'Opportunity Quote View'. This means that when the condition evaluates to TRUE the view will display.

If it is not acceptable to have any views in SI mode, then you could configure a dynamic drilldown on Sales Stage that accesses the Opportunity Quote View for some Sales Stage values and a different view for other values.

A user may wish to default the picklist value of a child business component with the value from a field in the parent business component. Setting the "Predefault value" does not work to default the picklist in the child business component because the picklist is independent of the parent BC. Picklists are independent because they can be used across multiple business components.

Option #1:

Use Business Component User Property "Picklist Pre Default Field n". 

Example:

Option #2:

If other fields are dependent on the picklist, scripting can be used to simulate the picklist behavior. For example, for Promotions, the Period Start Date and Period End Date fields are populated based on the Period selected in the picklist. If the Business Component User Property"Picklist Pre Default Field n" is used, the Period Start Date and Period End Date fields are not populated with default values on the New Record.

Scripting Steps:

1) In the “Parent” BusComp_ChangeRecord event you set the required field value as a global variable using the application SetSharedGlobal method.
2) In Pick Business Component BusComp_NewRecord event you write a script that retrieves the global variable (from step 1) using the application GetSharedGlobal method.
3) Set the correct field value using the appropriate method (SetFieldValue for standard fields or using the Pick functionality for Join fields).

Sample Script for New Record:
 

Solution a)Use a dynamic toggle applet based on the value of certain fields to show the read only applet. These applets are documented in Bookshelf > Siebel Tools Reference > Special-Purpose Applets and Controls > Dynamic Toggle Applets.

Solution b) create new field based on the same column as abstract and make it editable using the property and keep the abstract read only to make child records read only.

When the case insensitive and accent insensitive (CIAI) query feature is implemented, database queries you perform in the Siebel application ignore both case and the use of accents to return records that otherwise match the query criteria. This capability is important when searching for records such as contact or customer names. For example, an exact-match query produces different a query results than a case insensitive and accent insensitive (CIAI) query if the query results contain capitalization inconsistencies (such as MacArthur and Macarthur) or accent usage inconsistencies. CIAI queries apply to the entire query string.