BOS311 not excluding a private case

[vanessacalderon]

I marked case #1472 as private and this case is still visible in BOS311. The web portal is not displaying the case.

[jqr]

Here's the interface contract Spot Server is expecting:

From @gackerjr on Dec 5, 2017: Re: Private Cases

private cases aren't necessary for launch, but needed shortly thereafter ... cases will not be marked private due to language or personal information. Business process will be to scrub the data in the public fields and move them to internal fields.

And I recall from the phone call that cases were going to marked private for a very short period, scrubbed, and then the private flag removed.

The integration is not made to handle Cases that violate the contract and intend to stay private indefinitely.

This is the first I'm hearing of a policy change here but it has some serious technical impact on Spot's integration that are worth discussing.

[vanessacalderon]

Ok, I was just checking the"very short period" section of the contract. If, for a moment, the case would not show, because I was marking it private, checking BOS311, and then marking it public again, and then checking BOS311. So I guess the "very short period" is not applicable? The case will always stay visible in BOS311.

[jqr]

So the way I envisioned that working is short period was something like seconds to minutes. During that time the case would be fully visible in BOS311. Once the case was made public again the new scrubbed fields would take over.

Put another way, for BOS311 with the Incapsulate backed server, whenever something is marked private, it stops being sent to the BOS311 app, but it may already be there. If it is already there the data remains exactly as it was before private. As soon as it is public again, the new data will replace existing data on devices.

So from my end, the contract is important because it minimizes the time that private data can be seen.

The next best alternative is to force a full resync of all reporters whenever any ticket moves from public to private. While this is more correct, it is more disruptive and costly and something I thought we could avoid given the policy/contract in place.

Ultimately we'll do what it takes to make this right, but if we adhere to the contract then I think this issue is very minimized.

[vanessacalderon]

I guess I got confused because the web portal was instantly adapting to the change of private/public of the case. But we should leave it like that because we cannot make private a case for some API integrators that are public facing (BOS311 and Web Portal) and not to internal facing API integrators (City Worker).

[image: image.png]

[image: image.png]

[image: image.png]

On Fri, Sep 21, 2018 at 10:58 AM Elijah Miller notifications@github.com wrote:

So the way I envisioned that working is short period was something like seconds to minutes. During that time the case would be fully visible in BOS311. Once the case was made public again the new scrubbed fields would take over.

Put another way, for BOS311 with the Incapsulate backed server, whenever something is marked private, it stops being sent to the BOS311 app, but it may already be there. If it is already there the data remains exactly as it was before private. As soon as it is public, it goes out and replaces the existing data.

So from my end, the contract is important because it minimizes the time that private data can be seen.

The next best alternative is to force a full resync of all reporters whenever any ticket moves from public to private. While this is more correct, it is more disruptive and costly and something I thought we could avoid given the policy/contract in place.

Ultimately we'll do what it takes to make this right, but if we adhere to the contract then I think this issue is very minimized.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/CityOfBoston/CityWorker-issues/issues/126#issuecomment-423562219, or mute the thread https://github.com/notifications/unsubscribe-auth/AfC5vZOThOFqVbPG9nyc1RdxzGm8Gz7hks5udP6sgaJpZM4WVi-- .

--

[image: COB_B_Blue_square-01.png]

Vanessa Calderón

CRM Specialist

City of Boston | DoIT

vanessa.calderon@boston.gov

617.635.4412 (w)

[vanessacalderon]

Closing the issue

[vanessacalderon]