Applies to:
Product Release: V7 (Enterprise)Version: 7.7.2 [18325]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-1606004458.
Symptoms
SBL-BPR-00142We created a copy of the Applet Service Request Detail Applet..calling it GEN01 Service Request
Detail Applet. We then created a new runtime event to invoke the Siebel workflow "FS - Verify
Entitlement SR" (to replicate the functionality that is in the Service Request Detail Applet
Verify Entitlement button. However, for some reason, when we press verify on the custom applet
"GEN01 Service Request Detail Applet" we get the error "The input conditions for process 'FS -
Verify Entitlement SR' are not satisfied" this is in the Object Manager log...I pressed the
button on the vanilla applet "Service Request Detail Applet" with the same set of data and it
works fine. In the log I don't see anything different between the input parameters for both of
these applets. I have copied here the section of the log file....the first one is from the
vanilla Service Request Detail Applet. The second section is from the custom
applet. Please advise why this does not work correctly. Is there something in
the verify entitlement workflow/business service that has the name of the applet hard coded? If i
change teh name of my applet to the name of the vanilla one, it works
fine.
Begin: Business Service 'Workflow Process Manager' invoke
method: 'RunProcess' at
105352d8
PrcExec PrcExec 3 0 2004-11-11
16:53:34 Executing process definition
'A-105'.
PrcExec Create
4 0 2004-11-11
16:53:34 Instantiating process definition 'FS - Verify Entitlement
SR'.
PrcExec PropSet 4 0 2004-11-11
16:53:34 Setting runtime value of property 'Namespace: 'USER' Name:
'Field Name' Datatype: 'String''
to:
PrcExec PropSet 4 0 2004-11-11
16:53:34 EntitlementName
PrcExec PropSet 4 0 2004-11-11
16:53:34 Setting runtime value of property 'Namespace: 'PASSTHROUGH'
Name: 'Sub Eve...
Solution
Message 1
For the benefit of other readers:When customer used the <Verify> button on the custom applet "GEN01 Service Request Detail Applet" to call the workflow, the client-side log file showed the following trace and error:
------------------------------------------------------------------------------------------------
ObjMgrBusServiceLog InvokeMethod 4 0 2004-11-11 16:49:40 Begin: Business Service 'Workflow Process Manager' invoke method: 'RunProcess' at 105352d8
PrcExec PrcExec 3 0 2004-11-11 16:49:40 Executing process definition 'FS - Verify Entitlement SR'.
PrcExec Create 4 0 2004-11-11 16:49:40 Instantiating process definition 'FS - Verify Entitlement SR'.
PrcExec PropSet 4 0 2004-11-11 16:49:40 Setting runtime value of property 'Namespace: 'USER' Name: 'Field Name' Datatype: 'String'' to:
PrcExec PropSet 4 0 2004-11-11 16:49:40 EntitlementName
PrcExec PropSet 4 0 2004-11-11 16:49:40 Setting runtime value of property 'Namespace: 'PASSTHROUGH' Name: 'Sub Event' Datatype: 'String'' to:
PrcExec PropSet 4 0 2004-11-11 16:49:40 VerifyEntitlement
[1/5]
Message 2
[2/5]PrcExec PropSet 4 0 2004-11-11 16:49:40 Setting runtime value of property 'Namespace: 'PASSTHROUGH' Name: 'Event Name' Datatype: 'String'' to:
PrcExec PropSet 4 0 2004-11-11 16:49:40 InvokeMethod
PrcExec PropSet 4 0 2004-11-11 16:49:40 Setting runtime value of property 'Namespace: 'USER' Name: 'Triggering Event' Datatype: 'String'' to:
PrcExec PropSet 4 0 2004-11-11 16:49:40 1-NTK9
ObjMgrLog Error 1 0 2004-11-11 16:49:40 (stepexec.cpp (279)) SBL-BPR-00142: The input conditions for process 'FS - Verify Entitlement SR' are not satisfied.
PrcExec PropSet 4 0 2004-11-11 16:49:40 Setting runtime value of property 'Namespace: 'USER' Name: 'Error Code' Datatype: 'String'' to:
PrcExec PropSet 4 0 2004-11-11 16:49:40 SBL-BPR-00142
PrcExec PropSet 4 0 2004-11-11 16:49:40 Setting runtime value of property 'Namespace: 'USER' Name: 'Error Message' Datatype: 'String'' to:
PrcExec PropSet 4 0 2004-11-11 16:49:40 The input conditions for process 'FS - Verify Entitlement SR' are not satisfied.(SBL-BPR-00142)
....
Message 3
[3/5]PrcExec End 4 0 2004-11-11 16:49:40 Stopping process instance of 'FS - Verify Entitlement SR' with an 'Error' status.
Note the error message "SBL-BPR-00142: The input conditions for process 'FS - Verify Entitlement SR' are not satisfied." This is the cause of why the workflow did not execute properly.
The behaviour observed is only showing up with the custom applet. The combination of customizing the applet and the runtime event which the workflow triggers was part of the cause.
The "FS - Verify Entitlement SR" workflow process start off from a runtime event on a specific applet as follows:
Event Object Type: Applet
Event Object: Service Request Detail Applet
Event: InvokeMethod
Subevent: VerifyEntitlement
This branch in the workflow process is of Type = "Condition".
In this case where the applet was copied and named to "GEN01 Service Request Detail Applet", the applet's button is calling the same subevent "VerifyEntitlement", but the applet itself is not the same by name. The failing input condition is on the applet name. If we look at the branch coming out of the workflow process start step, the branch type is "Condition" and one of the condition is the applet name, which the vanilla workflow process process is checking for "Service Request Detail Applet".
.....
Message 4
[4/5]Customer was suggested to try the following:
Make a copy of this workflow process to be used when the button on the custom "GEN01 Service Request Detail Applet" applet is clicked. Name this copied workflow process as "GEN01 FS - Verify Entitlement SR".
Edit this workflow process by going to the branch after the start step, modify the branch's runtime event to have the following:
Event Object Type: Applet
Event Object: GEN01 Service Request Detail Applet
Event: InvokeMethod
Subevent: VerifyEntitlement
Deploy this "GEN01 FS - Verify Entitlement SR" workflow process.
Use Siebel Client > Administration - Business Process > Workflow Deployment, query for this "GEN01 FS - Verify Entitlement SR" workflow process and activate it.
Check the runtime event registration at Site Map > Runtime Event Administration > Events, query for Subevent = VerifyEntitlement, this should return two events now:
One for the vanilla applet "Service Request Detail Applet"
The other for custom applet "GEN01 Service Request Detail Applet"
......
Message 5
[5/5]Check the Action Set Name hyperlink to make sure each event calls a different workflow process ProcessId.
Then, reload runtime event via Event applet > Menu > Reload Runtime Events.
Then, test the <Verify> button on the custom applet to see if this works. Then, also do a sanity check to ensure that the <Verify> button on vanilla applet also still works.
Customer applied the above approach and was able to perform the verify entitlement from the custom applet.
Search keywords: VerifyEntitlement, InvokeMethod, Applet, Service Request Detail Applet, custom, customize, button, Verify, FS - Verify Entitlement SR, workflow, process, input, condition, The input conditions for process, are not satisfied, runtime, event
.
Applies to:
Siebel Workflow - Version: 7.5.3.15 [16279] - Release: V7Information in this document applies to any platform.
Symptoms
Customer had an issue whereby emails were not going out for a workflow process that they have created. When a web SR was created through eService application, an email was to be sent to certain individuals letting them know that the web SR has been created. They could verify that the policy which sets the workflow policy for the email notification got violated; however the email was not going out.Cause
WfProcMgr showed the following error:
(SBL-BPR-00142) The input conditions for process 'RG eService Web SR Email' are not satisfied.
This indicated that the input conditions were not defined correctly for the workflow in question.
It was found that customer had earlier planned to use this workflow through runtime event but later decided to call the workflow through workflow policy violation. The input condition for the runtime event was not required.
Solution
The solution for this SR was to remove the Runtime event condition that was defined in the branch following the Start step. Once this condition was removed, emails started going out.
No comments:
Post a Comment