Skip to content

UI Design - Completing party for Incorporation Application, Amalgamation and Continuation In #32820

@mstanton1

Description

@mstanton1

Design review is required to understand how to handle completing party for Incorporation Application, Amalgamation and Continuation In

Considerations

  • currently completing party for all corp filings is prepopulated from the logged on user but may be changed (we store logged on user separately in filing history)
  • completing party is only needed on incorporation application (not amalg or continuation in) and in this case it must be the logged on user
  • completing party for the incorporation application could be stored in a distinct certified by component without editability, or could be tackled by prepopulating completing party from the logged on user and locking that down
  • completing party was collected in COLIN for incorporation application, and has been collected in the modernized system thus far, but policy notes the purpose with COLIN was to obtain information for document mail out

Metadata

Metadata

Assignees

No one assigned

    Labels

    Entities TeamA label to filter on the tickets for the Entities based team that takes care of front end featuresUXUser Experience Research & UI Design

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions