Posts made by gregg_appcoll

Hi Mark,

Thank you for the feedback. This is an interesting idea and something we will pass on to engineering for consideration.

-AppColl Support

Thank you for the input. These are good ideas. We will pass this onto engineering for consideration.

• AppColl Support

Hi Mark,

You can actually use the following form fields which can be added to the description/comments of a task. Provided the task is created from the email.

{Email.Subject}, {Email.Body} and {Email.From}

• AppColl Support

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

• AppColl Support

Hi George, we understand what you're saying and will look into it.

Thanks.

• AppColl Support

Hi Bernd,

If you someone already has a login to AppColl, we don't charge for them to log into additional accounts. You could allow this person access to your account and restrict their access to just the matters you want them to see. Does this work for you?

• AppColl Support

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

• AppColl Support

Hi Sadiq,

Thanks for the suggestion. We will pass this along to our engineering team for future consideration.

• AppColl Support

Thanks for your feedback. The original intent of Client Code was to be a shorter and identifiable name for the full client name. So you could use it everywhere and save space in the table view.

You can refer to the full client name in form letters/emails by using {Matter.ClientFull}

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.

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

Hi George,

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

• AppColl Support

Thank you Travis. We have added this as a project to our engineering list. We will make an announcement when this has been added.

• AppColl Support

Hi George - we will contact you directly to discuss this further.

Hi Christian - this filter has been added. We hope this helps.

• AppColl Support

We will work on some of the quality of life items that have been suggested here. We will update this page as we add such items. We hope this helps.

Hi George,

Thank you for the suggestion. We have recorded this with engineering and will let you know when this has been completed.

Hi Richard,

Thank you for the suggestion. We will have recorded this with engineering and will let you know when this has been implemented.

Hi George. Thank you for the suggestion. We will have recorded this with engineering and will let you know when this has been implemented.

Thank you for the suggestion. We have recorded this as a new feature request. We will let you know when this will be implemented.

Thank you for the suggestion. We will take this under consideration.

Hi Mark,

Thank you for the suggestion. We have recorded this as a new feature request. We will let you know when this will be implemented.

Hi Mark,

Thank you for the suggestion. We have recorded this as a new feature request. We will let you know when this will be implemented.

Hi Christian,

Currently, the solutions you mentioned are the only ways of doing so. However, we are working on a solution. We will certainly make this known once it's done.

Hi Christian,

Protecting existing subject matter connections is certainly import. We're looking into this. Thank you for pointing this out.

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

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

1. The number of customers requesting the feature. Obviously more requests elevates the priority.
2. 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.
3. 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 Sadiq. Thank you for your suggestion. We have added this as a formal request with engineering for implementation. We do not have an ETA yet. However, we will let you once completed.

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

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

1. The number of customers requesting the feature. Obviously more requests elevates the priority.
2. 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.
3. 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:

1. The number of customers requesting the feature. Obviously more requests elevates the priority.
2. 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.
3. 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 Brandon for the suggestion.

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

1. The number of customers requesting the feature. Obviously more requests elevates the priority.
2. 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.
3. 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!