Skip to main content

When adding business component in Audit Trial Siebel is not showing the name

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 Trail Buscomp" applet.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.
Post a Comment
Read more

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...
Post a Comment
Read more

How to create and publish Inbound Web Service in Siebel based on Workflow

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...
Post a Comment
Read more