How to show busy cursor until operation is completed in Siebel

Go to Sitemap.
Search for Administration - Application and click.
In Aggregate view select System Preferences.

create new record and set Busy Cursor Timeout for System Preference Name and set its value in seconds.

all done.

System Preference Name: Busy Cursor Timeout
Default Value: 30
Description: Controls the maximum time the cursor shows as busy. The default value is 30 seconds and is also the minimum value.
The Busy Cursor Timeout preference provides a way to customize the maximum timeout of the application based on the customer process and usage. This system preference does not change the busy cursor behavior. It provides a way to customize the hourglass timing. Busy Cursor Timeout can be interrupted by other processes that also have timeouts, such as Message Bar interval, Portlet session timeout, or any custom implementation that does a polled server call at regular intervals. The Busy Cursor Timeout value should be less than the timeout values of these processes.
The end of the busy cursor period can indicate one of the following events:
1. A process may take more time than the maximum Busy Cursor Timeout value and the maximum time has been reached.
2. The process has completed.
3. The process has been interrupted by another module.

Source:
https://docs.oracle.com/cd/E95904_01/books/ConfigOpenUI/customizing39.html#wp1027381

Comments

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.

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

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

ITCanopy

Search This Blog