Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-4368

On the Group Document, if you forget to enter description, when you submit and get the validation errors it messes up the membership list

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.2.1
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-6971When copying a Term Specification, categories are not copied and you get a validation error when trying to submit on Context
      KULRICE-11043Person document goes into exception when attempting to deactivate a Person with a single group membership
      KULRICE-4137Validations and labels for group qualfications not getting correctly picked up
      KULRICE-7930Person document is allowing add of role memberships with bad information
      KULRICE-4575IM Person doc should only allow editing of direct group memberships
      KULRICE-6933If you enter more than one delegation for an individual they all become the same as the last entered.
      KULRICE-6819Error on view of Group Maintenance Document when group is assigned to a group
      KULRICE-9477Freemarker error with column calculation and submit of maintenance document
      KULRICE-4154Group document loses last added member when encountering an error
      KULRICE-8712Kim group document returns exception when submitting group with empty namespace

      Description

      Essentially, it reduces the membership list to one person. To reproduce a case:

      1) Go to group lookup
      2) Lookup WorkflowAdmin
      3) Click "Edit"
      4) Hit the submit button without entering a description
      5) Notice there is only one user in the member list

        Activity

        Hide
        Saurabh Ajmera (Inactive) added a comment -

        Greg Patterson added a comment - 17/Mar/10 06:30 PM
        Shannon,

        Have you done any research on this? I was going to start looking into it if you hadn't gotten around to it yet?
        [ Show » ]
        Greg Patterson added a comment - 17/Mar/10 06:30 PM Shannon, Have you done any research on this? I was going to start looking into it if you hadn't gotten around to it yet?

        [ Permalink | Edit | Delete | « Hide ]
        Shannon Hess added a comment - 17/Mar/10 06:33 PM
        No, i haven't looked into this yet.
        [ Show » ]
        Shannon Hess added a comment - 17/Mar/10 06:33 PM No, i haven't looked into this yet.

        [ Permalink | Edit | Delete | « Hide ]
        Shannon Hess added a comment - 19/Mar/10 12:19 AM
        I fixed the problem, testing locally, and commited. I didn't deploy it, thinking it could just go out during the next deploy.

        Determined the problem was in IdentityManagementGroupDocumentAction.java, so I put it in src-patched. Switched the call to the super.execute so that it occured after the member table render.

        KualiTableRenderFormMetadata memberTableMetadata = groupDocumentForm.getMemberTableMetadata();
        if (groupDocumentForm.getMemberRows() != null)

        { memberTableMetadata.jumpToPage(memberTableMetadata.getViewedPageNumber(), groupDocumentForm.getMemberRows().size(), groupDocumentForm.getRecordsPerPage()); }

        /**

        • Begin IU Customization
        • 03/18/2010
          *
        • Moved the following line to prevent the member table from being cut off when a validation error occurs.
        • It used to be before the member table was rendered. JIRA EN-1532.
          *
          */

        ActionForward forward = super.execute(mapping, groupDocumentForm, request, response);

        /**

        • End IU Customization
          */

        refer: https://uisapp2.iu.edu/jira-prd/browse/EN-1532

        Show
        Saurabh Ajmera (Inactive) added a comment - Greg Patterson added a comment - 17/Mar/10 06:30 PM Shannon, Have you done any research on this? I was going to start looking into it if you hadn't gotten around to it yet? [ Show » ] Greg Patterson added a comment - 17/Mar/10 06:30 PM Shannon, Have you done any research on this? I was going to start looking into it if you hadn't gotten around to it yet? [ Permalink | Edit | Delete | « Hide ] Shannon Hess added a comment - 17/Mar/10 06:33 PM No, i haven't looked into this yet. [ Show » ] Shannon Hess added a comment - 17/Mar/10 06:33 PM No, i haven't looked into this yet. [ Permalink | Edit | Delete | « Hide ] Shannon Hess added a comment - 19/Mar/10 12:19 AM I fixed the problem, testing locally, and commited. I didn't deploy it, thinking it could just go out during the next deploy. Determined the problem was in IdentityManagementGroupDocumentAction.java, so I put it in src-patched. Switched the call to the super.execute so that it occured after the member table render. KualiTableRenderFormMetadata memberTableMetadata = groupDocumentForm.getMemberTableMetadata(); if (groupDocumentForm.getMemberRows() != null) { memberTableMetadata.jumpToPage(memberTableMetadata.getViewedPageNumber(), groupDocumentForm.getMemberRows().size(), groupDocumentForm.getRecordsPerPage()); } /** Begin IU Customization 03/18/2010 * Moved the following line to prevent the member table from being cut off when a validation error occurs. It used to be before the member table was rendered. JIRA EN-1532. * */ ActionForward forward = super.execute(mapping, groupDocumentForm, request, response); /** End IU Customization */ refer: https://uisapp2.iu.edu/jira-prd/browse/EN-1532

          People

          • Assignee:
            Saurabh Ajmera (Inactive)
            Reporter:
            Saurabh Ajmera (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel