search

CityOfBoston / CityWorker-issues-Incapsulate

Archived for legacy purposes
0 stars 0 forks source link

Reallocation and transfer email #11

Closed vanessacalderon closed 6 years ago

vanessacalderon commented 7 years ago

@jqr -- sorry Elijah, can you give me the text of the reallocation email again?

I lost the link on the chat....

jqr commented 7 years ago

I deleted @davemitchell's original comment because the version I shared during the call had some minor fixes that were important to keep.

We are eager to get Reallocate finalized, so let me start with a proposal of what I believe we described during the most recent call.

Actions

The sequence of actions that the Spot servers will take to Reallocate a Request.

  1. We call PATCH on /311/v3/requests/REQUEST/activites/ACTIVITY.json

We will send these fields:

attribute[...]
media_url[...]
additional_comments
internal_comments
response_code

Will will omit this field:

outcome_code
  1. We call PUT on /311/v3/requests/REQUEST/reallocate.json

We will send these fields:

queue
reason

  1. We will mark Spot's local copy of the Activity as completed, and modify the foreign key reference. This will cause our upstream synchronization protocol to stop modifying the original Activity, but still send it to mobile clients for history preservation.

  2. We will synchronize upstream again and the single Incapsulate Activity will be created anew within Spot due to the foreign key mismatch, leaving the original Activity in place.

Results

I believe this should give both sides the historical record and a reasonable view of the current state of the Request at all times.

Salesforce Result: Only one Activity is ever created, but the history of that activity contains the reallocate data submitted in Step 1.

City Worker Result: Mobile clients will see an Activity completion for the Reallocate action, and a new Activity will appear, with identical outcome options/questions/etc. to the original activity.

Next Steps

We can begin this after sign-off from Boston(Vanessa) / Incapsulate(Karthik) that this is agreeable to all.

Once everyone is agreed, we expect a few days of implementation and a few more for testing/validation.

jqr commented 6 years ago

This has been decided through numerous emails, meetings, flowcharts and documents. I think BOS311API-70 is probably the best place to follow along, but I'll try to keep this updated as we make progress.

jqr commented 6 years ago

Actually, given this was just about the email thread. I'm going to close this Issue to remove some noise.

vanessacalderon commented 6 years ago

That is a good idea.

Thanks!

On Mon, Dec 4, 2017 at 12:19 PM, Elijah Miller notifications@github.com wrote:

Actually, given this was just about the email thread. I'm going to close this Issue to remove some noise.

— 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/11#issuecomment-349034355, or mute the thread https://github.com/notifications/unsubscribe-auth/AfC5vfuacCHO2JjYdQaO0GoeasFiVmGYks5s9CmcgaJpZM4P-O8Y .

--

Vanessa Calderon

CRM Specialist

City of Boston | DoIT

vanessa.calderon@boston.gov | 617.635.4412