ITCanopy

Error: Error invoking service 'EAI Siebel Adapter', method 'Update' at step 'Workflow Step Name'.(SBL-BPR-00162)--No user key can be used for the Integration Component instance 'Integration Component Name'.(SBL-EAI-04397) Steps to Reproduce: Created new Integration Component in Siebel Tools and set Id field (system default) as the Integration Component User Key. Created Data map in Siebel Client. Added a query step in workflow and get the response in Siebel Message process property. (EAI Siebel Adapter, Query) Added Data Map step and used above response. (EAI Data Transformation Engine,Execute) Added Update step and used the response of Data Map step. (EAI Siebel Adapter, Update) Deployed the workflow and run. On Run received the above error. Reason & Solution: From the Workflow instance logs got the Siebel Message value (from Step 3 and 4) and on inspection found out that Id tag was missing. When checked and compare the Id field in Integration compo...

Workflow instance monitor have three separate tables. One for logging workflow run (workflow instance), second for its steps execution to log (workflow steps) and third for logging the values of each process property value against each step of workflow (workflow process properties). If you increase the Workflow Monitoring level over the time tables space and DB load will be increase and sometimes instance monitor will be stopped working (Check Siebel Workflow Instance Monitor not working to fix this issue) . Its a good practice to delete the old workflow instance monitor records. Below are the queries for deleting the data. Its better to delete only old data and Year is perfect condition. Workflow Instance select count(*) from S_WFA_INST_LOG where EXTRACT(YEAR FROM TO_DATE(created))='2022' --delete from S_WFA_INST_LOG where EXTRACT(YEAR FROM TO_DATE(created))='2022' Workflow Instance Steps select count(*) from S_WFA_INSTP_LOG where EXTRACT(YEAR FROM TO_DATE(created))=...

Issue Details: In "Active Workflow Processes" Monitoring Level of  workflow is set to "3 - Detail" but when check the "Workflow Instance Monitor" there are no "Step Instances". Step to find the root cause: Set the Workflow Monitoring Level to "3 - Detail". Increase the Application Object Manager (in this case Public Sector) logs to level 5. Re login the application and invoke the workflow.  Find the Public Sector OM logs. (Path: C:\Siebel\15.0.0.0.0\ses\siebsrvr\log) Open the log file (PSCcObjMgr_enu_*.log) and search "Instantiating". When you find your Workflow step name (set in workflow) scroll down and find the place where Siebel is inserting the "Step Instance" and "Process Properties". Carefully read the end lines and you will find the issue. In my case below was the issue mentioned in logs: SQLParseAndExecute    Execute    5    000000fa635f2ee4:0    2022-10-31 21:10:15    OCIStmtExecute: DML erro...

Issue Steps (Siebel UI): Go to Contact Screen and Contact List. Drilldown Contact Name and Attachment Detail View. Click on New Button in Attachment applet, select file. Step off, or click on save button. Siebel Return an error. Error Details: [1]Error occurred while creating file in filesystem. Please contact your system administrator. (SBL-SVC-00184) [2]Error occurred while opening file 'S_CONTACT_ATT_ROWID.SAF'.(SBL-UIF-00229) Issue Steps (Siebel Workflow): Invoke workflow which is trying to add attachment using EAI Siebel Adapter. Error Details: [1]Error Invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Upsert Attachment'.(SBL-BPR-00162) [2]Method 'New Record' of business component 'Email Attachments' (integration component 'Email Attachments') for record search specification '[Parent Id] IS NULL' returned the following error: "Error occurred while opening file 'S_CONTACT_ATT_ROWID.SAF'.(SBL-...

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...

After completing the workflow you need to deploy. There are two ways either publish from tools or export workflow as xml and import from client side. My practice is to export workflow as xml and import. Errors: 1. 'EAI XML Read from File' service with method 'ReadEAIMsg' failed while processing XML from file *_temp_*.xml SBL-EAI-04264 2. The XML document cannot be converted to and XML hierarchy SBL-EAI-04110 3. XML Hierarchy Converter error - empty input message, expecting an XML document in <Value> of input arguments SBL-EAI-00246 Action: Facing above errors while importing workflow xml in Active Workflow Processes. Possible Reason & Solution: The drive on which Siebel is installed does not have free space. Try deleting log archives and dedicated logs if any. Make sure drive have empty space.

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.

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 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...

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...

Through eScript  BC InvokeMethod if (MethodName == "MyMethod") { var oBS=TheApplication().GetService("Workflow Process Manager"); var Inp=TheApplication().NewPropertySet(); var Out=TheApplication().NewPropertySet(); Inp.SetProperty("Object Id",TheApplication().ActiveBusObject().GetBusComp("My BC Name").GetFieldValue("My BC Field")); Inp.SetProperty("ProcessName","My Workflow"); oBS.InvokeMethod("RunProcess",Inp,Out); return (CancelOperation);   } On BC PreSetField if(FieldName == "My Field Name")    {     if(FieldValue == "My Field Value") { var Inp=TheApplication().NewPropertySet(); var Out=TheApplication().NewPropertySet(); Inp.SetProperty("Object Id",TheApplication().ActiveBusObject().GetBusComp("My BC Name").GetFieldValue("My BC Field")); Inp.SetProperty("ProcessName","My Workflow...

APPLIES TO: Siebel CRM - Version 7.8.2 [19213] and later Information in this document applies to any platform. SYMPTOMS Following error will be reported by EAI Data Transformation Engine (Intgeraiton Object Declarative Data Mapper) when mapping file attachment (copying file content) from improperly configured / provided source Integration Component Field; SBL-EAI-04058: Source expression generated attachment ID '...' but the corresponding attachment cannot be found. CAUSE The field type of the source (and also traget) Integration Component that (the field) provide the file attachment content has to be "DTYPE_ATTACHMENT". The error occurs if it is set  to  "DTYPE_TEXT" (that may be default setting provided while creating  the Integration Object from XSD schema using Siebel Tools Wizard. Also there are alo following requirements for the text (VALUE) of the XML element in the input XML document where the source integration object is instantiat...

Please follow the below steps: Create or Edit workflow. Add Business Service step. Set Business Service Name: Web Engine HTTP TXN Set Business Service Method Name: GetAllServerVariables Go to Output Arguments of Business Service Step and set the values as below: Property Name:  IpAddr Type:  Output Argument Output Argument:  REMOTE_HOST Please note:  This business service does not fetch the valid IP address on the Siebel Dedicated Client, it is only applicable and should only be used/tested using Siebel Web Client.

Workflow on Workspaces  Workflows are one such object on workspaces that must be managed only from a workspace. You can perform all activities on workflows, such as, create a new workflow process, modify an existing workflow process, import or export a workflow process and so on. A workflow process is tracked through workspace. To work on a workflow process: 1.   Create a workflow process record in a developer workspace under the parent or integration workspace. 2.   Make changes to the workflow process and when you complete making changes, click Publish. The status of the workflow process is set to Completed. The workflow is ready for delivery and activation. 3.   Submit the workflow for delivery. The status of the workspace changes and makes it ready for delivering the changes to the parent workspace. 4.   Deliver the workflow to merge the workflow changes with the parent workspace (Main/ Integration workspace). 5.   A...

APPLIES TO: Siebel Workflow - Version 17.6 [IP2017] and later Information in this document applies to any platform. SYMPTOMS PRODUCT VERSIONS: ------------------------------ SIEBEL VERSION: Siebel 17.6 [IP2017] SIEBEL APP O/S: Oracle Solaris on SPARC (64-bit) ISSUE STATEMENT: ---------------------------- When there are multiple versions of a workflow process in IP17 Siebel Tools (3 versions in this particular issue), and modify its latest version, delivering the workflow process then generates generates and error. Furthermore, when trying to publish and activate the workflow process from Siebel Tools, it generates another error. ERROR MESSAGE: -------------------------- a. The error that occurs when trying to deliver the workflow process is the following: The deliver failed with error: The same values for '<?>' already exist. If you would like to enter a new record, please ensure that the field values are unique (SBL-DAT-00382) b. The error tha...

APPLIES TO: Siebel CRM - Version 19.3 and later Information in this document applies to any platform. GOAL How to activate the Workflow in the client application after having it changed in Tools? SOLUTION Before 19.3 the following were the steps to publish and activate a modified Workflow (Please refer to IP17 Workflow Process Publish Errors With "Cannot activate task "WF NAME' version [4]. Make sure it has 'Completed' status. (SBL-BPR-00501)" (Doc ID 2394134.1)): Create a workflow process record in a developer workspace under the parent or integration workspace. 2. Make changes to the workflow process and when you complete making changes, click Publish. ***************** PUBLISH In DEV The status of the workflow process is set to Completed. The workflow is ready for delivery and activation. 3. Submit the workflow for delivery. The status of the workspace changes and makes it ready for delivering the changes to the parent workspace. *******...

WF/Task Editor Tool Bar Buttons Functionality When a workflow is managed through a workspace, the buttons on the WF/Task Editor Tool Bar function as following: Publish/Activate: Publishes and activates a workflow process in a single step. The workflows from only one workspace (MAIN by default, or any other INT WS identified in system preference) will be published/activated when they are delivered into that workspace. Add the following System Preferences in Siebel Tools and relaunch tools: System Preference Name: WS Name For WF Activation System Preference value: Name of the INT WS where WF publish/activation should be enabled. On clicking the button, a new run-time instance of the workflow gets created. The workflow process becomes available for use. Source: https://support.oracle.com/ > Doc ID 2537061.1

Siebel is returning below error, when invoking Outbound Web Service through Workflow. Error Code (SBL-BPR-00162)--IDS_EAI_WS_OD_RESPONSE_EXPECTED Error Message Error invoking service 'Business Service', method 'Method Name' at step 'Workflow Step Name'.(SBL-BPR-00162)--Operation 'Method Name' is expecting a response but no response was received.(SBL-EAI-04311) You should be getting above error while invoking Outbound Web Service through Workflow. Reason: Web Service might be unavailable at the host location. The machine on which Siebel Web Server is installed is not able to access the end point URL. Solution: Check with Vendor. Add entry of End Point URL in Windows Host file or exclude from Firewall and Antivirus.

Add new Business Service step in Siebel Workflow, set its properties as below: Business Service Name: Inbound E-mail Database Operations Business Service Method: InsertRecord Set the values of Input Arguments as below: Input Argument: BusComp Type: Literal Value: Service Request Input Argument: BusObj Type: Literal Value: Service Request Input Argument: Field: Status Type: Literal Value: In Process Note: While inserting the record Value In Process will be set against the Status field, you have set values of all required fields. Can add multiple field in similar manner. Set the values of Output Arguments as below: Property Name: SR ID Type: Output Argument Output Argument: Id Note: It will return the Row Id of newly inserted record.