Design

Back Next

Rules and guidelines for JSON files

Consider the following rules and guidelines when you import a JSON file to create a process object:

When you import a JSON file, if there is only one item available in the process object list that you import, the field type is set to

Reference

by default in the Process Object editor.

When you import a JSON file, if a process object doesn't contain any item, no field is created.

When you import a JSON file to create a process object, in addition to the objects defined within the JSON file, a root process object with the file name is also created.

Consider that you have a JSON file named

sampleJson.json

, which contains the JSON payload as shown in the following sample:

{
"address": "India",
"age": 25,
"contact":
	{
	"telephone": 5434344985
	},
"ID": 111,
"name": "",
"test": 
	{
	"contact":
		{
		"mobile": 1267673455
		}
	}
}

After you import the

sampleJson.json

file, three process objects named

ContactType

TestType

, and

SampleJsonType

are created.

The following image shows the process objects that are created after importing the JSON file:

If the JSON file name contains only numeric characters,

RootPO

is prefixed to the process object name.

For example, if the file name is

1234.json

, the process object name would be

RootPO1234

If there are multiple process objects with the same name in a single file, only one process object is created and reused. All the fields are merged into the same process object.

For example, in the above

sampleJson.json

file, there are two objects with the name contact. When you import the JSON file, the

telephone

and

mobile

fields are merged into the

ContactType

process object.

If the process objects with the same name already exist in the selected folder, the following message appears in the log:

[WARNING]: Process object <Process_Object_Name> imported with warning. Resolution: CONFLICT, Status: SUCCESSFUL, Status Code: MigrationSvc_055, StatusMesssage: Reuse existing object

Creating Process Objects from JSON Files

Download Guide

Watch

Comments

Cloud Application Integration Homepage