We do not use the web-based forms because you have to re-type information that already exists in our docketing system. Re-typing is a sure way to cause errors. Instead, I have programmed our docketing system to generate .xml documents that can be imported into an ADS which fills a good portion of the information. We also generate .xml that we use as a template for EPAS recordations. It would be great if the web-based ...more »
The last update to the Application Data Sheet (aia/0014) broke the XML import/export functionality. Please bring that back.
There needs to be a better way to get all XML data for all applications associated with a customer number. Currently outgoing correspondence xml data, customer number xml data, and app-specific xml data all have to be downloaded in order to get all relevant data for applications associated with a customer number. This data is used to auto-populate an on-the-fly docket program, whereby custom rules are applied to generate ...more »
If you download the XML data for a number of applications at once (e.g. for everything under a given customer number), you get significantly less data for each application than if you pulled the XML data for each application separately. Let there be an option to pull the complete XML data for multiple applications at once, please (and preferably all applications at once).
In PAIR, the ability to download XML data for a customer number is useful, but two suggestions: 1) Have an option to get data from all your customer numbers at once; and 2) include in the XML an indicator of current status. It already lets you filter on application status ('all', 'new', 'pending', 'issued', 'abandoned', 'other') - simply include this status tag in the download.