Yes, I agree this would be very helpful. By having an option to select a relative field (e.g., matter.attorney) as the "Owner" of a task, the system should be able to update who the task is assigned to, particularly when the matter is reassigned to a different individual (e.g., the Attorney of the matter is updated to a different person). Without this, updating the "Attorney" field of the matter does not (and will not) update owners of any Tasks, so it's necessary to change them separately.

This seems like a very easy change and is really important.

I'm looking for a Trigger Event of "When a particular TaskType with a FinalDueDate is in the past"

For example, the creation of the standard "Pay 1st Maintenance Fee - Final Deadline" task in AppColl is triggered at "When a 'Pay 1st Maintenance Fee - 1st Deadline' task completes with the 'Missed' state". That presumes that someone changes the 'Pay 1st Maintenance Fee - 1st Deadline' from "Open" to "Missed." Often we don't mark tasks as Missed although they were.

I might prefer that AppColl automatically adds the "Pay 1st Maintenance Fee - Final Deadline" task to the matter when the "Pay 1st Maintenance Fee - Final Deadline" task in the matter has a FinalDueDate that is in the past.

Possible?

It would be great if the E-mail Templates included an option to attach a Form to the e-mail being sent. Similar to how AppColl can assocaite and generate a Form with a Task, it would be helpful if the E-mail Templates could include the generation of a Form (i.e., letter, etc.) and attach it to the e-mail being sent.

@SadiqA2304 can you send a screenshot of the spot to click? I think we are thinking of two different process flows. I'm clicking the e-mail icon from within a matter in the matters tab.

I'm looking for a Trigger Event of "When a particular TaskType with a FinalDueDate is in the past"

For example, the creation of the standard "Pay 1st Maintenance Fee - Final Deadline" task in AppColl is triggered at "When a 'Pay 1st Maintenance Fee - 1st Deadline' task completes with the 'Missed' state". That presumes that someone changes the 'Pay 1st Maintenance Fee - 1st Deadline' from "Open" to "Missed." Often we don't mark tasks as Missed although they were.

I might prefer that AppColl automatically adds the "Pay 1st Maintenance Fee - Final Deadline" task to the matter when the "Pay 1st Maintenance Fee - Final Deadline" task in the matter has a FinalDueDate that is in the past.

Possible?

@SadiqA2304 can you send a screenshot of the spot to click? I think we are thinking of two different process flows. I'm clicking the e-mail icon from within a matter in the matters tab.

It would be great if the E-mail Templates included an option to attach a Form to the e-mail being sent. Similar to how AppColl can assocaite and generate a Form with a Task, it would be helpful if the E-mail Templates could include the generation of a Form (i.e., letter, etc.) and attach it to the e-mail being sent.

Are there any in-house counsel using AppColl that would be willing to interface with another in-house counsel about your experience with AppColl?

Ok good to know. Thanks.

Add a link to the "Matter Prior Art" for a Matter on the Matter Page.

I'd suggest that the "Owner" of a Task is maintained as a pointer to the "Paralegal" for the mattter, the "Attorney" for the matter, etc., EVEN AFTER the Task is created. It's somewhat problematic when the Attorney, for example, of an active matter having several pre-created tasks is changed, but it's necessary to separately change the "Owner" of all the pre-created tasks separately to the new Attorney.

@ChristianS2558 Agreed!

Yes, I agree this would be very helpful. By having an option to select a relative field (e.g., matter.attorney) as the "Owner" of a task, the system should be able to update who the task is assigned to, particularly when the matter is reassigned to a different individual (e.g., the Attorney of the matter is updated to a different person). Without this, updating the "Attorney" field of the matter does not (and will not) update owners of any Tasks, so it's necessary to change them separately.

This seems like a very easy change and is really important.