Assigning Security Labels for a Process Plan
|
|
You can specify the optional attribute, LongDescription, in the request body when creating a process plan or standard procedure using POST /ProcessPlans. To create a standard procedure, specify the value of the Standard attribute as true in the request body.
You can optionally create a process plan or standard procedure in the context of change (change notice).
|
You can assign multiple single-valued or multi-valued Security Labels when creating a process plan using POST /ProcessPlans.
Example: Assigning Single-valued Security Labels
This example shows you how to assign multiple single-valued security labels for a Process Plan. Use the following POST URI with the request body.
URI
POST /Windchill/servlet/odata/MfgProcMgmt/ProcessPlans
Request Header
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"Name": "Process Plan 01",
"Standard": false,
"LongDescription": "This is a long description.",
"OccurrenceLevel": false,
"ProcessPlanQuantity": 0,
"Unit": "ea",
"Context@odata.bind": "Containers('OR:wt.pdmlink.PDMLinkProduct:113009')",
"EXPORTCONTROL": "LNC",
"EXPORTCONTROL1": "LNC1"
}
Example: Assigning Multi-valued Security Labels
This example shows you how to assign multiple multi-valued security labels for a Process Plan. Use the following POST URI with the request body.
URI
POST /Windchill/servlet/odata/MfgProcMgmt/ProcessPlans
Request Header
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"Name": "Process Plan 02",
"Standard": false,
"LongDescription": "This is a long description.",
"OccurrenceLevel": false,
"ProcessPlanQuantity": 0,
"Unit": "ea",
"Context@odata.bind": "Containers('OR:wt.pdmlink.PDMLinkProduct:113009')",
"EXPORTCONTROL": "LNC,CUSTOM",
"EXPORTCONTROL1": "LNC1,CUSTOM1"
}