Details
-
Story
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
None
-
-
ERM Sprint 125, ERM Sprint 126, ERM Sprint 127, ERM Sprint 128, ERM Sprint 129
-
Bienenvolk
-
Lotus R1 2022
Description
Purpose:
If the suppress from discovery for an entitlement changes because of a change to the suppress from discovery field on:
- An agreement line
- A PCI
- A PTI
- A TI
the change should be advertised in the entitlement log through a new entry with an eventType of "UPDATE" (or similar)
User story statement(s):
As a consumer of the EntitlementLog,
I want to have the suppressFromDiscovery information
so that I can use it appropriately (e.g. in a union catalogue)
Scenarios:
- Scenario:
- Given an agreement line
- When I edit the "suppressFromDiscovery" field for the agreement line
- Then new entitlementLog entry or entries will be created with eventType of "UPDATE"
- Scenario:
- Given an agreement line which leads to an entitlement for a PCI
- When I edit the "suppressFromDiscovery" field for the PCI
- Then a new entitlementLog entry will be created based on that entitlement with eventType of "UPDATE"
- Scenario:
- Given an agreement line which leads to an entitlement for a PCI for a TI
- When I edit the "suppressFromDiscovery" field for the TI
- Then a new entitlementLog entry will be created based on that entitlement with eventType of "UPDATE"
TestRail: Results
Attachments
Issue Links
- clones
-
ERM-1883 Change to coverage should lead to updated entry in EntitlementLog
-
- Closed
-
- defines
-
UXPROD-2817 ERM Agreements Title addition and removal feed
-
- Closed
-
- relates to
-
ERM-1459 Support a log of resources that have been added/removed from a library collection
-
- Closed
-
-
ERM-1883 Change to coverage should lead to updated entry in EntitlementLog
-
- Closed
-
-
ERM-1884 Populate "suppress" field in EntitlementLog
-
- Closed
-
- requires
-
ERM-1902 Framework for UPDATE entitlement log entry events
-
- Closed
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...