API - New Securities Act Registration

[mstanton1]

New PR registration type

• [x] Update schema
• [x] Update spec
• [x] Update database data model
• [x] Update API model, validation rules
• [x] Update verification report (no UI design).

Developer Notes:

• Add column security_act_ind to account_bcol_ids
• Create a single client party code to be used by all security act registrations as 1 secured party.
• account_bcol_ids will link the BCROS account id to the secured party code
• Same MISCLIEN data requirements/validation as WL reg type.
• New MISCLIEN registration type description "Securities Act Notice"
• New properties (possibly new db model securities_acts table):
  • Distinguish 3 sub-types: i. Notice of lien ii. Notice of preservation order iii. SA notice of proceedings
  • effective date
  • description
  • orders (court or commission), allow multiple in the model
• Allow multiple notices per registration
• Search report update not in this ticket, waiting on UI design.

[doug-lovett]

Example request: POST /ppr/api/v1/financing-statements { "type": "SE", "clientReferenceId": "T-FS-SE-0001", "authorizationReceived": true, "registeringParty": { "code": "09070001" }, "securedParties": [ { "code": "09070001" } ], "debtors": [ { "businessName": "DEBTOR TEST INC.", "address": { "street": "721 Debtor Ave", "city": "Victoria", "region": "BC", "country": "CA", "postalCode": "A1A 1A1" }, "birthDate": "1990-06-15T00:00:00-07:00" } ], "generalCollateral": [ {"description": "SECURITIES ACT NOTICE GENERAL COLLATERAL HERE."} ], "lifeInfinite": true, "securitiesActNotices": [ { "securitiesActNoticeType": "LIEN", "effectiveDateTime": "2024-04-22T06:59:59+00:00", "description": "LIEN description", "securitiesActOrders": [ { "courtOrder": true, "courtName": "court name", "courtRegistry": "court registry", "fileNumber": "FN-000001", "orderDate": "2024-04-22T06:59:59+00:00", "effectOfOrder": "court order summary" } ]
}, { "securitiesActNoticeType": "PROCEEDINGS", "effectiveDateTime": "2024-04-22T06:59:59+00:00", "description": "PROCEEDINGS description", "securitiesActOrders": [ { "courtOrder": false, "courtName": "court name", "fileNumber": "FN-000002", "orderDate": "2024-04-23T06:59:59+00:00", "effectOfOrder": "commission order summary" } ]
}, { "securitiesActNoticeType": "PRESERVATION", "effectiveDateTime": "2024-04-22T06:59:59+00:00", "description": "PRESERVATION description" }
] }

Note: this will be a UI only registration.

[doug-lovett]

Verified in DEV with Base reg number 100215Q. Reg report attached.2024-04-24_BCPPR_SE_Registration_Verification_100215Q.pdf

[doug-lovett]

@chdivyareddy I verified in DEV with account id 3040 brtest1. If you want to test in DEV with a non-staff account I can set it up once you provide the account ID. Otherwise you will get an unauthorized response.

[chdivyareddy]

@doug-lovett thanks for checking, earlier I tried in DEV using BRTEST1 only and it did not work, but please give access to non-staff account BCREG0057 (ID: 2753) in DEV.

[doug-lovett]

@chdivyareddy 2753 can now submit SE reg type requests in DEV with the same client party code for the registering and secured party as the above example: 09070001. Maybe verify your Postman request header Authorization value, I see these errors for requests submitted last Friday: {"accountId":"3040", "error":"{"errorMessage": "API security error: JWT check failed.", "rootCause": "fault:faultstring:Failed to Resolve Variable : policy(Verify-JWT-Dev) variable(null),detail:errorcode:steps.jwt.FailedToResolveVariable"}", "messageId":"rrt-5282581435239514295-c-gnne1-14138-148502-1", "method":"POST", "requestPath":"/ppr/api/v1/financing-statements", "statusCode":"401", "userName":"ppr-app"} This error indicates the JWT was missing.

[chdivyareddy]

Thank you @doug-lovett , will take a look.

[chdivyareddy]

@doug-lovett , it worked in both staff and non-staff accounts in DEV. Thank you!!

Verified in DEV using postman request: PPR 100218Q, 100217Q

Registration report: 2024-04-29_BCPPR_SE_Registration_Verification_100217Q.pdf

[doug-lovett]

Updated registration and search result report examples (UXA review as part of the API amendment/discharge ticket): Registration: financing-sa-example.pdf

Search: search-detail-reg-num-example.pdf

[chdivyareddy]

TEST - PPR 100079Q

Registration Output: 2024-05-14_BCPPR_SE_Registration_Verification_100079Q.pdf

Search Output: 2024-05-14_BCPPR_Search_Result_100079Q_13133.pdf