[CIRC-1084] Stop periodic execution of age to lost processes Created: 15/Feb/21  Updated: 22/Apr/21  Resolved: 22/Apr/21

Status: Closed
Project: mod-circulation
Components: None
Affects versions: None
Fix versions: 20.0.0

Type: Task Priority: TBD
Reporter: Marc Johnson Assignee: Marc Johnson
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-3013 Schedule execution of age to lost pro... Closed
Relates
relates to CIRC-1057 SPIKE: Aged to lost process needs to... Closed
Sprint: Prokopovych - Sprint 108, Prokopovych - Sprint 111, Prokopovych - Sprint 109, Prokopovych - Sprint 112, Prokopovych - Sprint 110
Story Points: 2
Development Team: Prokopovych
Tester Assignee: Holly Mistlebauer

 Description   

In order to allow organisations to schedule age to lost processes more specifically than a fixed period, the system should not schedule them using an _okapi timer

Endpoints Involved

  • /circulation/scheduled-age-to-lost
  • /circulation/scheduled-age-to-lost-fee-charging

Scope

  • Create a new interface for these endpoints (including RAML files and JSON schema)
  • Define permissions to protect each endpoint
  • Remove these endpoints from the _timer interface

Remarks

  • In order to avoid any unnecessary loss of service in the hosted reference environments, this work needs to be coordinated with FOLIO-3013 Closed


 Comments   
Comment by Marc Johnson [ 11/Mar/21 ]

Holly Mistlebauer Please can you check that the age to lost processes work as expected on the snapshot environment, following them being FOLIO-3013 Closed

Comment by Marc Johnson [ 12/Apr/21 ]

Holly Mistlebauer Have you had chance to check the age to lost processes on the hosted reference environments?

Comment by Marc Johnson [ 22/Apr/21 ]

Holly Mistlebauer I'm moving this to done on the assumption that you have tested the age to lost processes on snapshot since this change was made

Generated at Thu Feb 08 23:24:59 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.