Advanced Customization > Business Logic Customization > Customizing Quality Management > Customizing Regulatory Submissions > Regulatory Transmission Delegate Interface > Using the Directory File Drop Transmission Delegate
Using the Directory File Drop Transmission Delegate
The directory File Drop Transmission Delegate writes the regulatory submission payload to a configurable location in an on-premises Windchill system. It does not process inbound acknowledgement messages. The inbound acknowledgement messages are processed through the RegMstr domain using the ProcessAcknowledgement action. This delegate uses its own log file located at <Windchill>/logs/regmstr.
To configure the directory File Drop Transmission Delegate, complete the following steps:
1. Customize the transmit functionality. For detailed steps, see Regulatory Transmission Delegate Interface. The following example shows an xconfiguration entry for a FileDropTransmissionDelegate delegate.
<Service name="com.ptc.qualitymanagement.regmstr.impl.RegulatoryTransmissionDelegateInterface">
<Option requestor="null" serviceClass="com.ptc.qualitymanagement.regmstr.impl.FileDropTransmissionDelegate "
selector="default" cardinality="duplicate"/>
</Service>
2. Configure a directory to be used by Windchill for storing regulatory submission payloads. Set the property regmstr.filedrop.filebased.path in a custom directory. The directory should have write permissions. Set this property using the site.xconf file as shown in the following example:
<Property name="regmstr.filedrop.filebased.path"
overridable="true"
targetFile="codebase/wt.properties"
value="<path-name>"/>
After the configuration is complete, successful transmission writes the regulatory submission payload file to the pre-configured location with the following structure:
<Configured filebased path>/outbox/<internal type name>/<Regulatory Submission Number>_PAYLOAD
Each type of regulatory submission writes the regulatory submission payload file to a separate directory.
Was this helpful?