Invoking workflows in Siebel has become very easy since the introduction of Runtime Events. Runtime events saves a lot of time for developers. We no longer have to create triggers or workflow policies to invoke workflows on certain record events.
In this post I will explain how easy it is to invoke a workflow using Runtime Events.
Objective: Execute a Workflow "SiebelGuide Lead WF" when a new Opportunity is created.
Steps:
-
Create the Workflow, Test and Deploy it.
-
Create an Action Set.
-
Go to Sitemap-> Administration-Runtime Events->Action Sets
-
Create a New Record
-
Under this one Action set you can run more than one action like Workflows or Business Services.
-
Name = "SiebelGuide_com_RunWF"
-
Choose Action Type = BusService
-
Enter Business Service Name = "Workflow Process Manager"
-
Business Service Method = "RunProcess"
-
Business Service Context = "ProcessName", "name of Workflow"
-
See the screen shot below
-
-
- Create Event Aliases
- Name = "Opportunity - New"
- Object Type = "BusComp"
- Object Name = "Opportunity" (This defines on what BC you need to trigger on)
- Event = "NewRecord" (This defines the event)
- See the screen shot below
- Create a Events
- Name = "Opportunity - New" (Here you choose the Event Alias you created in previous step)
- Action Set Name = "SiebelGuide_com_RunWF" (Here you choose the Action Set you created in Step 1)
- See the screenshot below
- Logout and Login back to see if your workflow is working.
- Whenever a New Opportunity Record is created the Workflow will be run.
Hope this helps. Comment if you have any questions.a
Related posts(Auto Generated):
December 20th, 2008 at 9:18 pm
Can I control whether the Workflow invoked by the RTE is Synchronous or Asynchronous call. If yes, how?
Thanks.
December 22nd, 2008 at 4:29 am
Check Siebel Book Shelf. Siebel Business Process FrameWork workflow guide->Invoking Workflow processes page 171 as per Siebel 8 Bookshelf.
From a run-time event with Processing Mode set to Remote Synchronous or Remote Asynchronous
July 23rd, 2009 at 8:21 am
Hi All,
In our application we can create Case from Case Home Page Screen [Virtual BC] after clicking “Add and Go” record will be display in Case Form Applet where we can enter Rest of the details.
Our Issue
There is one field “due date” where a work flow will calculate the due Date and populate the value there . the work flow is called by Run time event write record in HLS Case BC.But in our case the run time event is not getting triggered and the due date is not calculating for the records which are creating by this.
workaround
if we press ctrl + s it will call the workflow and due date is calculated.But user is checking for solution where he doent want to do this
solution we tried
–>we tried to put the same condition in runtime event change record of HLS case and it is working .But as it is on change record when ever there is change in certain field[where the change record expression depends] it is getting fired so mutiple times it is getting fired and it may leads to performance issue .
–> tired to refresh the view through script but still it is not working .
–>tried to do through a policy and it is working but once the policy got triggered and user tried to change the record at the same time where the workflow is also trying to update one record use will get error saying some other user is working on this record and it will make the record missing .so we can go with this .
could some one suggest how we can achieve this requirement .
thanks and regards
Joseph thomas
August 6th, 2009 at 6:31 am
Hi,
Can we create a Run time even in our SAMPLE database and test it ?
August 6th, 2009 at 5:21 pm
you should be able to. Never tried though.
December 20th, 2010 at 9:51 am
Hi,
I have a question.
What is the time point to trigger the workflow?
I mean before the opportunity save to DB or after.
Thanks
October 18th, 2011 at 8:45 am
When we should Invoke the Workflow through runtime and when through Workflow Policies?
February 3rd, 2012 at 2:06 pm
@Archana
Whenever we use the UI to trigger a workflow use Runtime events.
Use Workflow Policy whenever it is necessary to detect a database event.