Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Sprint:
      2021.R5 CloudLink Sprint 3
    • SCRUM Team:
      Globogym Purple Cobras
    • Story Points:
      8
    • Work Type Classification:
      Sustaining

      Description

      We need to update CloudLink Core so that we can:

      • Have another connection string to connect to the Macromatix DB
      • Make use of the existing stored procedures to load all stores in the "CloudLink" zone

      Currently, in the MMS website there is a page called "MMS_Manage_Zones.aspx" where we can assign stores to a zone. We'll need to setup a CloudLink Zone type along with a zone that we can assign stores to

      Upon startup, CloudLink can make use of the connection string and use some of the store procs already available: e.g. "qryMMSEntityZone_ListEntityByZoneID"

      We might have to build a custom stored procedure if there's nothing that will give us exactly what we need

      Some source code to start with
      Branch: WIP Load Stores By Zone

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Gareth.Leibbrandt Gareth Leibbrandt (Inactive)
                Reporter:
                brent.jacobz Brent Jacobz (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 48.5h
                  48.5h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 45h 55m Time Not Required
                  45h 55m

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.