• Developing Attribute Populators—To populate attributes for a new and revised regulatory submission.

• Developing an Alternate Editing User Interface—To provide an alternate launch URL for the purpose of editing a regulatory submission.

• Developing a Report—To generate a human-readable regulatory submission report.

• Developing a Clean Transmission Content Processor—To clean up the appropriate regulatory content and acknowledgement messages in preparation for an electronic submission or resubmission.

• Developing a Payload—To generate a submission payload.

• Developing a Submission Processor—To transmit the regulatory submission payload to the regulatory agency using the configured communication method, and perform any additional processing necessary as a result of the transmission.

• Developing an Acknowledgement Interpreter—To process an acknowledgement with the regulatory agency specific processing method.

• Developing a Completion Processor—To perform any necessary final processing of the regulatory submission after it has been successfully submitted to the regulatory agency.

• Developing an Expiration Processor—To perform any necessary processing of the regulatory submission after it has expired.

• Developing a Cancellation Processor—To perform any necessary processing of the regulatory submission after it is cancelled.

• Using the Simulate Transmission Delegate—To prepare a test transmission process during development.

• Using the Directory File Drop Transmission Delegate—To store the payloads on your Windchill system.

• Using the Azure File Drop Transmission Delegate—To store the payloads on Azure Blob Storage.