-
Notifications
You must be signed in to change notification settings - Fork 0
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
Multiple Agency/Partner Mechanisms #10
Comments
@benguaraldi: following up on the requirement changes, I looked into adding support for multiple agencies for a given mechanism...the problem is I can't find any with the current logic The code looks at each mechanism (category option) and then looks through its associated categoryOptionGroups. The categoryOptionGroup that has a I cannot find any mechanisms that have more than 1 category option group with a code that starts with Is there some other logic that Josephine might explain why Josephine says that there are mechanisms with multiple agencies? Could it be relevant for her if the Partner is shared with multiple agencies, rather than the mechanism itself? |
Also, FYI @hardingt if you have any ideas |
@tomzemp There shouldn't be any mechanisms with multiple agencies. Every mechanism has one and only one agency, partner, and operating unit. Maybe Josephine meant something else? (Sorry for the delayed response on this.) |
After discussing this with @benguaraldi, we assume that Josephine is referring to cases where the Partner has multiple agencies within a given OU, this would mean that users would need to be created by an Interagency User. In this case, we may want to display this information in the Partners box...but we will need to modify the app more to make subsequent calls to determine agencies for partner related to a given mechanism within a given OU...so unmarking it as MVP |
Investigate what a multiple agency/partner is for end users
The text was updated successfully, but these errors were encountered: