Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-6509

C8SaaS Email address recipient validation does not return list of invalid emails

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • backend
    • None
    • Not defined

      Brief summary of the bug. What is it ? Where is it ?

      In C8SaaS, the list of recipients for an alert is validated by the BE. If one of those addresses doesn't belong to a member of the Cloud organisation, the following error is returned by the API:

      {     
  "errorCode" : "invalidAlertEmailAddresses",
  "errorMessage" : "Users with the following email addresses are not available for receiving alerts: [asd@asd.asd]",
  "detailedMessage" : "Users with the following email addresses are not available for receiving alerts: [asd@asd.asd]",
  "reportDefinition" : null
}

      Error response to allow FE to translate the error message have to have a property called invalidAlertEmails but it is missing from the response now. this new property should be a string of comma joined email addresses

        This is the controller panel for Smart Panels app

          1. screenshot-1.png
            screenshot-1.png
            609 kB

            [OPT-6509] C8SaaS Email address recipient validation does not return list of invalid emails

            Omran Abazeed added a comment -

            This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10592. Please use this link for any future references and continue any discussion there.

            Omran Abazeed added a comment - This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10592 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              joshua.windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: