@BerndN5890 You'd have to remember that the calculated date could be incorrect if a terminal disclaimer was in place. Or if PTE was granted under Hatch Waxman. And, of course, non-payment of maintenance fees. And that's just for US patents. For foreign patents, it's even more complicated.
AppColl should support (and encourage) multifactor authentication. Preferably, you would allow the user to select multiple methods from a list of methods, such as email, SMS message, push notification, TOTP, and digital certificate. That way, if for some reason one method isn't working at login, an alternate method could be used.
I would really like to be able to create an AIA/82A by itself, without the AIA/82B form. You list an "AIA/82 Transmittal For Power of Attorney ..." form in the list of PTO forms that can be created and filled in with data from a matter. The form created is both an AIA/82A and an AIA/82B. For my clients, I have them sign an 82B once, then create an 82A for each application, which is how the forms are designed to work. But now I have to edit the AIA/82 created by AppColl to delete the pages for the 82B every time I create an 82A.
@jonah-soundhound-com I agree, although what I'd really prefer is for the truncation to be eliminated.
Please create a new matter type for TM oppositions. Yes, if someone opposes one of my client's marks, that can fit into a normal TM matter. But if my client is opposing someone else's application, a new matter type would be helpful.
@admin When did this get added? I never realized that docx was doable as a template.
I like the color scheme and am trying it for my own system. The one problem I have with AppColl's implementation is that the text in some columns is washed out, while other columns, it's very readable. 
Any ideas on why or how to avoid that problem?
@joe-appcoll-com Eventually, maybe. But I've not seen anything like a roadmap saying when. As a solo with clients who only work in a small number of countries, I can create my own rules fairly easily. But AppColl would have to spend a lot of resources to cover the world and all of the possible updates that have to be made from time to time. I managed a docketing group for a large firm for a while that used IP Manager (ugh), and the number of updates the vendor made--90% of which probably were of no interest to our clients--was huge.
@jonah-soundhound-com A simpler way to do it would be to just generate a bunch of annual docket entries for the entire lifetime of the patent all at once, just like some systems generate a docket entry for each extension of time that's possible for a response when an office action arrives.
But I hate seeing all of those future entries and having to clear them if they're not needed, so I prefer a more complicated configuration that only generates each docket entry when it's needed. A little careful work up front pays off over time.
Right now, if you use the {Matter.PriorityConnection} you get the country code and application number for the first priority connection, But if you want all of the priority connections, the {Matter.PriorityConnections} gives all of the application numbers, but omits the country codes. The {Matter.PriorityConnectionsFull} and {Matter.PriorityConnectionsVerbose} give the country codes, but include other information that isn't always wanted.
@joe-appcoll-com In my mind, this is by far the greatest weakness of AppColl. Doing it right is a huge undertaking, however.
@RichardS3059 Thinking about this some more, I think this might work. Keep my CN First Annuity task as is but change the CN Pay Annuity task to trigger off completion of the CN First Annuity task instead of setting the filing date. That would avoid the need to close annuity tasks with Not Needed until issuance, I think.
@jonah-soundhound-com I agree. There's no way to do this quite right in AppColl today. What I've done is to create two CN annuity tasks:
CN Pay First Annuity - triggered when Allowance Date gets a value for a CN patent application. The response date is based on the allowance date with an offset of 2 months and 0 days. It's a Hard External Deadline. That date isn't quite correct, because the actual first due date is specified in the notice of grant, but it should be conservative.
CN Pay Annuity - triggered whenever a CN patent application FilingDate field gets any value or whenever a CN Pay Annuity task completes. The response date for this task is based on the official filing date offset by 12M/0D or, if later, the triggering task respond-by date offset by 12M/0D. It's a Hard External Deadline. Until issue, I just close these with Not Needed.
That setup doesn't account for the 6-month grace period and I need to fix that. What I usually do for countries with grace periods is set 3 tasks. The first one is triggered on the normal due date or completion of first one or the third one. The second is triggered by a Missed completion of the 1st one or the third one. The third one is triggered by completion of the second one.
For example, here are my three tasks for paying DE annuities:
DE Pay Annuity first deadline - triggered by either setting a filing date in a DE patent application or by a DE Pay Annuity first deadline task completing with Completed or by a DE Pay Annuity first deadline(2) task completing with Completed. It's an Extendible External task. The response date is set to the matter filing date +12M/0D with a final deadline offset of 18M/0D or if later, the triggering task's respond-by date +12M/0D with a final deadline offset of 18M/0D. Completion states are defined for Completed and Missed, with an auto-close of Missed.
DE Pay Annuity first deadline(2) - triggered by a DE Pay Annuity final deadline task completing with a Completed state. It's an Extendible External Deadline with a response date based on the triggering task's respond-by date +6M/0D final deadline offset 12M/0D.
DE Pay Annuity final deadline - triggered by either the DE Pay Annuity first deadline or DE Pay Annuity first deadline(2) task completed with Missed. It's a Hard External Deadline with a response date of the triggering task's respond-by date +6M/0D
All three DE tasks have the "one the last day of the month" flag set. I have similar sets of three tasks for other countries, with offsets or original triggers based on the national law.
If anyone has a better way of doing this, I'd love to hear it..