rrawson Honored Contributor.
Honored Contributor.
466 views

UA SOAP UI Optional Fields

Question: I understand that the form part and the SOAP parts of the UA are separate and distinct. We can do things in the SOAP API that would be prevented in the forms. So we can have fields which are required or optional in forms and submit a workflow without every field populated.

So now I want to have the same thing directly via SOAP. I don't want to have to specify each and every field in the form when I don't want to put a value there. I know I can specify each one and put a blank there, but my question is whether there is a magic attribute of some element, or a particular different API call, which loosens up how the SOAP messages are processed and permits the submission of a start workflow without specifying every single field from the PRD form?

Thanks
Rob
Labels (1)
0 Likes
3 Replies
Micro Focus Expert
Micro Focus Expert

Re: UA SOAP UI Optional Fields

On 2018-05-04 03:24, rrawson wrote:
>
> Question: I understand that the form part and the SOAP parts of the UA
> are separate and distinct. We can do things in the SOAP API that would
> be prevented in the forms. So we can have fields which are required or
> optional in forms and submit a workflow without every field populated.
>
> So now I want to have the same thing directly via SOAP. I don't want to
> have to specify each and every field in the form when I don't want to
> put a value there. I know I can specify each one and put a blank there,
> but my question is whether there is a magic attribute of some element,
> or a particular different API call, which loosens up how the SOAP
> messages are processed and permits the submission of a start workflow
> without specifying every single field from the PRD form?


If you start a workflow via SOAP, you need to include an element for
every field that has a post activity mapping for the "Start" activity.


--
Norbert
--
Norbert
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: UA SOAP UI Optional Fields

On 2018-05-04 10:49, Norbert Klasen wrote:
> On 2018-05-04 03:24, rrawson wrote:
>>
>> Question: I understand that the form part and the SOAP parts of the UA
>> are separate and distinct. We can do things in the SOAP API that would
>> be prevented in the forms. So we can have fields which are required or
>> optional in forms and submit a workflow without every field populated.
>>
>> So now I want to have the same thing directly via SOAP. I don't want to
>> have to specify each and every field in the form when I don't want to
>> put a value there. I know I can specify each one and put a blank there,
>> but my question is whether there is a magic attribute of some element,
>> or a particular different API call, which loosens up how the SOAP
>> messages are processed and permits the submission of a start workflow
>> without specifying every single field from the PRD form?

>
> If you start a workflow via SOAP, you need to include an element for
> every field that has a post activity mapping for the "Start" activity.


You can get the requried DataItems and their default values with a call
to getAllProvisioningRequests.

See the example at
https://www.netiq.com/documentation/identity-manager-47/identity_apps_admin/data/b94o0oy.html#b956yi0

--
Norbert
--
Norbert
0 Likes
rrawson Honored Contributor.
Honored Contributor.

Re: UA SOAP UI Optional Fields

Thank you that could be handy
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.