Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: CFA 2021R1
    • Component/s: None
    • Labels:
      None

      Description

      Configuratoin
      • There is no configuration specific to this feature
      Testing notes
      • From CFAMX-12068
      • After testing this on JAT, I can confirm that the Backplane /Core/Api message appears to be delayed by 30 seconds. I opened multiple browsers on the desktop and iPad and verified that all the counts were synchronized and on JAT, almost instantaneously. After applying the count in one browser, the other browsers posted the message that the count was submitted. There was only one count in the database that was updated by multiple browsers. The count pending icon in the menu was reset. I recycled the app pools on JAT and all the web pages refreshed to it's original state successfully while counting.

      Deployed to Production as a part of 2020R4

      Story

      As a development team I would like to evaluate how we use SignalR and refactor some process-heavy stored procedures used by Counts. This will help performance and uptime.

      Details

      1. Investigate the best way to use SignalR:
        1. Timeouts - Confirm SignalR fails after "X" failed connections
        2. Reduce the amount of times that SignalR reaches out to the database.
      2. Update stored procedures to improve performance for users who may be working in the same count. Reduce the amount of database interactions.
      3. Update when Count data is loaded. Should Count data all be loaded when the user logs in or at some time after as the user interacts with inventory counts or at sometime in between?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                will.englefield Will Englefield (Inactive)
                Reporter:
                jason.powell Jason Powell
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

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