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

Enable frontend registry support for application definitions

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      ERM Sprint 112, ERM Sprint 113
    • Development Team:
      ERM

      Description

      Description:

      • Capture and store frontend application that can be referenced by widget definitions and efficiently reused for widget outputs and interactions

      Breakdown:

      • We need to figure out which information we wish to store about frontend operations.
      • Initially I would like to include:
        • A description of all icons - do we need to constrain ourselves to stripes bundle or allow for external icons to be described as well?
        • Descriptions of frontend SAS(Q) filter patterns work, possibly some kind of template?
        • Similarly to the above, lists of resources managed by the entry and templated paths to those.
        • Any information about plugins? - Do these have a separate registry entry?
      • Should these be kept up to date by the stripes bundle itself, what does that interaction look like?

      Development Tasks:

      1. Define registry domain structure
      2. Populate with agreements and licenses frontend data
      3. Consume registry data in dashboard Simple Search widget. Test with
        1. Link to object resource
        2. Link to filtered Search and Sort Query

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                ostephens Owen Stephens
                Reporter:
                jag.goraya Jag Goraya
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases