@ChristianS9906 Yes, I have been manually updating it for each filing so that I could more easily calculate expiration dates. Having an auto-populated EBD date will be good. I never really understood the purpose for "Official Filing Date" in the original definition of the matter record.

What about using EBD and PTA to auto-populate Expiration date? I understand that AppColl may not want to do that for liability reasons and you would also need to have PTE (which none of my clients get) to fully implement expiration date calculations.

I still don't see EBD. Guess it is still 'coming soon' but I am looking forward to having it.

@ChristianS9906 I am seeing EarliestBenefitDateEdited as a choice for Trigger Events. I would guess that your analysis is correct. I just want to make a change in EBD is a reliable trigger for my event. If changing the EBDEdited field causes EBD to change, then it will be. That is the crux of my question.

Another question on how things work. If the user puts in an EBD date then later adds Connections that would cause the EBD to actually be earlier, how will the user be notified that they should check the EBD? Will there be a warning triangle (like when USPTO data doesn't match AppColl data) or something like that so the user can make a decision about whether or not to change their manual override?

@gregg_appcoll One more question. I also see an EarliestBenefitDateEdited field. What is that?

@gregg_appcoll It still looks like EBD is not being proactively populated for all cases by AppColl. If I add the column in the Matters tab, I can see that it is not populated for most matters. But if I open a matter, it has been populated, so if I then save the matter, it is there. Are there plans to proactively populate existing matters? If not, is there some way to get EBD populated without opening each matter and then saving it?

@ChristianS9906 I thought about docketing both up front, but thought it would be better to daisy-chain them - either should work. The trick is to get the 6 year reminder to post even if the matter is filed after the 6 year date, but there is a setting in tasks that lets you tell it to go ahead and generate the task even if it is past due. Then the next day it should auto-close and generate the 9 year reminder. At least that is my plan.

@ChristianS9906
How do you plan on triggering these tasks. I am thinking that I will create a 6 year reminder whenever a US matter non-provisional utility matter (including continuations, divisionals, etc) is created and then have it auto-close with a custom task type of "Passed without filing". The 9 year reminder would be created whenever a 6 year reminder closes with "Passed without filing". Figure that this will work even for a case that is filed after the 6 year deadline.

@ChristianS9906 _ 100% agree. The tasks I created currently use "Official Filing Date" as the basis for the response date. Would need to use EBD field there.

@gregg_appcoll
It looks like the EBD field is calculated when a matter is opened, so it can then be saved. But it has not yet been calculated for all matters because if I add it as a column in the Matters module, it is blank for most matters. Are there plans to proactively calculate EBD for all matters in the system?
It would be a pain to go in and do it for all pending matters.

@ChristianS9906 I just put in a support ticket asking the same question.

@ChristianS9906 Yes, I have been manually updating it for each filing so that I could more easily calculate expiration dates. Having an auto-populated EBD date will be good. I never really understood the purpose for "Official Filing Date" in the original definition of the matter record.

What about using EBD and PTA to auto-populate Expiration date? I understand that AppColl may not want to do that for liability reasons and you would also need to have PTE (which none of my clients get) to fully implement expiration date calculations.

I still don't see EBD. Guess it is still 'coming soon' but I am looking forward to having it.

What is the status of this? I don't see EBD as an option for fields in the trigger events for task types.

I have actually been using the "Official Filing Date" field for this purpose since I began using AppColl 10 years ago. It is the same date that is useful for calculating the start of the 20 year term.