Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-15193

CloudLink - Retrieve and set Radiant Pos Name and Pos Polling Id for Message Queue Message

    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 4
    • SCRUM Team:
      Globogym Purple Cobras
    • Story Points:
      5
    • Work Type Classification:
      Sustaining

      Description

      Currently, the MSMQ message is constructed, and then the "POS Type" and "Pos Polling Id" are hardcoded.

      We need to either:

      • Load this from Mx (Get "Radiant" Details from tbPollPos)
        OR
      • Have a config in CFA Message Processing Service Configuration

      This probably won't be changing too much, so this could well just be a config:

      • PosName: "Radiant"
      • PosId: 1

      Update

        Attachments

          Issue Links

          implements

          Feature Request - CFAMX-14120 CloudLink - MVP

          • Major - Major loss of function.
          • Open
          There are no Sub-Tasks for this issue.

            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 - 14.5h Original Estimate - 14.5h
                  14.5h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 14h 35m
                  14h 35m

                    PagerDuty

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