Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

Schema + Legal API: move court order file number validation from schema to API #18846

Closed
2 tasks
severinbeauvais opened this issue Dec 1, 2023 · 2 comments
Closed
2 tasks

Schema + Legal API: move court order file number validation from schema to API #18846

severinbeauvais opened this issue Dec 1, 2023 · 2 comments
Labels
blocked ENTITY Business Team

Comments

@severinbeauvais
Copy link
Collaborator

severinbeauvais commented Dec 1, 2023 •
edited
Loading

IT IS STILL UNDECIDED WHETHER WE WANT THE COURT ORDER SCHEMA TO NOT REQUIRE FILE NUMBER

  • make file number not required in schema
  • add API validations to require file number for all other filings (that use court order object)
@severinbeauvais severinbeauvais added the ENTITY Business Team label Dec 1, 2023
@severinbeauvais
Copy link
Collaborator Author

Blocked as we need a decision on whether or not we prompt/require the court order file number.

cc: @Mihai-QuickSilverDev

@severinbeauvais
Copy link
Collaborator Author

Not needed. Design changed.

This was referenced Dec 1, 2023
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
This was referenced Dec 2, 2023
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
blocked ENTITY Business Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@severinbeauvais