Updating Attributes of Standard Control Characteristic
To update the attributes of an existing Standard Control Characteristic (CC) object or its subtype, you must first check out the object.
If you perform Undo Checkout on the Standard CC object, the changes are rolled back. When you update the Standard CC object, the version of the Standard CC object will be iterated upon checking it in. You can specify the OID of any iteration/revision/view of the Standard CC object or its subtype. You can update modeled and all other types of attributes, including IBAs such as enumerated lists.
To update an attribute, you must specify the value with its valid internal name. If a constraint is applied to the attribute, you must specify the internal name of the value specified in the constraint.
If you want to clear the value of an attribute, you can specify its value as null in the request.
If you do not specify an attribute in the request body, then the attribute retains its existing value.
|
|
You cannot modify the following attributes: Name, Number, Category.
|
Example: Updating Attributes of a Standard CC Object
This example shows you how to update the attributes of a Standard CC object. Use the following PATCH URI with the request body.
URI
PATCH /Windchill/servlet/odata/MfgProcMgmt/StandardCCs('OR:com.ptc.windchill.mpml.pmi.MPMStandardCC:196272')
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"Description": "Description",
"NominalValue": "004",
"LowerLimit": "001",
"UpperLimit": "005",
"LongDescription": "LongDescription"
}
Example: Updating Attributes of Multiple Standard Control Characteristics
This example shows you how to update the attributes of two Standard CC objects specified in the request body. Use the following POST URI with the request body.
URI
POST /Windchill/servlet/odata/MfgProcMgmt/UpdateStandardCCs
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"StandardCCs": [
{
"Description": "Description1",
"ID": "OR:com.ptc.windchill.mpml.pmi.MPMStandardCC:196272",
"NominalValue": "005",
"LowerLimit": "001",
"UpperLimit": "0010",
"LongDescription": "LongDescription1"
},
{
"Description": "Description2",
"ID": "OR:com.ptc.windchill.mpml.pmi.MPMStandardCC:196286",
"NominalValue": "003",
"LowerLimit": "001",
"UpperLimit": "005",
"LongDescription": "LongDescription2"
}
]
}
Updating Standard Control Characteristics in Context of Change
This example shows you how to update two Standard Control Characteristics in the context of Change. In this example, one Change Task object is specified for each Standard Control Characteristic object in the request body. Use the following POST URI with the request body.
URI
POST /Windchill/servlet/odata/MfgProcMgmt/UpdateStandardCCs
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"StandardCCs": [
{
"ID": "OR:com.ptc.windchill.mpml.pmi.MPMStandardCC:196272",
"Description": "Description1",
"ResultedByObjects@odata.bind": [
"ChangeTasks('VR:wt.change2.WTChangeActivity2:205227')"
]
},
{
"ID": "OR:com.ptc.windchill.mpml.pmi.MPMStandardCC:196286",
"Description": "Description2",
"ResultedByObjects@odata.bind": [
"ChangeTasks('VR:wt.change2.WTChangeActivity2:205227')"
]
}
]
}
The request updates and adds the modified Standard Control Characteristic object as a Resultant object to the specified Change object.