ITCanopy

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

function GetCurrentDateMMDDYYYY() { var dSysTime = Clib.time(); var dTime = Date.fromSystem(dSysTime); var sYYYY, sMM, sDD; sYYYY = ToString(dTime.getFullYear()); sMM = ToString(dTime.getMonth() + 1); if (sMM.length == 1) { sMM = "0" + sMM; } sDD = ToString(dTime.getDate()); if (sDD.length == 1) { sDD = "0" + sDD; } return (sMM + "/" + sDD + "/" + sYYYY); } -------------------------------------------------------- function GetCurrentDateYYMM() { var dSysTime = Clib.time(); var dTime = Date.fromSystem(dSysTime); var sYYYY, sMM, sDD, sYY; sYYYY = ToString(dTime.getFullYear()); sMM = ToString(dTime.getMonth() + 1); if (sMM.length == 1) { sMM = "0" + sMM; } sDD = ToString(dTime.getDate()); if (sDD.length == 1) { sDD = "0" + sDD; } sYY = sYYYY.substring(2,4); return (sYY + sMM); }

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

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.

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