Uploaded image for project: 'Providence'
  1. PROV-2807

Required fields that are set as required through different channels display error messages separately

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects versions: None
    • Fix versions: 1.7.7
    • Components: None
    • Labels:
      None

      Description

      There are several ways to make fields required including:
      -labels & idno in app.conf
      -min characters on a metadata element
      -min relationships on a relationship bundle

      Each of the error messages for these requirement approaches come through separately, meaning first you receive notice that a record can't be saved because of min characters, then on the next attempt to save you are alerted about labels/idno and then on a third attempt at save the relationship minimum error is triggered. Ideally all of these errors would be served together on the first attempt at save.

      Additionally, if a relationship type restricted field (for example, Related Donor) is set to have minimum relationships of 1 but another (for example, Related Creator) is open the error message isn't specific enough. It says: There must be at least 1 relationship for entities. Can this error message take the custom field label, ie. "There must be at least 1 relationship for Related Donor" in order to disambiguate?

        Attachments

          Activity

            People

            • Assignee:
              Seth
              Reporter:
              Julia Weist
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Due:
                Created:
                Updated: