Not yet. But it's high up on our radar.

@mike_appcoll nice

Thanks. This is a great addition.

Thanks! That is great.

@ChristianS9906 That takes care of one part. The UI is always a large part of any project. We also have to notify account admins when sync changes have been made so that they can review the changes. Other side effects that I haven't predicted have to be considered as well.

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

Hi George,

Thank you for your suggestion. We will pass this on to engineering for future consideration.

@RichardS3059 I second IP Manager (ugh). I too managed a medium sized law firm docketing group and while the updates were nice, the firm's portfolio was made up of a mixture of foreign and US. As you said, the effort to keep those rules current if quite a commitment. One thing we appreciate about AppColl is the affordability. I think by not having foreign rules certainly helps with keeping costs low.

@BrandonK6644 said in .docx Form Letter templates:

I'd also love to be able to automatically generate a template within a task when the task is generated. Is that possible?

+1 for this request - automatically adding documents to tasks would be a great time saver.

Hi @TarC6989 we don't currently have a way to do this. However, we will pass this on to our engineers for future consideration. Thank you.

I am also looking for a way to automatically attach files associated with tasks (e.g., responses to office actions) when working with client-reporting templates

@AnnM9156 thanks for your input. We use an arbitrary attorney reference number format which does not include a country code.

The transient task solution wouldn't really do much--just email the recipients once when the note is updated. Fast forward a month later, and nobody will remember that they received that email, and might miss whatever is important.

Your pop-up slap-to-the-face approach would be much more effective at getting a user's attention.

@mike_appcoll Thank you for doing Learning Series tutorials on often overlooked features. But please also always consider why often overlooked features are often overlooked. Perhaps some eventual user interface tweaks will result in fewer features being often overlooked.

@RichardS3059 - what you really want is {Matter.Client.ShortName} for the client code and {Matter.Client.Name} for the full name. We hope this helps.

Thank you for the suggestion. We should be able to remove the prefix from the sort. However, sorting by last name would affect all customers who have come to expect it with first name first.

@MarkW5689 The new form field explorer control should help with most form field questions. It is available on the same pane as the history and discussion tabs.

@ChristianS9906 We have elevated the priority and will discuss at our next engineering projects review.

@AppCollS2261 That's great--I would, however, make sure that:

a) The update only happens to tasks that have the same role as the task owner (for example, if you change the attorney for several matters, you'd only want to update the tasks for those matters that had the previous attorney as the owner--you wouldn't want to make the new attorney, for example, the owner of tasks owned by the paralegals for the matter).

b) The update only happens to "open" tasks--the "owner" of closed tasks is a historical record of which person handled that closed task. It shouldn't be changed (or, at the least, make it an option that you have to opt into in order to bulk-update the owner of closed-out tasks).

Looking forward to this.

Best,
Christian

@support_appcoll Pretty good solution!