@GeorgeJ4336
This happens for us frequently as well. Our work around is to forward the email to the appropriate AppColl email address (ex. xxxxm123@intake.appcoll.com). I generally just put "for the file" in the email message, but this way it is saved to the matter, the documents are saved separately AND the message appears in the conversation tab.

@jonah-soundhound-com I use Patent Center. I haven't used EFS-Web for months. The missing fonts issue I mentioned above relates to Patent Center. I did not try uploading the IDS via EFS-Web. I agree, it does not make sense to spend engineering effort to help with problems in a system that is planned for deprecation. However, Patent Center is not planned for deprecation.

Thank you for the feedback.

@JohnG8374

This is a significant project that we have formally added to our project list. This may take quite a bit of time.

Thanks.

@gregg_appcoll Perfect! Thanks.

I can now automatically address e-mail correspondence to examiners, such as to request interviews. In the "To" field, I put:

{Matter.Examiner} <{Matter.Examiner(FirstWord)}.{Matter.Examiner(LastWord ToTitleCase)}@USPTO.gov>

and in the salutation, I put:

Dear Examiner {Matter.Examiner(LastWord ToTitleCase)}:

-George

@AlexandreP4784 Thank you for the input. We will pass this on to engineering for their consideration.

@RichardS3059 I have a follow-up question about this topic. Is there a way for the ReferenceDate of the "Request non-pub rescission" task to be the filing date of the non-US application? The task I created uses the US application filing date instead of the non-US application filing date as the reference date.
74dcf24e-3975-4f6c-ab8d-0e245fbcfffc-image.png

@RichardT8744

Hi Richard - setting up periodic reports is the way to go for exporting data. This can be sent to your SFTP server, S3 buckets or traditional email.

You can also send data to our SFTP server, which we can upload into your account. You would need to reach out if this route is something you're considering.

We hope this helps.

@RichardS3059 Do you have form letters attached to automatically generated tasks that are triggered when an eOfficeAction is received?

@BrandonK6644

So sorry for the delay. We have increased the priority on this one. We will announce when this has been done.

We have upped the priority of this. In the meantime, you can add a Fee offset billing item and enter the dollar amount you are discounting. We hope this helps.

@ChristianS9906 agree that is a good alternative

@CatherineVH9536-0

Hi Catherine. It looks like the new SB08a form resets the numbering for each category. And not a continuous number all the way through each category. We wouldn't be able to change this since the form forces the cite number. We hope this helps.

@JonahP1621 I'd like to see some built-in color schemes to choose from with text chosen to display well on the background chosen. Or at least the ability to change both background and text colors.

@jonah-soundhound-com And based on my experience, I can guarantee that foreign associates will do that.

@BerndN5890 Cool!

@AnnM9156 That is correct--it is just a field that records data regarding the application. You can, however, customize triggering for tasks based on the value in that field. I took a look at our docket, and our 3-month non-final OA response deadline has two flavors--one that is called "Respond to Non-Final Office Action - 3-month deadline" and the other that is called "Respond to Non-Final Office Action - 3-month deadline (Track One)." The "track one" version triggers when a non-final OA is received in a case that has Track One status specified, and the non-track one version triggers when a non-final OA is received in a case that does not have Track One status specified. Our 4-month OA deadline triggers when either of the 3-month deadlines closes as "missed."

@KimG5166 Does the "Same as above" residency checkbox solve your issue for inventors? It should allow you to put in a secondary residency address. fa0fabb3-7d76-4233-a4d5-4f49da803261-image.png

@SadiqA2304 I thought of that but was concerned that it might muck with triggering conditions if the task name was later changed to remove the "under development" text.

It would also mean that normal users would still see it and the under development tasks would still clutter up the interface.

Hi there. Thank you for the suggestion. We will certainly look into this.