Regulatory Submission Processor Interface
The Regulatory Submission Processor Interface is an interface that provides the ability to customize the behavior of regulatory submissions and implement specific formats for the regulatory agencies. For example, you can customize the attributes while creating or revising regulatory submissions. You can also customize regulatory submissions to open the default or an alternate editing user interface.
Scope, Applicability, or Assumptions
Assumes you have general knowledge about Java classes and concepts such as class extension
Assumes you have general knowledge about the xconf mechanism to register service classes
Prerequisites
To apply this best practice you need to have an understanding of the following:
Java class extension
Xconfmanager
Solution Elements
The description of the various solution elements is given in the table below.
Element
Type
Description
com.ptc.qualitymanagement.regmstr.impl.SimpleRegulatorySubmissionProcessor
Java Class
Out-of-the-box processor interface that is registered for a non-revisable regulatory submission.
com.ptc.qualitymanagement.regmstr.impl.AERSubmissionProcessor
Java Class
Out-of-the-box processor interface that is registered for an Adverse Event Regulatory Submission.
com.ptc.qualitymanagement.regmstr.impl.ERSubmissionProcessor
Java Class
Out-of-the-box processor interface that is registered for an Establishment Registration Submission.
com.ptc.qualitymanagement.regmstr.impl.RPSSubmissionProcessor
Java Class
Out-of-the-box processor interface that is registered for a Regulatory Product Submission.
com.ptc.qualitymanagement.regmstr.impl.UDISubmissionProcessor
Java Class
Out-of-the-box processor interface that is registered for a Unique Device Identifier Regulatory Submission.
Default Behavior
When searching for a regulatory submission processor, Windchill searches the Type tree until a processor is found. For example, if a subtype of Adverse Event Regulatory Submission does not have a processor that is registered using xconf, the AERSubmissionProcessor is used.
Creating xconf Entries
To register custom populators relative to specific regulatory submission types and subtypes, create entries in a custom service.properties.xconf file.
An example of an xconf entry to register against a non-revisable regulatory submission subtype is given below:
<Service name="com.ptc.qualitymanagement.regmstr.impl.RegulatorySubmissionProcessorInterface ">
<Option
requestor="null"
serviceClass="com.ptc.qualitymanagement.regmstr.impl.CustomSimpleRegulatorySubmissionProcessor"
selector="com.ptc.qualitymanagement.regmstr.RegulatorySubmission "
cardinality="duplicate"
/>
</Service>
An example of an xconf entry to register against a revisable regulatory submission subtype is given below:
<Service name="com.ptc.qualitymanagement.regmstr.impl.RegulatorySubmissionProcessorInterface ">
<Option
requestor="null"
serviceClass="com.ptc.qualitymanagement.regmstr.impl.CustomRevisableRegulatorySubmissionProcessor "
selector="com.ptc.qualitymanagement.regmstr.RegSubmission2"
cardinality="duplicate"
/>
</Service>
An example of an xconf entry to register against a non-revisable regulatory submission subtype is given below:
<Service name=" com.ptc.qualitymanagement.regmstr.impl.RegulatorySubmissionProcessorInterface ">
<Option
requestor="null"
serviceClass="com.ptc.qualitymanagement.regmstr.impl.CustomSimpleRegulatorySubmissionProcessor"
selector="com.ptc.qualitymanagement.regmstr.RegulatorySubmission|org.rnd.CustomSimpleRegulatorySubmission "
cardinality="duplicate"
/>
</Service>
An example of an xconf entry to register against a revisable regulatory submission subtype is given below.
<Service name=" com.ptc.qualitymanagement.regmstr.impl.RegulatorySubmissionProcessorInterface ">
<Option
requestor="null"
serviceClass="com.ptc.qualitymanagement.regmstr.impl.CustomRevisableRegulatorySubmissionProcessor "
selector="com.ptc.qualitymanagement.regmstr.RegSubmission2|org.rnd.CustomRegSubmission2"
cardinality="duplicate"
/>
</Service>
* 
If a service class does not exist for a subtype, the parent types of the subtype are checked until a service class is found. If a service class is not found, a trace log entry reports on the class and type with no service class defined. Turn on TRACE logging for com.ptc.qualitymanagement.qms.util.helper.QMSServiceClassHelper to display the log entry.
The following sections describe the areas of customization for regulatory submissions.
Was this helpful?