on Apr 17, 2018CREATE ACCOUNT web service call fails if I add additional request info/ Variables as parameters. Actually we need to pass on Additional parameters defined by users for the create account fulfillment.
https://host:port/aveksa/command.submit?cmd=createChangeRequest&token=xxxxxxxxxxxxxx
<UserChange>
<Operation>Create</Operation>
<Account>XXXXX</Account>
<Parameters>
<Parameter scope="job">
<Name>Add</Name><Value>false</Value>
</Parameter>
</Parameters>
<BusinessSource>ABC</BusinessSource>
</UserChange>
</Changes>
<html>
<head>
<title>Error</title>
</head>
<body>Error occurred creating change request. Index: 1, Size: 1
Query String=cmd=createChangeRequest&token=xxxxxxxxxxxx3863
</body>
</html>
I works fine without adding parameters,
<Changes>
<Description>test</Description>
<Notes>value</Notes>
<AccountChange>
<Operation>Create</Operation>
<User>XXXXX</User>
<BusinessSource>ABC</BusinessSource>
</AccountChange>
</Changes>
<?xml version="1.0" encoding="UTF-8"?>
<createChangeRequest>
<Request type="fulfillment">
<Id>56789</Id>
<Name>12345</Name>
</Request>
</createChangeRequest>
Any way to pass job level parameters to workflow using webservice call.
A different webservice ADD ACCOUNT TO GROUP with custom parameters works well passing the job level parameters to workflow
<Changes>
<Notes>Request for testing</Notes>
<Parameters>
<Parameter scope="job">
<Name>Add</Name><Value>false</Value>
</Parameter>
<Parameter scope="job">
<Name>Multiple</Name><Value>false</Value>
</Parameter>
</Parameters>
<AccountChange>
<Operation>Add</Operation>
<Account>dummy, user2</Account>
<AccountCollector>XYZ ADC</AccountCollector>
<Group>RSAGroup</Group>
<GroupCollector>XYZ Group ADC</GroupCollector>
</AccountChange></Changes>
<?xml version="1.0" encoding="UTF-8"?>
<createChangeRequest>
<Request type="fulfillment">
<Id>12345</Id>
<Name>67890</Name>
</Request>
</createChangeRequest>
Please assist.
One difference I noticed between the working and non-working scenario is that you are probably adding the Parameters tag in the wrong place. The parameters tag should be under the main Changes tag, but it fails when you add it under the UserChange tag.
If you check the documentation under Admin > WebServices, the example is as follows: