Creating Process Objects Manually

1In Application Integration, click New > Process Object > Process Object > Create.
The process object editor appears.
The following image shows the process object editor:

2Specify a name for the process object.
The name must start with a letter, and can contain only alphanumeric characters, multibyte characters, underscore (_), and hyphens (-). The name must not exceed 120 characters.
3Click Browse to specify a location to save the process object.
4Optionally, enter a description for the process object.
5To add a field to the process object, perform the following steps:
1. aEnter a name for the field.
The name must start with a letter, and can contain only alphanumeric characters and hyphens (-).
2. bOptionally, enter a label for the field.
3. cOptionally, from the Type list, select an appropriate data type for the field. Default is Text.
To reference another process object, select the type as Reference.
4. dClick Add Field to add the field to the process object.
• ▪ If you selected the type as Object List or Reference, browse and select the process object to be referenced. You can also enter the process object name in the Find box to search for a process object.
Note: If you change the name of a referenced process object, you must also save the parent process object. For example, you can make a minor change to the description of the parent process object and click Save.
You can click View Referenced Process Object to view the referenced process object from the process object editor itself. The referenced process object opens on a new tab on the left navigation bar in a read-only mode.
• ▪ If you selected the type as Picklist or Multi-Select Picklist, enter one or more options separated by commas.
5. eTo set the type as a list of simple types for the text, integer, number, check box, date, date time, or time data types, select the row that contains the type, and then select the This is a list check box.
Note: The list of simple types feature in process object is in technical preview. Technical preview functionality is supported but is unwarranted and is not production-ready. Informatica recommends that you use in non-production environments only. Informatica intends to include the preview functionality in an upcoming GA release for production use, but might choose not to in accordance with changing market or technical circumstances. For more information, contact Informatica Global Customer Support.
6. fTo configure additional fields for the text, date, date time, time, number, or integer data types, expand the Name field and enter the additional fields as follows:
• ▪ Length and format of the text for the text data type
• ▪ Date range for the date data type
• ▪ Date time range for the date time data type
• ▪ Time range for the time data type
• ▪ Minimum and maximum values for the number data type
• ▪ Minimum and maximum values for the integer data type
7. gTo set the field as a required field, select Required.
A required field must be included in the request payload. It can contain a value, be empty, or be null.
8. hIf you do not want the field to accept null values, clear the Nullable check box. By default, the check box is selected.
6Configure the required fields for the process object.
The following image shows an Employee process object with three fields namely, ID, Name, and Address:

To order a field, use the arrow icons against the row that contains the field to move up or down.
To delete a field, hover over the row that contains the field and click the Delete icon.
7 To edit the field values, click anywhere on the row that contains the field.
All the fields in the row become editable.
8Click Save to save the process object.

Rules and Guidelines for using Process Objects in a Process

• •If you use a process object with required fields as the input for an Application Integration process, you must ensure that the required fields are present in the request payload. Otherwise, when you run the process, you receive an error for the missing fields.
For example, in a process object, you have set the ID field as required, but the field is not present in the request payload as shown in the following sample:
<root xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<Employee>
<Name xsi:nil=”true”></Name>
<Address xsi:nil=”true”></Address>
</Employee>
</root>

After you run the process, you will receive the following error:
<root>
<code>400</code>
<details>
<missing>[ID]</missing>
</details>
<message>The parameter validation failed</message>
</root>

• •If you set a process object field as Nullable, it can contain a valid value or be null. Non-nullable fields cannot be set as null.
In the JSON and XML formats, null values in a process object field that is used as the input for an Application Integration process are handled differently.
In the JSON format, you can specify null values directly as a field value.
For example, {"Name":null}
XML does not support null values. Therefore, in the XML format, if a field is set as Nullable and you want to pass null values, you must set the xsi:nil attribute as "true" in the field element and include <xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> in the root element as shown in the following sample:
<root xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<Employee>
<ID>1234</ID>
<Name xsi:nil=”true”></Name>
<Address xsi:nil=”true”></Address>
</Employee>
</root>