I would like to see this as well.

@RichardS3059 Fair enough that AppColl won't be able to accurately calculate every expiration date. But it could still calculate a default date that will be correct for most patents. Even a human can't calculate the expiration date at issue accurately if the patent later becomes eligible for PTE.

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

Yup, I agree, this is a little task that I do, but I would love it if it were already completed when I received the doc!

This would be so helpful for me. I have no doubt it would assist AppColl beginners to organize the information on reports more easily as well!

Thanks. I've done that.

Thank you for the request Brandon.

The speed with which we implement new features depends on several factors:

The number of customers requesting the feature. Obviously more requests elevates the priority.
The complexity of the feature, particularly if it requires a user interface change. We strive to keep AppColl easy-to-use - keeping the UI simple and uncluttered is a big part of that.
The generality of the request. Is this something all AppColl users would find useful or just a few?
We've recorded your suggestion and we will let you know if and when we have a schedule for implementation.

We very much appreciate you taking the time to send us thoughts about how to improve AppColl. Keep the ideas coming!

Hi Jonah. Thank you for the suggestion. It's a great idea.

The speed with which we implement new features depends on several factors:

The number of customers requesting the feature. Obviously more requests elevates the priority. The complexity of the feature, particularly if it requires a user interface change. We strive to keep AppColl easy-to-use - keeping the UI simple and uncluttered is a big part of that. The generality of the request. Is this something all AppColl users would find useful or just a few?

We've recorded your suggestion and we will let you know if and when we have a schedule for implementation.

We very much appreciate you taking the time to send us thoughts about how to improve AppColl. Keep the ideas coming!

Hi Jonah. Thank you for the suggestion. This is a good one.

The speed with which we implement new features depends on several factors:

The number of customers requesting the feature. Obviously more requests elevates the priority. The complexity of the feature, particularly if it requires a user interface change. We strive to keep AppColl easy-to-use - keeping the UI simple and uncluttered is a big part of that. The generality of the request. Is this something all AppColl users would find useful or just a few?

We've recorded your suggestion and we will let you know if and when we have a schedule for implementation.

We very much appreciate you taking the time to send us thoughts about how to improve AppColl. Keep the ideas coming!

Hi Brandon. Thank you for your suggestion.

The speed with which we implement new features depends on several factors:

The number of customers requesting the feature. Obviously more requests elevates the priority. The complexity of the feature, particularly if it requires a user interface change. We strive to keep AppColl easy-to-use - keeping the UI simple and uncluttered is a big part of that. The generality of the request. Is this something all AppColl users would find useful or just a few?

We've recorded your suggestion and we will let you know if and when we have a schedule for implementation.

We very much appreciate you taking the time to send us thoughts about how to improve AppColl. Keep the ideas coming!