Closing Of Newly Created Workspace Will Not Take To Previous Screen (Doc ID 2476192.1) in Siebel

APPLIES TO:
Siebel CRM - Version 17.5 [IP2017] and later
Information in this document applies to any platform.
SYMPTOMS
On : 17.5 [IP2017] version, Configuration - General

ACTUAL BEHAVIOR
---------------
Cannot open any workspace in WebTools connect to db2 database

EXPECTED BEHAVIOR
-----------------------
After click the X button, web tools should go the object explorer view. But it stays at workspace page.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Log into Siebel WebTools
2. Select the newly created workspace
3. Click the Open button
4. Click the X button
5. The busy cursor shows up and disappear, but it stays in the same worksapce page. It should to go to the object explorer view

CAUSE
This is a known product defect BUG 27550972 - CLOSING OF NEWLY CREATED WORKSPACE WILL NOT TAKE TO PREVIOUS SCREEN

SOLUTION
Please use the below work around.

1. Log into Siebel WebTools
2. Select the newly created workspace
3. Click the Open button
4. Navigate to Tools->List of values and then to the required types

Source:
https://support.oracle.com/ > Doc ID 2476192.1

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