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

KRAD Sampleapp Demo Travel Account Maintenance New Travel Account Type Code lookup doesn't select checkbox on value return

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.4
    • Fix Version/s: 2.4
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-13768Create AFT for Travel Account Bulk Update
      KULRICE-9982Component Library: Travel Account Maintenance, lightbox lookup showing values as editable instead of readonly
      KULRICE-12113Fill AFT Per-Screen Item Gap: KRAD Demo: Travel Account Lookup
      KULRICE-11403Error adding Sub Account to KRAD Demo Travel Account
      KULRICE-10540Demo Travel Account Maintenance Edit Route log inline 404 (KRAD-sampleapp)
      KULRICE-11716Fill AFT Per-Screen Item Gap: KRAD Demo: Travel Account Type Lookup
      KULRICE-11419KRAD Sample Travel App: Move unnecessary screens into their own menu section
      KULRICE-12903AFT Failure DemoTravelAccountMaintenanceNewAft Travel Account Type Code Search icon missing
      KULRICE-8038Travel Account Maintenance (New) account number validation broken and validation message nulled
      KULRICE-12434Create Travel Account Lookup with advanced features
    • Rice Module:
      KRAD
    • Sprint:
      2.4.0-m4 KRAD Sprint 3
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required

      Description

      KRAD Sampleapp
      Demo
      Travel Account Maintenance New
      Lookup Travel Account Type Code
      Click any return value
      Expect appropriate checkbox to be checked, but none are.

        Issue Links

          Activity

          Hide
          Steve Manning (Inactive) added a comment -

          I did a little bit of research on this. I found that if a user goes to the "Travel Account Lookup" in the KRAD sample app, from the lookup screen (http://env14.rice.kuali.org/kr-krad/lookup?methodToCall=start&dataObjectClassName=org.kuali.rice.krad.demo.travel.dataobject.TravelAccount), the user can do a "Travel Account Type Lookup" return the value, and have it correctly populate the radio button. Inspecting the working radio buttons, we see that they look something like this:

          <input type="radio" id="uk9kofn_control_0" name="lookupCriteria[accountTypeCode]" value="CAT" checked="checked" class="uif-verticalRadioControl" data-role="Control" data-control_for="uk9kofn">

          On the non-working "Travel Account Type Lookup" the inspection of the radio buttons (after the lookup has been invoked and the value returned) results in the radio button components looking something like:

          <input type="radio" id="quickfinder1_control_0" name="document.newMaintainableObject.dataObject.accountTypeCode" value="EAT" class="uif-verticalRadioControl required validChar-document.newMaintainableObject.dataObject.accountTypeCode0 error" data-role="Control" data-control_for="quickfinder1" aria-required="true" aria-invalid="true">

          In this case, the user selected "EAT" as the account type code, and all radio buttons have this as their value. A snippet illustrating all three radio buttons with their values set as this is attached to the jira.

          Show
          Steve Manning (Inactive) added a comment - I did a little bit of research on this. I found that if a user goes to the "Travel Account Lookup" in the KRAD sample app, from the lookup screen ( http://env14.rice.kuali.org/kr-krad/lookup?methodToCall=start&dataObjectClassName=org.kuali.rice.krad.demo.travel.dataobject.TravelAccount ), the user can do a "Travel Account Type Lookup" return the value, and have it correctly populate the radio button. Inspecting the working radio buttons, we see that they look something like this: <input type="radio" id="uk9kofn_control_0" name="lookupCriteria [accountTypeCode] " value="CAT" checked="checked" class="uif-verticalRadioControl" data-role="Control" data-control_for="uk9kofn"> On the non-working "Travel Account Type Lookup" the inspection of the radio buttons (after the lookup has been invoked and the value returned) results in the radio button components looking something like: <input type="radio" id="quickfinder1_control_0" name="document.newMaintainableObject.dataObject.accountTypeCode" value="EAT" class="uif-verticalRadioControl required validChar-document.newMaintainableObject.dataObject.accountTypeCode0 error" data-role="Control" data-control_for="quickfinder1" aria-required="true" aria-invalid="true"> In this case, the user selected "EAT" as the account type code, and all radio buttons have this as their value. A snippet illustrating all three radio buttons with their values set as this is attached to the jira.
          Hide
          Steve Manning (Inactive) added a comment -

          This file shows three radio buttons with all of their values set (incorrectly) to be the same.

          Show
          Steve Manning (Inactive) added a comment - This file shows three radio buttons with all of their values set (incorrectly) to be the same.

            People

            • Assignee:
              Jeff Ruch
              Reporter:
              Erik Meade
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Time Spent - 6 hours Remaining Estimate - 2 hours
                2h
                Logged:
                Time Spent - 6 hours Remaining Estimate - 2 hours
                6h

                  Agile

                    Structure Helper Panel