• Not defined

      Context:
      Currently the value parsing of KPI reports in DigestService.getKpiValueString is not nullsafe and can lead to NPEs if for some reason the value is null.

      Also, there is an incorrect error log for nonexisting reports in getKpiSummaryDtos.

       

      AT:

      • incorrect error log is removed
      • getKpiValueString  is made nullsafe

       

      Testing notes:

      Unfortunately the NPE cannot be tested as the issue doesn't seem to be reproduceable. 
      The incorrect log can be tested: set up a digest, wait for it to be sent out and confirm that there is no log that claims that a report for a digest could not be found.

       

      This is also backported to 39 and 310 maintenance branches

        This is the controller panel for Smart Panels app

            [OPT-7045] Make KPI value parsing nullsafe

            Helene Waechtler created issue -
            Helene Waechtler made changes -
            Status Original: Triage [ 10612 ] New: Ready [ 10005 ]
            Helene Waechtler made changes -
            Description Original: Context:
            Currently the value parsing of KPI reports in DigestService.getKpiValueString is not nullsafe and can lead to NPEs if for some reason the value is null.

            Also, there is an incorrect error log for nonexisting reports in getKpiSummaryDtos.

             

            AT:
             * incorrect error log is removed
             * getKpiValueString  is made nullsafe
            New: *Context:*
            Currently the value parsing of KPI reports in DigestService.getKpiValueString is not nullsafe and can lead to NPEs if for some reason the value is null.

            Also, there is an incorrect error log for nonexisting reports in getKpiSummaryDtos.

             

            *AT:*
             * incorrect error log is removed
             * getKpiValueString  is made nullsafe

             

            *Testing notes:*

            Unfortunately the NPE cannot be tested as the issue doesn't seem to be reproduceable. 
            The incorrect log can be tested: set up a digest, wait for it to be sent out and confirm that there is no log that claims that a report for a digest could not be found.
            Helene Waechtler made changes -
            Assignee Original: Helene Waechtler [ helene.waechtler ] New: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ]
            Status Original: Ready [ 10005 ] New: In Review [ 10212 ]
            Helene Waechtler made changes -
            Labels New: SUPPORT
            Giuliano Rodrigues Lima made changes -
            Assignee Original: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] New: Helene Waechtler [ helene.waechtler ]
            Status Original: In Review [ 10212 ] New: Rework [ 11413 ]
            Helene Waechtler made changes -
            Status Original: Rework [ 11413 ] New: Ready for Testing [ 10008 ]
            Helene Waechtler made changes -
            Assignee Original: Helene Waechtler [ helene.waechtler ] New: Cigdem Ilhan [ cigdem.ilhan ]
            Cigdem Ilhan made changes -
            Status Original: Ready for Testing [ 10008 ] New: In Test [ 10004 ]
            Helene Waechtler made changes -
            Description Original: *Context:*
            Currently the value parsing of KPI reports in DigestService.getKpiValueString is not nullsafe and can lead to NPEs if for some reason the value is null.

            Also, there is an incorrect error log for nonexisting reports in getKpiSummaryDtos.

             

            *AT:*
             * incorrect error log is removed
             * getKpiValueString  is made nullsafe

             

            *Testing notes:*

            Unfortunately the NPE cannot be tested as the issue doesn't seem to be reproduceable. 
            The incorrect log can be tested: set up a digest, wait for it to be sent out and confirm that there is no log that claims that a report for a digest could not be found.
            New: *Context:*
            Currently the value parsing of KPI reports in DigestService.getKpiValueString is not nullsafe and can lead to NPEs if for some reason the value is null.

            Also, there is an incorrect error log for nonexisting reports in getKpiSummaryDtos.

             

            *AT:*
             * incorrect error log is removed
             * getKpiValueString  is made nullsafe

             

            *Testing notes:*

            Unfortunately the NPE cannot be tested as the issue doesn't seem to be reproduceable. 
            The incorrect log can be tested: set up a digest, wait for it to be sent out and confirm that there is no log that claims that a report for a digest could not be found.

             

            This is also backported to 39 and 310 maintenance branches

              Unassigned Unassigned
              helene.waechtler Helene Waechtler
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: