Skip to content

Fix normal walkthrough after opposing-party address #3

@drkwjr

Description

@drkwjr

Issue

The Separation Agreement interview still has a normal-flow walkthrough blocker after the opposing-party address screen.

In local Docker testing, docassemble.ADivorceAgreement:divorceagreement.yml now reaches the new trial court division screen and accepts trial_court.division, but after submitting other_parties[0].address.*, docassemble returns:

Problem getting current question:'nota'

What we know

  • This was reproducible on origin/main before the Portable/schema adapter branch, so it was not introduced by the adapter work.
  • The adapter PR fixed a separate missing court-field problem by adding trial_court: MACourt and a trial_court.division question.
  • With already-known tail fields preloaded after opposing-party address (users[0].address, signature_date, docket_number, preview continue), the interview reaches download a_divorce_agreement and generates a_divorce_agreement.pdf.

Acceptance criteria

  • A normal API/UI walkthrough can proceed past opposing-party address without tail-field preloading.
  • The interview reaches the download screen for the no-children baseline scenario.
  • Generated PDF still includes the expected party names, docket number, and address values.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions