Fix existing secure request workflow issues

Description

  1. Module: mod-tlr
    Action: "Confirm arrival"
    Issue: mod-request-mediated updates the Primary request with real delivery info which triggers the request update event. mod-tlr handles this event and changes Secondary request's delivery info to the real delivery info.
    Solution: When handling a request update event, mod-tlr should not update Secondary and Intermediate requests' delivery info with the info from the event if they already have Interim SP as a pickup location. (TBD) In this case, Interim SP should be updated to Secure SP - CONFIRMED, no need to change Interim SP value.

  2. Module: mod-tlr
    Action: Primary request editing (Secure tenant)
    Issue: mod-tlr ignores Intermediate request when propagating request update from the Primary request.
    Solution: Propagate updates to both Secondary and Intermediate requests.

Environment

None

Potential Workaround

None

Attachments

2
  • 14 Feb 2025, 01:42 PM
  • 12 Feb 2025, 04:27 PM

Checklist

hide

Activity

Show:

Oleksandr Hrusha February 14, 2025 at 1:42 PM

Checked on eureka bugfest , works as expected

2025-02-14_15h41_53.mp4

Oleksandr Hrusha February 12, 2025 at 4:27 PM

What was checked: there was a problem that the primary request displayed a real service point

Checked on eureka snapshot , works as expected, all 3 circulation requests now have “Interim service point”

2025-02-12_18h25_33.mp4
Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Vega

Fix versions

Release

Ramsons (R2 2024) Service Patch #1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 29, 2025 at 2:23 PM
Updated February 14, 2025 at 7:11 PM
Resolved February 12, 2025 at 4:59 PM
TestRail: Cases
TestRail: Runs

Flag notifications