Skip to main content

How to Publish a Workflow Process From 19.3? (Doc ID 2537061.1)

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. *********** SUBMIT from DEV To INT

4. Deliver the workflow to merge the workflow changes with the parent workspace (Main/ Integration workspace). ******* DELIVER from INT to MAIN

5. Activate the workflow using the Publish/Activate button on the WF/Task Editor tool bar. Activation of the workflow deploys the workflow, making the workflow available for use in the application. **** ACTIVATE IN MAIN


By default it is no longer needed to "Publish" the Workflow Process from 19.3. Related buttons will be disabled.

1. Create an INT Workspace under Parent MAIN

2. Create a DEV Workspace under INT

3. Locate any workflow and make a small change

4. Workflow Status remains as "Completed"
Version is still 0

5. Checkpoint / Submit for Delivery / Deliver from DEV to INT

6. Open INT WS and Submit for Delivery / Deliver from INT to MAIN

In Client:

6. Activate the Workflow (Version 0)
If you still want to manually Publish/Activate the Workflow in which will have the workflow "Activated" in the Client, then please refer to Business Process Guide: https://docs.oracle.com/cd/F14158_03/books/BPFWorkflow/whats-new-in-this-release.html#whats-new-in-this-release where it says:

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

Comments

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.

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