-
Notifications
You must be signed in to change notification settings - Fork 2
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
RW Permit Forms Update Request to show Comments on All RW permits (SS) (On PROD) #1918
Comments
Have 8 subtypes on the RW folder, only 1* shows the comment field in the Property and Street information when it is printed out for permit applicants. These can be important details such as "Singular lane closed, not entire road." It's not high priority, there are a ton of workarounds and this might be taken care of by V7. *Maybe OSE's does too; not sure; they might not need it |
Have been changes to the permit form itself; matter of getting it into production. |
Populate Property and Street information free form comments into the existing report: Folder Type = RW (Right of Way Use Permit): Subtype = Parking Spaces (50535) Subtype = Temporary Right of Way Use Permit (50500) |
Scheduled meeting for Tuesday the 16TH of March at 2pm to go over this a bit more |
@TracyLinder updated Acceptance criteria from the my meeting with Paloma. Moving to Backlog |
@TracyLinder @Nadin-Nader |
@Nadin-Nader The reports are updated with the minor updates and tested on TEST. Ready for UAT. Thanks. Meanwhile I have raised SCTASK0322425 - for copying the rpt files in C:\reports on DEVserver so that the changes reflect in permit portal reports, too. |
Checked the Service request and it has not been deployed. I have changed the priority to level 3 |
ROW Review - Approved for PROD 🎉 |
@Nadin-Nader Submitted SCTASK0324563 for PROD deployment. Thanks. |
@TracyLinder can you UAT this on PROD? Subha is saying the report is correct but the configuration may be off |
How to Test on PROD:
|
Sent Kyle a message to UAT this on PROD |
@SubhaShroff Kyle UATd this and it is not approved on PROD: |
Today(6/27/2023) Swapna redeployed the EX, DS and RW permit reports on PROD. Kyle will be testing it tomorrow morning on PROD. |
@SubhaShroff Here is Kyles Response: [10:48 AM] N, Nadin Hi. Ok Kyle got back to me and said the following: [10:46 AM] K, Kyle Morning Nate. Finished testing those three reports. We shouldn't need to roll back the changes as the report format isn't messed up as it was before. But unfortunately the RW-TURP and EX reports don't reflect what was approved in AMANDA Test. [10:46 AM] K, Kyle For whatever reason, only the RW-Film report worked out correctly. |
@Nadin-Nader I got in call with Swapna, and got the rpt files in the right place. And with her help I tested and here are the downloaded pdf files(look right ones) for the same RSNs Kyle tested this morning. Please inform him. Thanks. |
@SubhaShroff Kyle has approved this one on PROD. |
As a ROW Permit Tech, it would be helpful to have the "Comments" and "Date" fields from the "Property & Street Information" tab on the printed Permit.
Acceptance Criteria:
Update all RW permit forms to incorporate the property & Street info tab (free form) Comments and Date field.
The 3 reports updated are:
TURP free-form info fields to include/exclude:
Existing RW form/reports:
Folder Type = RW (Right of Way Use Permit):
SubType = Film (50505)
Report = Film Closure Permit ROW (50509)
SubType = Parking Spaces (50535)
Report = Parking Permit (50512)
SubType = Temporary Right of Way Use Permit (50500)
Report = Temp Use Permit ROW Use (50511)
SubType = Street Event (50510)
Report =
SubType = Street Vendor (50530)
Report =
SubType = Valet Operator (50515)
Report =
SubType = Valet Parking Annual (50525)
Report =
SubType = Valet Parking Temporary (50520)
Report =
4/7/2023
On ROW-AMANDA-DTS Review Call, decided the following:
Request Date: 2018-11-29 16:28:00
Request ID: DTS18-103015
DTS URL: https://atd.knack.com/dts#service-requests/view-issue-details/5c0067f6253cc617b53b9c78
Migrated from atd-amanda #33
The text was updated successfully, but these errors were encountered: