Skip to content

Error when trying to change the 'Place of stay' and 'Responsible jurisdiction' of Port Health case as responsible jurisdiction is editable #12708

Open
@adinaflorea9

Description

Problem Description

An error appears asking the user to provide a valid point of entry appears when trying to change the 'Place of stay' and 'Responsible jurisdiction' of a port health case (point of entry case) for cases of Travel Entries and for cases created directly as point of entry cases.

Steps:
Create case from the page of a travel entry:

  1. Log in with an Admin+NatUser;
  2. Open an existing travel entry and click on 'Create case';
  3. Fill in the mandatory information and se the jurisdiction to Region1, District1;
  4. Save the new case;
  5. When on the case edit page, update the jurisdiction to Region2, District 2 and try to save.

Create case from the case directory:

  1. Log in with an Admin+NatUser;
  2. In the 'Cases' directory, click to create a new case;
  3. For the 'Case origin' select 'Point of entry';
  4. Fill in the mandatory information and set the jurisdiction to Region 1, District 1;
  5. Save the new case;
  6. When on the case edit page, update the jurisdiction to Region 2, District 2 and try to save.

Actual behavior: An error appears asking the user to specify a valid point of entry.

Expected Behavior

The point of entry belongs to the responsible region and district -> it is cleared when the jurisdiction changed and saving is not allowed.

The responsible jurisdiction should be read only.

The "Place of stay of this case differs from its responsible jurisdiction" checkbox - if the checkbox is checked when the case is created, afterwards the place of stay information is already read only and can not be updated.

Additional Information

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    caseschangeA change of an existing feature (ticket type)readyIssue fulfills the definition of ready and can be implementedvaadin-appAffects the Vaadin application

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions