Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpEx: Practitioners' email address, as defined in each of their cases #5574

Open
wants to merge 1 commit into
base: staging
Choose a base branch
from

Conversation

jimlerza
Copy link
Collaborator

Added a report that will show what email address is defined for a given practitioner in each of the cases they are associated with. This is intended to be used by a human to manually determine if any cases failed to update after a practitioner updates their email address.

pract => pract.userId === practitionerId,
);
if (practitionerObj && practitionerObj.email) {
practitionersEmailInCases[practitionersCase.docketNumber] =
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to have a duplicate docketNumber (e.g., maybe missing distinguishing suffixes)?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even for docket numbers that have suffixes, the docketNumber.S field will not contain the suffix. The suffix is stored separately in the docketNumberSuffix.S field and a composite of the docket number and suffix is stored as docketNumberWithSuffix.S for good measure.

Because the docket number (without suffix) is used as the pk/sk for a case, there won't be duplicates.

If, however, it happens that the same practitioner can somehow be in a given case's [irs|private]Practitioners array twice, the .find() a few lines above will settle for the first match it comes across.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it--great explanation, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants