Uploaded image for project: 'ERM Platform'
  1. ERM Platform
  2. ERM-1884

Populate "suppress" field in EntitlementLog

    XMLWordPrintable

Details

    • ERM Sprint 125, ERM Sprint 126, ERM Sprint 127, ERM Sprint 128, ERM Sprint 129
    • Bienenvolk
    • Lotus R1 2022

    Description

      Purpose:

      In the entitlement log, the "suppress" field should be populated based on on the "Suppress from discovery" field on the entitlement, PCI and Title instance. If any of these are "true" then the "suppress" field should be "true" OTHERWISE it should be false

      User story statement(s):

      As a consumer of the EntitlementLog,
      I want to know if the entry should be suppressed from any discovery layer
      so that I can use it appropriately (e.g. in a union catalogue)

      Scenarios:

      1. Scenario:
        • Given an agreement line with "suppressFromDiscovery" == true
        • When I view the EntitlementLog entry or entries (in the case of a package) which has been created because of that entitlement
        • Then the "suppress" field will be "true"
      2. Scenario:
        • Given an agreement line which leads to an entitlement for a PCI with "suppressFromDiscovery" == true
        • When I view the EntitlementLog entry which has been created because of that entitlement
        • Then the "suppress" field will be "true"
      3. Scenario:
        • Given an agreement line which leads to an entitlement for a PCI for a TI with  "suppressFromDiscovery" == true
        • When I view the EntitlementLog entry which has been created because of that entitlement
        • Then the "suppress" field will be "true"

      Dev task breakdown

      This line in the view file will need updating with logic that takes into account the suppress fields on all levels.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                ostephens Owen Stephens
                ostephens Owen Stephens
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases