OSE - New Processes For Neighborhood Block Party Folder (TL)

[atdservicebot]

As an Street Event Reviewer, I need to track department specific reviews for on RW, Work Type Neighborhood Block Party. Those department reviews are APD Review, Fire Review, and Trash and Recycling Review. These reviews need to populate on those department's user group tasks lists.

Requester: Maria Alonzo DTS Manager: Tracy CTM Help Desk Ticket # : 1969325

Acceptance Criteria:

Previous Acceptance Criteria:

• On folder type RW, Street Event, and work type Neighborhood (NPH), the folder will insert 3 review processes when an Approved attempt is saved on the Event Review process (50560)
  • 72014 APD Review, 50040 Fire Review, 72008 Trash and Recycling Review.
• The "Approved" attempt should not close out the Event Review process, it should stay open
• The 3 processes should be assigned to the correct groups
  • ACE APD, ACE ARR Review, Fire Review
• The 3 processes are grouped by 'Review' type
• Should there be a calculated end date? Yes and it should be the Event Start date
• The 3 New Review processes will automatically close (if still open) when certain attempts are saved on any of the 3 New Review processes (ACE APD, ACE ARR Review, Fire Review)
  • Attempts: Approved, Rejected, Withdrawn
• Once any of the 3 New Review Processes have an attempt of Approved, Rejected, Withdrawn; It will close out all 3 New Review Processes as well as the Event Review Process with a status of "Closed"

---

"Event Intake" does not be inserted at all, "Event intake" Process needs to be not be inserted automatically "Event Review" Process needs to already be there when the folder is created The Trash and Recycling Review need to be assigned to ACE ARR Review group The APD Review need to be assigned to ACE APD Reviewer On the Info tab: Add "Neighborhood Block Party" to Event type info

---

The "Approved" attempt should not close out the Event Review process, should stay open Should there be a calculated end date? Yes and it should be the Event Start date Once any of the 3 New Review Processes have an attempt of Approved, Rejected, Withdrawn; It will close out all 3 New Review Processes as well as the Event Review Process with a status of Closed

Next Steps

• LIT Development

Request Details HD 1969325.pdf

Migrated from atd-amanda #112

[Sreelatha-BlazeKannan]

Aishwarya would do the DEV UAT and update the same thank you.

[TracyLinder]

UAT with Maria is scheduled for 10/30 @ 1pm

[vschandramouli]

Deleted comments on meeting notes to avoid confusion on AC.

[aishwarya2505]

Post discussion with Nadin on Teams, a new requirement was identified: Approved will leave a status of Closed, the others will leave; Withdrawn = Withdrawn; Rejected = Rejected but all 3 would close the Processes.

I have made these changes on local host and also sent the demo recording via e-mail. All but this latest change have been committed on DEV. Post approval of demo, I shall make the commit in DEV.

[TracyLinder]

UAT Feedback:

• I've scheduled a meeting w/ the dev team to discuss the feedback on 11/2

[Sreelatha-BlazeKannan]

@Nadin-Nader @TracyLinder - Aishwarya have submitted the most recent demo post discussion with Nadin on another new requirement. Post meeting this can be updated.

[TracyLinder]

AC has been updated. This is going back to 'In Progress'

[Sreelatha-BlazeKannan]

@Nadin-Nader , @TracyLinder - Changes are in progress by Aishwarya

[aishwarya2505]

@Nadin-Nader @TracyLinder

The demo with the revised AC has been sent on 11.4.2020.

Part 1 and Part 2 have been addressed.

Link: https://launchitcorp-my.sharepoint.com/:v:/p/aishwarya_r/EVdrXmN6VxRBjCVAo3ItG8kB0cBLirq5ZR061hzkPT0IQQ?e=k7fylp

[Sreelatha-BlazeKannan]

@Nadin-Nader @TracyLinder - waiting for feedback. once it is approved it can be moved to DEV.

[Nadin-Nader]

@Sreelatha-BlazeKannan @TracyLinder I have reviewed the demo and the acceptance criteria has been met. I approve to go to DEV

Approved for DEV Deployment 🎉🎉

[Nadin-Nader]

@Sreelatha-BlazeKannan @aishwarya2505 @SubhaShroff @TracyLinder I have sent this over to the DevOps CM Team for DEV deployment under TASK SCTASK0105133

Status:

Waiting on CM Team to deploy to DEV

[Nadin-Nader]

@Sreelatha-BlazeKannan @aishwarya2505 @TracyLinder This has been deployed to DEV and is ready for UAT

[aishwarya2505]

Tested 11896203 in DEV and the changes work as expected.

[Nadin-Nader]

@aishwarya2505 @TracyLinder @Sreelatha-BlazeKannan i have UATd this on DEV and it looks good with the new changes. Please send me the TEST deployment as soon as you can so we can UAT in TEST and get it to PROD before 1pm tomorrow

Ready for TEST Deployment 🎉🎉

[Nadin-Nader]

@aishwarya2505 @TracyLinder @Sreelatha-BlazeKannan Deployment has been sent to the CM DevOps Team to deploy to TEST under TASK SCTASK0105643

Status:

Waiting on CM Team to deploy to TEST

Next steps: Deployment to TEST, Stake Holder UAT on TEST and Promotion to PROD

[Nadin-Nader]

@Sreelatha-BlazeKannan @TracyLinder @aishwarya2505 Per George, this has been deployed to TEST.

Status: Ready for UAT and approval on TEST with stakeholder

[aishwarya2505]

Tested 12396668 in TEST and the changes work as expected.

[TracyLinder]

Update

Per @Nadin-Nader , he spoke to stakeholder Maria today and she's changed the AC. As a result, this will not be deployed before the code freeze.

I scheduled a meeting on 11/24 to update the workflow diagram; then we'll update the issue description & AC.

[Nadin-Nader]

We were actually able to get this in to TEST (SCTASK0105801) and to PROD (SCTASK0105802 deployment will be tonight)

[Nadin-Nader]

@TracyLinder @Sreelatha-BlazeKannan @aishwarya2505 Spoke to Maria and she said that it is working perfectly and Thank you for the hard work. Closing card