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

Schema - AGM Location Change (part II) #18162

Closed
5 of 6 tasks
Mihai-QuickSilverDev opened this issue Oct 13, 2023 · 6 comments
Closed
5 of 6 tasks

Schema - AGM Location Change (part II) #18162

Mihai-QuickSilverDev opened this issue Oct 13, 2023 · 6 comments
Assignees
Labels
ENTITY Business Team

Comments

@Mihai-QuickSilverDev
Copy link
Collaborator

Mihai-QuickSilverDev commented Oct 13, 2023

Data elements from the requirements pov. Developers to make the final decisions on the data elements details.

  • Company AGM Location Change

  • Applicable to BC Ltd., BEN, ULC, CCC, C company types.

  • Requirements and UI Design are completed and baselined.

  • Data Elements
    i. AGM Year – Numeric, 4 digits, the year for which an AGM Location change is requested.
    ii. Reason – Character box, maximum 2,000 chars. Reason for requesting an AGM location change.
    iii. AGM location - Character box, maximum 100 chars. Would contain City, Province/State and Country. Would be used to generate an output letter. Originally an address field was proposed, and then this format was requested, as it is used currently.

  • Verify the Reason field, 2,000 chars max.

  • Remove address reference

  • Add AGM Location field max. 100 chars
    - [ ] Add Completing Party (maybe -- Mihai to confirm)

  • The output letter was approved to use a generic "Dear Applicant" expression, so we do not need to collect the Completing Party anymore.

  • Update example data

  • Create unit tests

@Mihai-QuickSilverDev Mihai-QuickSilverDev added the ENTITY Business Team label Oct 13, 2023
@severinbeauvais severinbeauvais changed the title AGM Location Change - Schema part II Schema - AGM Location Change part II Oct 13, 2023
@severinbeauvais severinbeauvais changed the title Schema - AGM Location Change part II Schema (AGM Location Change) part II Oct 13, 2023
@severinbeauvais severinbeauvais changed the title Schema (AGM Location Change) part II Schema - AGM Location Change (part II) Oct 18, 2023
@chenhongjing chenhongjing self-assigned this Oct 19, 2023
@Mihai-QuickSilverDev
Copy link
Collaborator Author

@chenhongjing The completing party is no longer needed. I have crossed it out from this ticket's description.
@severinbeauvais @yuisotozaki

@Mihai-QuickSilverDev
Copy link
Collaborator Author

Strange, previous comment never got changed, trying again here:
The AGM Year field is required to be displayed in several places in the outputs, so we need this value.
Would leave it up to the developers to decide how to capture it.

@severinbeauvais
Copy link
Collaborator

@Mihai-QuickSilverDev
Copy link
Collaborator Author

  • We started with the address box, however the business rejected this approach for two reasons:
  1. Clients never had to provide a complete address before.
  2. There is also a very good chance that clients might not know a full address when requesting the location, as they have not secured a venue yet.

@severinbeauvais
Copy link
Collaborator

Well, please let us know if the current newAgmLocation text field is OK or if we need to break it down into country/province/city.

@lmcclung
Copy link
Contributor

As per Mihai, I agree that clients have never had to provide a complete address before and indeed, it would be unwise for them to book a facility until they have approval from us to move location.

This is a really low volume filing, like maybe half a dozen a year; and would be done by paralegals. I’m okay for this to be a free form text field with no location validation and not stored as an address in our database. If it is even stored in the CPRD database currently, it would be a text field there, too.

If we need to introduce validations, based on evidence of poor data in self-serve filings, we can cross that bridge later.

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

No branches or pull requests

4 participants