-
Notifications
You must be signed in to change notification settings - Fork 59
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
PPR Lien - Amend and Cancel Transport Permit #21012
Comments
@chdivyareddy not sure with verify tickets if you retest or just move to Done? |
@doug-lovett I'll retest this and move it to done once completed, thanks! |
@chdivyareddy thanks, moving to in progress after reviewing the design. |
LT lien verification:
POST https://bcregistry-dev.apigee.net/mhr/api/v1/admin-registrations/108336
Response Error:
|
Hey @doug-lovett , LT and ML validations looks expected, but for the MN registration type 'Cancel transport permit' validation is not displayed as expected. I'm seeing a 401 authorization failure error. Please take a look, thanks!! I'm using the BCREG0062 account (ID: 3248) in DEV using MHR 100377 for MN registration type. |
@chdivyareddy did 3248 create the transport permit for MHR 100377? You will see an authorization error with a cancel transport permit if the account did not create the permit. I just checked and staff created the permit. |
@doug-lovett , oh...got it, transport permit was created by staff for MHR 100377, will try with the same account, thank you! |
Reference Designs
Race condition is caught
(similar ticket Verify - Conditions Restricting Transfers on Manufactured Homes (all Transfer Types) #18330)
No PPR lien restrictions for staff. Verified.
Qualified suppliers are blocked if the PPR registration type is LT, ML, or MN. Verified with LT reg type.
Qualified suppliers are blocked on submission if a PPR lien LT, ML, MN registration type is created after the MHR registration starts. Verified
Qualified suppliers are not blocked for other PPR registration types. Verified with SA reg type.
The text was updated successfully, but these errors were encountered: