UA SOAP UI Optional Fields

[rrawson]

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

[klasen]

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

[klasen]

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

[rrawson]

Thank you that could be handy