-
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
Legal API: return "displayLedger" flag in filings results #18490
Comments
@kzdev420 Hi Kevin, would you be able to help with this back end ticket? This would unblock in turn the front end ticket. Business would like this escalated, so I have brought it into this sprint. |
I will do this ticket |
Are we still creating the freeze/unfreeze ledger entries, and simply adding "displayLedger=false"? In that case, the requirements in #16967 need to be updated. |
We had agreed we wouldn't put anything in the ledger that would then need to be hidden. |
@argush3 Hi Argus, I see that this ticket is in Review. What was decided and done on the BE for this? And would the corresponding FE ticket be unlocked now? |
A PR has been created but we need to decide what to do with this. Please take a look at Thor's comment above. |
Actually the proposed approach is strongly dictated from the user side. In a majority of cases the freeze would be caused by a missed payment, and businesses have expressed in the past strong opinions on not having ledger entries added that could be considered detrimental to a company's reputation, etc. I have escalated this for resolution and executive decision at the Product Owner and Program Director's level and wll communicate here an abiding decision. |
For the record, the I'm not sure if this mitigates the "hidden items need FOI request" concern. And actually, how would users know whether some ledger items are not displayed? |
Dave spoke with Elizabeth who will circle back around this week, when we hope to unblock this. |
Linda will discuss with Thor. |
I met with Yasmin and we've agreed that the admin freeze/unfreeze actions should not appear in ledger history. Using the bank statement analogy, when the bank sends us a letter or vice versa there isn't anything appearing in the list of ins/outs on our bank statement regarding the correspondence. At the end of the day, there should be a message in the tombstone that it is frozen. And the comment staff entered should show up in the comments tab. |
thanks @lmcclung |
@thorwolpert , since Freeze and Unfreeze are filings, should we: Also, staff are required to add a detail comment to a Freeze/Unfreeze filing. This comment is linked to the filing (not to the business). Since we won't be displaying the filing in the ledger, should the comment be linked to the business instead, or shown in the staff comments section anyway? PS - Yes, the business response ("tombstone") does indicate when an admin freeze is in place: |
When they were presented more than a year ago, it was an admin flag and a staff note, not a filing. As stated above, they are often done because of payment issues. |
@thorwolpert OK, but this is the way they are now. Can you help us figure out what to do? |
@thorwolpert - Mind helping us solutioning this within what you see could work? |
sure, but it does seem like it should still be just setting the flag to block a business from being updated and assigning a staff note as to why. |
With also having more than 1 managing account now, I think the whole freeze/block thing needs a review. |
@thorwolpert , the existing code creates a Freeze (and Unfreeze) filing in the ledger. Do we show it? If not, how do you propose we hide it? And if we hide it, how do you propose we show the detail comment in the Staff Comments instead of the Filing Comments? PS We do set an |
If it's in the ledger, then I guess it gets shown. |
Requirements:
Option 1: change freeze and unfreeze to not be filings Option 2: hide freeze and unfreeze filings in ledger Based on the feedback from @lmcclung above, and a decision by @davemck513 today, we are going to implement this ticket as documented: we will hide the freeze and unfreeze filings. This ticket is no longer blocked. |
Test NotesThis Legal API change was tested as part of #16967. More specifically, you can look at the |
The Legal API needs to return a
displayLedger
boolean flag for every filing in the filings response. All filings should be True except for:Here are the detailed requirements, taken from Argus' comment in #16967:
I don't think it will be in the business response if I'm understanding your question correctly.
This flag will be specific to a filing. So the displayLedger flag can be returned in the GET /filings and GET /filings/<filing_id> endpoints I think.
I was thinking just add a dictionary to the BE that defines filings that shouldn't be displayed on the ledger. And these two filing endpoints will just use to set the flag accordingly.
At the end of the day, for our use case, we probably only need to update the GET /filings endpoint.
Examples
GET /filings endpoint

GET /filings/<filing_id> endpoint

The text was updated successfully, but these errors were encountered: