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

Assess feasibility of supporting a Connect Card enrollment pathway for the SACOG region #2567

Open
3 tasks
indexing opened this issue Dec 5, 2024 · 1 comment
Assignees
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc) product Issue captures work for the product team

Comments

@indexing
Copy link
Member

indexing commented Dec 5, 2024

Acceptance Criteria

  • Compiler product and engineering teams understand the technical architecture used to manage Connect Card users
  • The above technical configuration will work with the Eligibility Server module in Benefits
  • The team managing the Connect Card implementation believes they can support the Eligibility Server module.

Additional context

  • If feasible, we aim to deploy this solution in Q1 2025 for all agencies in the SACOG region.
@indexing indexing added the deliverable Work that ends with a non-code deliverable (e.g. Google doc) label Dec 5, 2024
@indexing indexing self-assigned this Dec 5, 2024
@indexing indexing moved this from Todo to Needs shaping in Digital Services Dec 5, 2024
@indexing indexing added the product Issue captures work for the product team label Dec 5, 2024
@indexing
Copy link
Member Author

indexing commented Dec 5, 2024

@thekaveman I'd like to do a quick co-working session (or asyc update here) with the dev team to scope what information we need to assess to determine if we can support the Connect Card with our Eligibility Server. Once we have a basic scope, I'll setup a meeting with the SacRT IT team for a deeper discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc) product Issue captures work for the product team
Projects
Status: Needs shaping
Development

No branches or pull requests

1 participant