@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, yes. They are numbered within each category. Can it be sent to number cumulatively for the entire SB/08? Thank you.

@BrandonK6644 We worked in depth with our developers on this today. Unfortunately, there is not a way to make this work within the current reporting capabilities of AppColl.

Apologies for the delay.

@BrandonK6644

So sorry for the delay. We have increased the priority on this one. We will announce when this has been done.

@BruceY9495 UPDATE: Our account has EBD data for about 40 matters, but that's it. I guess it is still updating/being calculated.

Our account had the EBD data in it as of this morning, so I think they have added it.

Thanks, Gregg!

@MelissaT3398 The new form was pushed out yesterday from the PTO. We should have it in AppColl by tomorrow. I hope this helps.

@ChristianS9906 Great. Thanks for the feedback.

@ChristianS9906 agree that is a good alternative

Hi Sadiq, no progress yet, but we will review priorities with engineering. Thanks.

@joe_appcoll Nice, thanks

Thanks for the suggestion. We will certainly pass this on to engineering.

The reason may have been to stop generating a number of tasks when the priority date changes. This allows you to manually edit what you need.

@ChristianS9906 We will be adding a way to access the client's intake address if their account is being synced to.
There is not currently a notification for when a bad intake address receives an email.
We will discuss adding this as well.
Account admins do receive a notification if an email is sent to a valid intake address but the sender is not whitelisted.

@ChristianS9906 Whereas AppColl already implemented the change you requested, I'm reluctant to request they change it back. I don't know to what extent others have strong or weak feelings about e-mail addresses with or without aliases (display names). You and I have stated our preference and reasons. It would be interesting to see if anyone else expresses an opinion.

This feature is really important and should be prioritized. It is causing many manual work around on our end and that is disappointing.

Hi George,

Interesting idea. Thanks for spending the time to clearly lay this out. We'll take a look at it.

@AccountingA3700

We have added this as a formal new feature request. We will let you know when this has been added.

@KimG5166

Thank you for the suggestion. We will look into adding an option to choose between the two. We hope this helps.