Error message for a Request Form that fails to submit is confusing

XMLWordPrintable

    • 7
    • Severity 3 - Minor
    • 88
    • Warranty

      Issue Summary

      If you configure a validator on the create step for a Request Type, if the validator fails, the generic message that is included with any error message from the validator is confusing and misleading. This error message is presented followed by any custom error message returned from the validator:
      "The request type associated with this email account has validation rules applied to one of the fields. You can either create a new request type for this email account or remove validation from the field."

      Steps to Reproduce

      1. Create a Request Type that can be submitted via the JSM Portal.
      2. Add a validator to the workflow on the create step for this Request Type.
      3. Specify an error message in the validator configuration
      4. Attempt to submit a request via the Portal ensuring that the validator will fail

      Expected Results

      The error message that you note in the validator configuration should be shown to the user on its own.

      Having the default message around failing to submit the Request followed by the error message the user specifies is okay, but the default message should be made more clear. Perhaps something like "Failed to submit request type" – then the user defined message. The current message related to "email accounts" is quite confusing.

      Actual Results

      The following message is displayed first "The request type associated with this email account has validation rules applied to one of the fields. You can either create a new request type for this email account or remove validation from the field." then your custom error message.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Abhinav Pande
              Reporter:
              Andy Rusnak
              Votes:
              19 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: