You can define process object fields as required and nullable in the WSDL, Swagger JSON or YAML, and OpenAPI 3.0 JSON or YAML files before you import the files to generate a process object.
In a WSDL file, to define a field as nullable, set the nillable attribute to "true" in the field element. If you do not specify the nillable attribute, the field is set to not nullable by default. If you do not want to set a field as required, set the minOccurs attribute to "0" in the field element. If you do not specify the minOccurs attribute, the field is considered as required by default.
For example, consider a WSDL file that has a schema named ProcessObjectReq. The schema is of a complex type and contains two elements called as Name and ID. To set the ID field as nullable and not required, set the nillable attribute to "true" and the minOccurs attribute to "0" as shown in the following sample:
When you import the WSDL file, the nullable and required field elements defined in the WSDL file are propagated to the process object as shown in the following image:
Similarly, you can set the required and nullable field elements in the Swagger JSON file and create a process object as shown in the following sample:
If you use a process object with nullable fields in a process, and generate the Swagger file for the process, the generated Swagger file might not contain the x-nullable field defined in the process object. The field is set to not nullable by default. Therefore, Informatica recommends that you use a WSDL file or OpenAPI 3.0 file to preserve the nullable field values.
When you use this process object in a process, the fields marked as required and nullable use the same restrictions in the generated WSDL file, Swagger file, and OpenAPI 3.0 file.
When you import the JSON file and create a process object, all the fields are marked as nullable and not required by default.
