@JanisA1115

This is a good idea and something we have added as a new feature request with our engineering group. We will let you know when this has been implemented. An ETA is not know as of yet. Thanks.

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.

@KimG5166 this is on our list of future projects. We will make an announcement when this has been added. We hope this helps.

Hi Christian and Sadiq - we understand what you're asking and will pass this on to engineering.

@ChristianS9906

This has been added. Apologies for the delay. We hope this helps.

Thank you for pointing this out George. We will get this taken care of and let you know when done.

Hi Amy - Each time a document is saved (with the same name) a revision is created. Since we do not provide for editing a document within AppColl, the document must be edited on your local PC/Mac and then uploaded back into AppColl. This will create a new revision. Under this scenario, users would never be editing the same document.

We hope this helps.

@GeorgeJ4336

This is great information. Adding multiple signatures per document is our highest priority for Signatures. We will let you know when this has been added.

Hi - we are actively working on the transition. We will make an announcement this week.

@amy_appcoll

Yes, there is. You can use triggers for multiple task types that are all the same. So task 1 would trigger when some other action occurs. Task 2 would trigger from the exact same action as task 1 did. Same with tasks 3, 4, etc.

@ChristianS2558

We will get this done. Ver 1 may be to send the notifications to the account admins. Would this be OK? We can elaborate on it a bit later.

Hi Christian,

Thank you for your suggestions. Currently, we prevent multiple accounts from using the same customer number. This is for privacy reasons. A second account can use a cust number once we have approval from the first. Allowing any customer number in the contacts page would circumvent that requirement without additional validation.

Your addendum request is feasible and will be passed on to engineering. I hope this helps.

Thank you both for the suggestions. We will pass this onto engineering for consideration. We hope this helps.

Hi Darin,

Could you submit a formal request to support@appcoll.com to set up a call to get you comfortable with this type of setup?

Thanks.

@GeorgeJ4336 We accomplished this by adding a new field called {Matter.Client.PrimaryContact.NickNameOrFirst}. With this change, we will use the nickname if it exists, and if not, we will use the first name.

Sorry for the delay in following up. We hope this helps.

Hi George, thanks for reporting. This issue should be resolved soon.

Hi Kevin, thanks for the feedback. This feature is being worked on and should be available in the future.

Hi Michael. Thanks for the feedback. Did you know that AppColl can create one invoice per matter in a bulk operation? This may alleviate the issue you have with multiple users trying to create multiple client-specific invoices. Now, as you know, this will not allow for editing multiple invoices by multiple users simultaneously.

The daily task notification emails are a legacy way of alerting you to upcoming due dates. We highly recommend creating your own custom docketing reports instead, as this approach is very limited in the data that can shown in the email.

However, if you are still using the legacy reports, we do not include every upcoming due date on every day. By default, as shown below, each task is shown on the 1, 2, 3, 4, 5, and 6th month of its due date. Then within 1 month, the task is shown 1, 2, and 3 weeks before its due date. Within the last week, the task is shown each day leading up to its actual due date.

@JohnG8374

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

Thanks.