@gregg_appcoll OK so to clarify, if I create a custom field "Test," configure the field for a contacts query, and set that field for a given Matter to a particular Contact, then {Matter.Test.email} will return that Contact's email address? How can I restrict the contact fields to match the current client? This is the logic I'm looking for but the syntax isn't quite right:

275350d0-9d8b-4271-a594-7357d713f874-image.png

@BrandonK6644 You could very easily set up such task types--just use the existing ones as templates, update/rename them as needed, and start using them going forward instead of the vanilla Filed RCE. You'd have to manually select the appropriate one, of course.

Doing the same for OAs would be a little more challenging since they autodocket, but I think it could be done. You'd have to make some fancy database query triggers that would check to see if a prerequisite task (e.g., 1st OA) had docketed before triggering a 2nd OA task, and checking to make sure that no existing 2nd OA task was present. I think this can all be done in the current task framework--see example below.

First NFOA - Create "Respond to 1st Non-Final Office Action" task
When a specific task is created: "Receive non-final office action"
AND
While a task database query doesn't return any records: Matter = "{Task.Matter}" and TaskType.Contains("Respond to") and TaskType.Contains("Non-Final Office Action")

Second NFOA - Create "Respond to 2nd Non-Final Office Action" task
When a specific task is created: "Receive non-final office action"
AND
While a task database query returns one or more records: Matter = "{Task.Matter}" and TaskType = "Respond to 1st Non-Final Office Action"
AND
While a task database query doesn't return any records: Matter = "{Task.Matter}" and TaskType = "Respond to 2nd Non-Final Office Action"

And so forth for 3rd, 4th, etc. NFOAs (assuming you want that level of granularity).

NOTE: In order for this to work, the most recent previous NFOA task has to be correctly assigned since each subsequent task creation event looks for the "previous" task that should have been created according to the trigger rules. So you'd have to analyze your docket and at least update the most recent Respond to NFOA tasks to reflect their proper "number" before implementing the above rules.

As far as I know, there isn't a "While a task database query returns exactly X records" where you can specify X. If that existed, you could avoid having to back-update your tasks to the new format.

Cheers,
Christian

Interesting idea - thanks. We'll pass this onto engineering.

Hi Christian. Thank you for the suggestion. We will certainly pass this on to engineering.

Hi Christian - we opened a fix for this. We'll let you know when done. Thanks.

Hi Christian - we will work on alleviating this by doing some truncation. We will keep you in the loop.

Hi Ashley - this is a good idea and something we will pass on to engineering for future consideration. We will certainly let you know of any progress made.