Skip to main content

Posts

Showing posts with the label Workspace

After Flattening The Repository, New Workspace Status Is Blank (Doc ID 2431747.1)

APPLIES TO: Siebel Tools - Version 17.6 [IP2017] and later Information in this document applies to any platform. SYMPTOMS On : 17.6 [IP2017] version, Configuration - General When attempting to edit / create new objects under new work space the following error occurs. 1. Workspace Status is blank 2. The selected record has been modified by another user since it was retrieved. Please continue (SBL-DAT-00523) CHANGES  Perform Flatten workspace and try to create new workspace. CAUSE During performing flatten workspacce, internal Seed Data reference got issue. SOLUTION Execute Flattened with disabled the workspace. Renable workspace and test to Create/Edit objects under new workspace. Source: https://support.oracle.com/ > Doc ID 2431747.1

Siebel Tools, Creating Workspace Non-ENU Does Not Set Workspace Status To Created (Doc ID 2351879.1)

APPLIES TO: Siebel Tools - Version 17.3 [IP2017] and later Information in this document applies to any platform. SYMPTOMS On : 17.3 [IP2017] version, Installation ACTUAL BEHAVIOR --------------- Siebel Tools, creating Workspace Non-ENU does not set Workspace Status to Created We are using local (ENU) tools with the Tools Language mode=NLD. When we create a workspace the Workspace Status is not set, it remains empty. When we create a workspace in the webtools, it sets the Workspace Status to 'Created' (actually to 'Aangemaakt', the related Dutch value of Created). EXPECTED BEHAVIOR ----------------------- When create a workspace the Workspace Status should be set STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. When we create a workspace the Workspace 2. Status is not set, it remains empty. 3. create a workspace in the webtools, it sets the Workspace Status to 'Created' (actually to 'Aange...

Unable to make changes to the Object with the newly created Workspace after the upgrade (Doc ID 2497349.1)

APPLIES TO: Siebel Tools - Version 18.12 and later Information in this document applies to any platform. SYMPTOMS Unable to make changes to the Object with the newly created Workspace after the upgrade STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. Login into the tools 2. Create a Workspace dev_sadmin_deu_test 3. In the Action BC > try to inactivate a MVL 4. Getting following error"The selected record has been modified by another user since it was retrieved. Please continue.(SBL-DAT-00523)" CAUSE In the SQL which is causing this Issue STATUS_CD is empty UPDATE siebel.S_WORKSPACE SET   DB_LAST_UPD = current timestamp,   LAST_UPD = ?,   LAST_UPD_BY = ?,   MODIFICATION_NUM = ?,   LATEST_VER = ?,   OBJ_LOCKED_BY = ?,   OBJ_LOCKED_DATE = ?,   OBJ_LOCKED_FLG = ?   WHERE   ROW_ID = ? AND LATEST_VER = ? AND STATUS_CD = ? AND MODIFICATION_NUM = ? SQLParseAndExecu...

Unable To Change Objects In Siebel Tools Using Workspace_SBL-DAT-00523 (Doc ID 2345990.1)

Not able to modify any object in any worksapre, siebel is returning error APPLIES TO: Siebel Tools - Version 17.3 [IP2017] and later Information in this document applies to any platform. SYMPTOMS On : 17.3 [IP2017] version, Configuration - Dev Env When attempting to make any change to objects in siebel tools using workspace, the following error occurs. ERROR ----------------------- SBL-DAT-00523: The selected record has been modified by another user since it was retrieved. Please continue. STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. login siebel tools, 2. open workspace 3. locate object (business component, applet, etc) 4. change any object property CAUSE UPDATE SIEBEL.S_WORKSPACE SET   DB_LAST_UPD_SRC = :1,   DB_LAST_UPD = current_date,   LAST_UPD = :2,   LAST_UPD_BY = :3,   MODIFICATION_NUM = :4,   LATEST_VER = :5,   OBJ_LOCKED_BY = :6,   OBJ_LOCKED_DATE = :7...

Error SBL-DAT-00523 or SBL-DAT-00523 Occurs When Modify Objects On My Workspace (Doc ID 2527635.1)

APPLIES TO: Siebel Tools - Version 18.12 and later Information in this document applies to any platform. SYMPTOMS Using SADMIN user can not modify any object, following error is displayed: ERRORS: ---------------- The state of selected workspace has been modified by another user , workspace will refresh itself and proceed .(SBL-DAT-60295) OR The selected record has been modified by another user since it was retrieved.  Please continue. (SBL-DAT-00523) STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. Log in to Siebel Tools using SADMIN 2. Try to modify an object 3. Above error is displayed CAUSE In the siebdevopenWS.log, there are below error messages: ObjMgrLog Error 1 000000025ca60cc4:0 2019-04-04 08:12:11 (workspacemgr.cpp (2672)) SBL-DAT-00523: The selected record has been modified by another user since it was retrieved. Please continue. ObjMgrBusCompLog Error 1 000000025ca60cc4:0 2019-04-04 08:12:11 (sql...

Workflow on Workspaces in Siebel IP Guide

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

Siebel Webtools Application Logout if User Clicks On Close Button in Workspace (Doc ID 2341292.1)

APPLIES TO: Siebel Tools - Version 17.0 [IP2017] and later Information in this document applies to any platform. SYMPTOMS On : 17.0 [IP2017] version, Upgrade ACTUAL BEHAVIOR -------------------------- Workspace not getting closed in Siebel Web tools IP17 EXPECTED BEHAVIOR ---------------------------- Upon closing the workspace in web tools, it should show all objects locked/ editable for the user to edit STEPS ------------ The issue can be reproduced at will with the following steps: 1. Login to Siebel Web Tools. 2. Click on workspace explorer icon. 3. Select workspace. 4. Click open and then close. 5. Developers are taken back to Login screen. SOLUTION There is no solution available at this time. The workaround of setting the context (may be just by clicking on any applet record) before clicking on workspace explorer can be used to avoid this. Source: https://support.oracle.com/> Doc ID 2341292.1

Work space in not opening in Siebel Web Tools

On : 19.10 version, Configuration - Dev Env ACTUAL BEHAVIOR --------------- work space explorer should be closed and Object explorer should be displayed. EXPECTED BEHAVIOR ----------------------- application hangs STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. Login to Web Tools 2. Click on Work space icon 3. Open a work space 4. click on close button. BUSINESS IMPACT ----------------------- The issue has the following business impact: Impacts dev timelines. Steps to reproduce the issue ====================== 1. Login to Web Tools 2. Click on Work space icon 3. Open a work space 4. click on close button. Application hangs. Tried executing a blank query and then followed the above steps from 2 to 4. Issue not reproduced.

Is It Possible To Create Or Update The LOV Values Directly From Application Rather Than Webtools/Workspace? (Doc ID 2368503.1)

This was not possible in IP17 until 19.3, from 19.3 the LOVs should be editable without creating a WS. APPLIES TO: Siebel CRM - Version 17.4 [IP2017] to 19.3 [Release V17] Information in this document applies to any platform. GOAL Is it possible to create or update the LOV values directly from Application rather than webtools/workspace? SOLUTION Updating LOVs directly from the Application is not supported in IP2017. Users cannot edit LOVs from Administration - Data > List of Values, not even the SADMIN user. This has been removed from IP2017. Users can only update LOVs from webtools/workspace, starting with IP2017. The new behavior is by design for IP2017. The following Enhancement to allow editing of LOVS in Administration - Data > List of Values has been rejected by Engineering:       Enhancement Request Bug 27617505 : LOVS SHOULD BE ABLE TO MODIFY USING ADMINISTRATION - DATA LIST OF VALUES. There have been many queries if the LOVs can be upd...

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