Capturing the Regulatory Content for an Existing Revisable Regulatory Submission

To capture the regulatory content for an existing revisable regulatory submission, the regulatory submission must be the latest version.

For every request sent after the first request, the revisable regulatory submission must be the latest checked-out version to capture the regulatory content of a different category.

To add regulatory content to an existing revisable regulatory submission, you must have Modify or Modify Content permissions to the regulatory submission.

The following example shows you how to capture the regulatory content for an existing revisable regulatory submission.

To capture the regulatory content, the specified category must:

• Be a supported or configured category of the regulatory content.

• Not already exist as regulatory content on the revisable regulatory submission.

Use the following PUT URI with the request headers.

PUT /Windchill/servlet/odata/RegMstr/RegSubmission2('OR:com.ptc.qualitymanagement.regmstr.RegSubmission2:256705')/RegulatoryContent

Accept:*/*
Content-Type: multipart/form-data
CSRF_NONCE: <Use the value from Fetch NONCE example>
PTC-ContentCategory: ACKNOWLEDGEMENT1

The request payload is the same as that of the Stage 2–URI in the three-stage upload process. For details, see Three-Stage Upload of Attachments to a Regulatory Submission.

The request adds the regulatory content of ACKNOWLEDGEMENT1 category.

The response returns the 201 status code and details of the captured regulatory content for the regulatory submission.

To replace the regulatory content for an existing revisable regulatory submission, you must first delete the regulatory content and then add the regulatory content with the PUT request.

You can also capture the regulatory content using the following request body for the Stage-3 POST URI in the three-stage upload process.

POST /Windchill/servlet/odata/RegMstr/RegSubmission2('OR:com.ptc.qualitymanagement.regmstr.RegSubmission2:256705')/PTC.RegMstr.UploadStage3Action

Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>

{
"ContentInfo": [
{
"StreamId": 12601,
"FileSize": 95305,
"EncodedInfo": "76035%3A2%3A150329%3A76035",
"MimeType": "img/png",
"Role": "REGULATORY_CONTENT",
"FileName": "filename"
}
]
}