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

Thank you so much 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!

This is a good suggestion and one we will pass on to our engineers for their consideration. Thank you.

Hi Brandon. This is an excellent suggestion and something we plan to implement in the future. We do not have an ETA yet. However, we will make an announcement when this is available. We hope this helps.

This is a good idea. We have passed this on to our engineers. Thank you for the suggestion.

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.

Hi there. AppColl here. We appreciate the request and will certainly take this under consideration.

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 - While we currently grab the respective document(s) for each eOA --e.g. we do grab docs that go with 892 actions that come in-- I'll send this over to the Engineering team to see if it's something we can/should/could do. I like the idea of never having to log into PAIR (for various reasons, ha).

Scott