EXAMPLE (WOOD4.JSON)

Wood4.json is a bigger example and contains information from two object domains, “locations” and “processes”. One new concept that is introduced is relations.

{
	"type": "humanResource",
	"id": "oid4004",
	"originId": "oid4004",
	"originSource": "EXCEL",
	"attributes": {
		"name": "Operator 2",
		"abbreviation": "O2"
	},
	"relations": [
		{
			"operation": "sync",
			"type": "processExecution",
			"list": [
				{
					"id": "mupp3",
					"originId": "line-177-child-ref-99",
					"toId": "processes:oid3988"
				}
			]
		}
	]
},

“relations”

Relations follow the same format as objects and children but uses “toId” instead of “refId” to reference the “other end” of the relation.  Relations often points to PLM objects that resides in another domain. In these cases, the domain is written before the id and separated by a “:” (colon).