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.

While the Connections field lets me see the priority application(s) for the current application, including information on child applications would be really nice. Yes, I can go into Patent Center (for US applications) and use the Continuity tab to get that, but being able to click on a link to a child application in AppColl would be quite useful.

The feature of automatically generating a billing item when the Task Status value changes should be enhanced by making the triggering status value a drop-down using the configured completion states instead of having to type in a value.

@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.

@joe-appcoll-com In my mind, this is by far the greatest weakness of AppColl. Doing it right is a huge undertaking, however.

@SadiqA2304 I'd rather not add yet another field. First Name and Nickname aren't the only fields that could use something like this. For example Filing Date and Official Filing Date. What I'd really prefer is some kind of syntax that allows generally indicating "use field X if it's not null, but use field Y if field X is null." Perhaps something like:

            {{Matter.ClientContact.Nickname},{Matter.ClientContact.FirstName}}

I'm not pushing that syntax. It was just the first thing that came to mind. Even more powerful would be a more generalized IF syntax.

What I end up doing now is filling in Nickname with the first name all the time, and just using Nickname all the time.

As the number of tasks continues to grow, we need to be able to filter the list of task types in addition to just searching for the next task type that contains a word. While I would prefer filtering based on any of several task fields, even filtering the display to just task types that contain a filter word in the TaskType field would be a big help.

For example, all of my country-specific tasks have a task type that starts with the two-letter country code. Being able to filter the tasks list for, say, only tasktypes that start with CA would be a useful improvement.

Mind you, I would also love for you to add a CountryCode field to tasks (with the default being "All countries") and allow me to filter on that, too.

From time to time, I need to send an informative email to a group or all of my active clients. I would really like to generate that email by selecting the relevant client contacts, then have AppColl generate the email, either as separate emails with them as To:, or as a group email, with each of them in the Bcc: line.

@jonah-soundhound-com I agree, although what I'd really prefer is for the truncation to be eliminated.

@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.

I created two user fields, one for first use in commerce and one for first use anywhere. I wouldn't try to overload priority date or some other pre-existing date with first use information.

Of course, it would be nice if AppColl had standard fields for these dates.

As the number of tasks continues to grow, we need to be able to filter the list of task types in addition to just searching for the next task type that contains a word. While I would prefer filtering based on any of several task fields, even filtering the display to just task types that contain a filter word in the TaskType field would be a big help.

For example, all of my country-specific tasks have a task type that starts with the two-letter country code. Being able to filter the tasks list for, say, only tasktypes that start with CA would be a useful improvement.

Mind you, I would also love for you to add a CountryCode field to tasks (with the default being "All countries") and allow me to filter on that, too.

@TPLA3794 I did create a few custom tasks. Because my practice is small (I'm semi-retired), I only created tasks that met my immediate needs rather than attempt to be fully general. But I'd be happy to share them with you, of course with the understanding that I take no responsibility for how you use them or for any errors that might be in them.

Drop me an email at richard@schafer-ip.com and I'll try to figure out a good way to share them.

@SadiqA2304 That certainly seems odd and I haven't seen that problem in my account.

@KristaJ3145 Don't be too shy about changing standard tasks to fit your needs. I've done it a lot without any problems.

I can think of a few ways to do this.

1. Create a user field that indicates annuities are paid by the client as a Yes/No field, such as TaxPaidByClient. Then update the triggers for the annuity tasks to include a criterion that the TaxPaidByClient does not contain Yes. You could do it with the criteria that the field contains No, but then you'd have to set that user field in every matter where you pay the annuities. Which is best may depend on the ratio of client pays vs. attorney pays.

2. Add a tag to the Contact entry for the client that indicates Client pays annuities. Then add a trigger criterion that says the tag does not contain that indication to the trigger for generating the annuity task.

3. Put a keyword in any matter where the annuities are to be paid by the client. Then add a trigger criterion that that says the keyword field for the matter doesn't contain that keyword.

The feature of automatically generating a billing item when the Task Status value changes should be enhanced by making the triggering status value a drop-down using the configured completion states instead of having to type in a value.

One of the great weaknesses of AppColl is the lack of tasks related to non-US prosecution. I'm trying to develop a fleet of tasks for Madrid applications for use with my clients. Is anyone willing to share how they're doing it?

@JessamyN2308 Here's a way I think might work. Create a user checkbox field named something like USNonpublicationRequest. Check the box in the US matter if true. When you create a non-US app where a non-pub request was filed, check that box i the foreign matter, too. Then create a "Request non-pub recission" task that is triggered by the filing date field in the non-US app gets any value while that checkbox is checked. Make sure that the task setup checks the "only create in any related US app" box. That should generate the task in the relevant US app.

Alternatively, you could skip the checkbox in the foreign app, and just auto-generate the task in the related US app any time you file a foreign app, but then you close the US task with not needed.

It's not ideal, but it might be better than nothing. To do more would require AppColl to implement a way for one task to cause the creation of a task in another matter, depending on a condition in the other matter.

While the Connections field lets me see the priority application(s) for the current application, including information on child applications would be really nice. Yes, I can go into Patent Center (for US applications) and use the Continuity tab to get that, but being able to click on a link to a child application in AppColl would be quite useful.

@GeorgeJ4336 At first glance, the right answer would seem to be don't change commas to semicolons except when parsing email address fields. There's no reason to change commas to semicolons elsewhere. But your template would fail even if they only did that and you had a BillTo.EmailNoCC value of "jack@xxx.com, jill@xxx.com"; that would produce an invalid email address:

Nicole Sxxxx Xsssss(USA), Inc. <jack@xxx.com; jill@xxx.com>