@SadiqA2304 Thanks. We will get this taken care of.

@BruceY9495 UPDATE: Our account has EBD data for about 40 matters, but that's it. I guess it is still updating/being calculated.

Our account had the EBD data in it as of this morning, so I think they have added it.

Thanks, Gregg!

@MelissaT3398

Hi Melissa,

We added the ability to use the AttorneyRef as part of the email address for sending correspondence into a matter.

@mike_appcoll nice

Hi Bruce and Christian - The EarliestBenefitDateEdited was not meant to be included in task triggers. This will removed. It's an internal field we use to know whether an EBD has been manually edited by the user.

If another connection is added to a matter, we will automatically recalc the EBD, for the current matter as well as each matter in the family (assuming a change is needed). I hope this helps.

Thanks. This is a great addition.

@gregg_appcoll Thanks, Greg, however I would still find it very helpful to have a syntax for an alternate field, when a first field is blank. As I previously noted, I have several situations where such a syntax would be helpful:

(a) a client-specific USPTO customer number (if the client has one), or the firm's customer number (if the client doesn't have one) (Some of my clients want me to use their customer number, rather than mine. I have templates for responses to Office Actions, etc. that include a customer number in the document headers)

(b) a client-specific USPTO deposit account number (if the client has one), or the firm's deposit account number (if the client doesn't have one). (My template responses include boilerplate language authorizing charges to a deposit account, in case of a missed extension of time.)

(c) actual filing date or official filing date or priority date, depending on what is available. (For example, when calculating due dates for foreign applications.)

Thanks,
George

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.

@ChristianS9906 Great. Thanks for the feedback.

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

@ChristianS9906 Whereas AppColl already implemented the change you requested, I'm reluctant to request they change it back. I don't know to what extent others have strong or weak feelings about e-mail addresses with or without aliases (display names). You and I have stated our preference and reasons. It would be interesting to see if anyone else expresses an opinion.

Hi Sadiq, no progress yet, but we will review priorities with engineering. Thanks.

@gregg_appcoll Thanks, looks like it's working. For Examiner names, I'm doing

{Matter.Examiner(ToTitleCase, AddPeriodToSingleCharacter)}

@BrandonK6644 We worked in depth with our developers on this today. Unfortunately, there is not a way to make this work within the current reporting capabilities of AppColl.

Apologies for the delay.

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

@joe_appcoll Nice, thanks

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