Search This Blog

SBL-BPR-00164: Method '%1' requires a value for argument '%2'.

Applies to:

Siebel Tools - Version: [6399] Comm/Energy and later   [Release: V6 and later ]
z*OBSOLETE: Microsoft Windows NT Terminal Server
Product Release: V6 (Siebel 2000-Enterprise)
Version: [6399] Comm/Energy
Database: Oracle 8.1.6
Application Server OS: Microsoft Windows NT Server 4.0
Database Server OS: Microsoft Windows NT Server 4.0

This document was previously published as Siebel SR 38-2633173311.



Dear Support,
We have created a new command object, with the following parameters:
Name: Renew
Business Service: Workflow Process Manager
Method: RunProcess
Method Argument: ProcessName=SIS OM Modify Products & Services Process
Target: Server

Following, we have added a new Applet method menu item in "SIS OM
Products & Services Root List Applet (Service) – Tiny" with the
following values.
Command: Renew
Menu text: Renew

After compiling the selected projects we can see the new menu item on
the menu item list but when we select it, we get the following error
Method 'RunProcess' requires a value for argument 'ProcessName'




Message 1

For the benefit of other readers:

You cannot directly invoke the Workflow Process Manager from a command object.

Invoking the Workflow Process Manager can be done via the

Asynchronous Server Requests
Synchronous Server Requests
or the
Workflow Process Manager
business service,

but you will need to specify the Workflow Process Name in a child property, and this cannot be done in the command object.

Please create a business service that uses scripting to invoke the Workflow Process Manager

FAQ 1508: "Asynchronous Server Requests" business service is needed to run workflow asynchronous.
has a scripting example showing how child parameters can be passed.

Depending on how you want to invoke the business service, use either the
Asynchronous Server Requests
Synchronous Server Requests
business Service to run the business service on the Siebel Server (Workflow Process Object Manager),

or, if you want to execute the Workflow Process on the client,
invoke the
Workflow Process Manager
Business Service from your script,

using the example described in

Bookshelf for Siebel eBusiness Applications Version 6.0
-- Siebel Workflow Guide > Chapter 6: Running Workflow Processes > Invoking a Workflow Process > Invoking from a Script


Siebel Technical Support

Applies to:

Product Release: V7 (Enterprise)
Version: [15252]
Database: Oracle
Application Server OS: Microsoft Windows 2000 Advanced Server SP 2
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-979940151.


SBL-OMS-00203, SBL-OMS-00107, SBL-BPR-00162, SBL-BPR-00164

If you try to use the Business Service "Synchronous Server Request" and as input argument select "Component Job" the Pick Applet set always "WfProcMgr" and not the select Job.


Message 1

For the benefit of the other users, it is observed that Component Job name is not correctly reflected in the workflow process for Synchronous Server Requests

Steps to reproduce the behavior :

1) Create a workflow process, 'TESTING'. Include a Start and End step.
2) Goto SiteMap > Server Administration > Enterprise Configuration > Component Job Definition.
3) Create a Job with Component = Workflow Process Manager. Populate the workflow process name = 'TESTING'
4) Create a new workflow process, 'CALLWF' with Start, Business Service, End step.
5) In the Business Service step, set the following :
. Business Service: Synchronous Server Requests
. Method; Submit Request
Input Arguments:
Input Argument: Component Job
Type: Literal
Value: Select 'TESTING' from the pick applet but the values return is WfProcMgr.

When running this workflow process via the simulator, the process fail with an error indicating that the process name is mandatory.

Change request #12-G8F4PY has been logged to address the error.

Workaround :

1) Copy a workflow process manager component

2) Set Input Argument applet for the Synchronous Server Requests business service as follows :

I)     Input Argument : Component
    Type : Literal
    Value : WfProcMgr

II)     Input Argument : WfProcMgr.ProcessName
    Type : Literal
    Value : <workflow process name to be invoked>


Message 2


Depending the workflow process to be invoked here, the following input argument is optional :
III)     Input Argument : WfProcMgr.RowId
    Type : Literal
    Value : <The row_id required to be passed into the workflow process>

Do note that "WfProcMgr.ProcessName" does not exists in the pick list. However, you could input the value in the field.

Siebel Technical Support

No comments:

Post a Comment