You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now select the underenhet again, and you should be taken to the form.
It seems that when using the browsers back button, some form of state remains, preventing the user from changing party. This creates a confusing login process, where the user gets the impression that they can't use the form.
Additional Information
Ideally, we would have liked to reproduce the error screen used when a user fails the "oppstartskontroll" validation, by redirecting them back to the party-selection screen with a custom error message like so,
The text was updated successfully, but these errors were encountered:
Regarding my comment under "Additional Information". ivarne pointed out on Slack that the InstantiationValidationResult object we return contains a validParties fileld. We assume we could achieve the desired behaviour by using this, but we've been unable to find a way of determining what parties the user has access to, and how to aquire them. Is there an endpoint we can call in the app for such information?
Description of the bug
When using a custom IInstantiationValidator, if validation fails, the user can get stuck trying to change the party they are representing.
We have a custom IInstantiationValidator in one of our forms. This validator allows "Privatpersoner", "juridisk enhet uten underenheter" and "underenheter".
Steps To Reproduce
It seems that when using the browsers back button, some form of state remains, preventing the user from changing party. This creates a confusing login process, where the user gets the impression that they can't use the form.
Additional Information
Ideally, we would have liked to reproduce the error screen used when a user fails the "oppstartskontroll" validation, by redirecting them back to the party-selection screen with a custom error message like so,
The text was updated successfully, but these errors were encountered: