ITCanopy

Issue Description: Configured the Audit Trail for "My Business Component"on Dev Tools and compiled the changes. From Application side map navigated to "Administration - Audit Trail". Created a new record and provided the Business Component name in "Audit Trail Buscomp" applet. Added fields in "Audit Trail Field" applet. Tested and all good. Compiled the objects on Prod srf and when adding the business component in "Audit Trail Buscomp" applet Siebel opened "Business Components" pick applet with no records. Conclusion and Solution: Get the table name from "Business Components" pick applet's BC and run a query on Prod SQL. SELECT * FROM S_BUSCOMP WHERE NAME = 'My Business Component' And there was no record. Now add "My Business Component" to sif file and import it on Production tools. Now when you run the above query it will return record and you will also be able to add record in "Audit Trai...

Description: Configured a new Pick Applet and after compilation when tested, OK button was disabled. Forced the OK button to enable by using CanInvoke = TRUE. When tested Siebel returned below error: SBL-UIF-00348: Method PickRecord is not allowed here. Possible Solutions: Make sure Business Component is not read only for the selected record. Filed on which Pick Applet is configured is not read only on Business Component level. Filed on which Pick Applet is configured Immediately Post Change, Link Specification check boxes are checked.

1: Error Join in business component definition '%1' has source fields that come from tables '%2' and '%3' (SBL-DAT-00452). 2: Steps on which error occurred 2.1. In Business Component created new Join by providing table, alias and outer join flag checked. 2.2. In Join Specification created new record provided the destination column and source field (field is based on base table of the business component). 2.3. In Join Specification created new record provided the destination column and source field (field is based on other table, added using join). 2.4. Created new field based on the new join and exposed in applet. 2.5. Compiled the objects and open Siebel application. 2.6. When navigate to view Siebel returned the above error. 3: Findings and Conclusion: When inspecting the Object Manager (Public Sector) logs could not able to find the exact reason but just the above error. When checked on Oracle Docs found out that documentation is saying that in Join Specific...

0: Overview Sometime as per the requirements you need to display 3rd party web page inside Siebel to achieve that there are two simple steps which are described here in details. 1: Prepare BIP Report URL In this post requirement is to show Oracle BI Publisher report inside Siebel Applet with report filters. 1.1. First Oracle BIP Developer will create report and share report link and important thing here is to ask BIP Developer to share the link without BIP Header page shown in below image. And link will look like this (Removed default filter details as they will auto set when report will open) : http://BIPServer:PORT/xmlpserver/FOLDER/REPORT_NAME.xdo?_xpf=&_xpt=0&_xdo=%FOLDER_PATH%2FREPORT_NAME.xdo&_xmode=2&_xt=REPORT_TITLE&_xf=pdf&_xana=view&_xautorun=false 1.2. Now simply divide this URL into input parameters so that we can configure this URL into Siebel Application. "&" is the key from where you can determine the parameter name and their val...

  There are two ways one is that you change the date format on server level but this will cause issue like if you are getting date in business component and parsing it with some business rule and when you change the date format you need to modify operation everywhere. Below solution is simple and easy to execute. Follow below simple steps to achieve your desired date format. Open Siebel Tools. In Tool go to Applet and query the applet where you want to change the date display format. Now from list or control query the desired date field. Scroll right or use tab to find the "Display Format". Now from below you can make your own date format. For example as per my requirements I am using "DD-MMM-YYYY" after compiling the applet on UI date will display "21-Sep-2022". Format mask Description: YYYY or yyyy four digit year such as 2017 YY or yy last two digits of year such as 17 M month with no leading zero 1-12 MM Two digit month 01-12 MMM Three letter month suc...

Design the workflow. Add new Business Process step on workflow canvas. Add below Business Service Name and Method. Business Service Name: Outbound Communications Manager Business Service Method: SendMessage Now go to " Multi Value Property Window " and Input Arguments and set the arguments as below. AttachFileList > Attachment File path (C:\Siebel\xx.0.0.0.0\ses\siebsrvr\temp\S-WEB-APP_8364_9620_0_Attachment Name.pdf) CommProfile > Communication Profile Name through which Siebel will send the Email MsgBody > Email Body MsgSubject > Email Subject MsgToList > Destination Email (t@t.com; a@a.com) Save the workflow deploy and test. If you need to add attachment from Siebel Contact, Service Request or Case attachment please check the below article: How to get Siebel attachment as file in Workflow If you don't know how to configure or find the working " CommProfile " parameter value please check the below article: Setting up Communication Profil...

You might need to extract a specific file from Siebel Attachments or want to attach that file in Email as attachment. To achieve that Siebel provide a vanilla business service which will get file and return its path. Prepare the workflow and drag drop the Business Service step on workflow canvas. Open properties and set the as below: Business Service Name: FINS Industry BC Facility Service Business Service Method: GetFile Now go to " Multi Value Property Window " and add the below Input Arguments : AttachmentId > Row Id of specific attachment which you want to get as file. BusObjName > Business Object name in which Attachment Business Component is present. FileBusCompName > Attachment Business Component Name. FileNameField > Attachment Name Field. If you are not sure which field is in your case, query " FILE_NAME " in Business Component Column and use that Field Name which query will return. RootBusCompName > If Attachment Business Component is...

In Siebel if you copy the value from field (which have line break character) and paste in notepad it will look fine, but when you use query step in workflow or script and check the logs, the search spec will have a large white space due the line break character stored in data base of that specific column and query will not work. For removing line breaks in a field you can use below eSciprt. Line breaks in strings Windows: \r\n carriage return followed by newline character. Linux: \n just a newline character. Regular Expression: if(MethodName == "Remove LB CR")     {         var vTemp = Inputs.GetProperty("vIn");         vTemp = vTemp.replace( /[\r\n]+/gm, "");         Outputs.SetProperty("vOut",vTemp);         return (CancelOperation);     }   See Also: How to remove Line Break when selecting data from SQL Server

Error: No user key can be used for Integration Component instance 'IC NAME'.(SBL-EAI-04397) Cause: In this case the behavior was encountered on Siebel CRM 8.1 release, where customer had another definition of the same IO deployed in the run time database. The IO deployed in the run time database was later amended to incorporate some changes in the user key fields. Next 'EAI Siebel Adapter' was invoked with a SiebelMessage corresponding to the amended/latest IO definition, which was compiled in the srf but not re-deployed in the runtime database. Since in version 8.1, IOs are first read from the cache and then from the SRF, this made 'EAI Siebel Adapter' to ignore the amended IO definition and throw the user key error. From experience gathered, it is seen that similar incidents can often arise when the "Deploy the Integration Object" checkbox is selected while creating an IO (using the EAI Siebel Wizard). In order to avoid such incidents due to inconsis...

This Article will cover below points: How to create DB View in Microsoft SQL Server. How to provide permissions to DB View. How to export DB View to .sql file. How to create DB View in Microsoft SQL Server: Connect MS SQL Server to Siebel DB. Expand the Siebel DB and navigate to Views Right click on Views and Select New View.. This might take few minutes on first use and it will open below new window from where you can create db view by selecting Table, Views etc. But I prefer to write query and directly use.Click on Close button. On Close you can see a new query window with three sections.  1st section will show the table/ view relational diagram. 2nd section will show the Columns and their details. 3rd window will have the SQL query. Copy and Paste the SQL query in 3rd section and click on other section, MS SQL Server will auto create the relation diagram and populate the Column details. From the top tool bar click on Save button and MS SQL Server will ask for DB View name, pr...

This article will guide you to make field case insensitive for Query/ Search in Siebel Tools. Login the application and navigate to applet for which we need to make field case insensitive. Get the applet name from Help > About View... Login the Siebel tools and query the applet name, from List Column or Control get the field name. Go to the Business Component and query the field name and get the Column name. Go to Table and query through Column name. Right click on the Column name and from menu click on Case Insensitivity... A wizard window will appear, click on Next button. Click on Finish button. Now query the table and Apply DDL. Compile the table on SRF (Server/ Dedicated Client). Login the application and check the change. Note: Oracle does not recommend making field search case insensitive. This slows down the search performance.

Issue: When try to login Siebel Tools error appear as below: Failed to load user preference file 'E:\Siebel\8.2.2.0.0\Tools_1\bin\SADMIN&Siebel Tools.spf'(SBL-UIW-00138)  Reason: Can be multiple reasons, most common is due to disk space full Siebel Tools not able to write data in spf file on close. Solution: Go to file path delete or rename the file and try to login again in Siebel Tools.

Error: The ability to delete records is not available in this screen or applet.(SBL-DAT-00278)    Reasons: The error is thrown in the following case: 1. The No Delete property may be set to TRUE for one of the following repository objects; business component, applet, MVL, Link. 2. The record may be set to read-only by the business component user properties. 3. For business components that have the state model activated, the No Delete parameter may be set to TRUE for the corresponding State Model under Administration - Application > State Models > States.  Source: Oracle Community

Error: The method 'My BS Method' is not supported on Business Service 'My Custom Business Service'. (SBL-DAT-00323)    Possible reason and solution: Check your method which is causing the error, at the end of method add cancel operation as return. if (MethodName == "My BS Method" ) {     //code code code     return ( CancelOperation ) }  

Error: The workflow/task engine cannot determine a next step while executing process definition 'Workflow Name'. The last step that it executed was 'Workflow Step Name'.(SBL-BPR-00176) Reason: This is a problem with the connectors attached to your step 'Workflow Step Name'. Solution: Delete the incoming and outgoing connectors of this step. Save the workflow. Add the connectors again.

Please your wsdl file in Temp folder. E:\siebel\8.2.2.0.0\Tools_1\TEMP Open Siebel Tools and Login. Click on "New" button, "New Object Wizards" window will open go to "EAI" tab and select "Web Services". Click "OK". On "WSDL Import Wizard" provide the Project and specify the wsdl file using "Browse" button and click "Next>". In Next window click on "Finish" button. On Finish below objects will be created in the repository. in Tools Integration Object(s) Business Service(s) and in application Outbound web services. See Also: How to host middle ware or website on iis manager for Siebel How to create and publish Inbound Web Service in Siebel based on Workflow

Normally we use Search specification filed in Applet List, but sometime we have to add long search expression which Search specification field can not contain (max length is 255 characters). For that we can add search specification in applet load server scripts. Right click on applet and from menu click on "Edit Server Scripts". From functions list click on "WebApplet_Load". First get the bussiness component by follow below script var oBusComp = this .BusComp () ; Now add with (The ' with ' statement adds the given object to the head of this scope chain during the evaluation of its statement body.) and statement Add Sort specification as below SetSortSpec( "Created(DESCENDING)" ); Now write search specification on the desired fields for mvl field you need to use "EXISTS". var Search1 = "EXISTS ([Case Contacts] = '" + case_id + "')" Using AND/OR you can extend the search specification. var Search1 = "...

Process: Please follow below steps: Login the Siebel Tools. Query the workflow and from right click select Edit Workflow Process. Drag and drop Business Process step from Palettes window to workflow canvas. Open Properties and provide below Business Service name and its method : BS Name: FINS Teller UI Navigation BS Method: RefreshCurrentApplet Go to Multi Value Property Window and Input Arguments tab, there create new record. Either from drop down of Input Argument field select or directly paste below: Refresh All Set Type to Literal and provide Y in Value field. Connect the step and deploy the workflow and test.

You can use COMCreateObject("WScript.Shell") for displaying the custom message or for debugging the issues in eScript. This can be used in server script and in older versions of Siebel (which supports vb script). Below is the example: //Instantiate var msg = COMCreateObject( "WScript.Shell" ); //Display message msg.popup( "Custom text" + variable ,0, "Message title" ); //Example: of text and variable concatenation msg.popup( "Doc Num:" +docNum + " Owner Id:" +OwnerId+ " P Id:" +POAsrId,0, "Debus Script" ); You can use TheApplication() .RaiseErrorText( "Text" + variable); but Siebel will consider this as error and will not execute any code after this.

You can perform query operation on Business Component through Workflow, eScript with the help of Siebel Operation, Inbound E-mail Database Operations (method: FindRecord) or EAI Siebel Adapter (method: Query but you need to create Integration Objects). This Business Component can be Virtual Business Component (VBC), External Business Component (EBC) or generic Business Component (BC).  See also: Difference Between Business Components and How to Create BC in Siebel through Object Wizard through Workflow with the help of Siebel Operation Create a workflow and provide the Business Object, business component should be in this BO for which you want to perform the query operation. From the Palettes window drag drop the Siebel Operation into workflow designer plane. Select the Siebel Operation box and open the properties window, provide the Business Component name from the drop down list and set Query in Operation field. You can set the search specification by two means either provide the...