Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-5835

changes to a field populated by fieldAttributeQuery.returnFieldMapping doesn't trigger progressive rendering based on that value

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-b4, 2.0
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      In the KRMS agenda editor there is a progressive render on the Type field that is conditional on the value of the agenda.contextId value which is set by the fieldAttributeQuery on the Context field when leaving that field. Tabbing out of the Context field populates the agenda.contextId but doesn't trigger the progressive render of the Type field.

        Attachments

          Issue Links

            Activity

            Hide
            gilesp Peter Giles (Inactive) added a comment -

            Per our conversation in the standup today, I tried making the Context ID a visible field and it still doesn't trigger the progressive disclosure when it's populated by the fieldAttributeQuery.

            Show
            gilesp Peter Giles (Inactive) added a comment - Per our conversation in the standup today, I tried making the Context ID a visible field and it still doesn't trigger the progressive disclosure when it's populated by the fieldAttributeQuery.
            Hide
            gilesp Peter Giles (Inactive) added a comment -

            Hey Jerry, I'm adding a patch that goes against version 23769 of AgendaEditorView.xml (which is the HEAD at the moment), all the patch does is comment out the hidden agenda.contextId field, and add a visible one. With the patch applied:

            1. Open the Agenda Editor link
            2. Set the namespace of the new agenda to 'Kuali Rules Test'
            3. Set the input labeled 'Context' to the value 'Context1' and tab out of the field.
               

            Result: the agenda.contextId field gets populated by the fieldAttributeQuery on the contextName field, but the progressiveRender on the agenda.typeId field doesn't get triggered. Even if you then put your cursor in the input labeled 'Context ID' and then tab out, the progressive render won't occur.

            To see what I think should happen:

            1. Open the Agenda Editor link
            2. Set the namespace of the new agenda to 'Kuali Rules Test'
            3. Set the input labeled 'Context ID' to the value 'CONTEXT1' and tab out of the field.
               

            Result: the field for agenda.typeId will progressively render.

            I created this scenario to test the hypothesis that the field needed to be visible for the progressive render to work. It would be great to fix that, but it would be better still to also enable progressive render based off the value of a hidden field (so it would work without the patch applied).

            Show
            gilesp Peter Giles (Inactive) added a comment - Hey Jerry, I'm adding a patch that goes against version 23769 of AgendaEditorView.xml (which is the HEAD at the moment), all the patch does is comment out the hidden agenda.contextId field, and add a visible one. With the patch applied: Open the Agenda Editor link Set the namespace of the new agenda to 'Kuali Rules Test' Set the input labeled 'Context' to the value 'Context1' and tab out of the field.   Result: the agenda.contextId field gets populated by the fieldAttributeQuery on the contextName field, but the progressiveRender on the agenda.typeId field doesn't get triggered. Even if you then put your cursor in the input labeled 'Context ID' and then tab out, the progressive render won't occur. To see what I think should happen: Open the Agenda Editor link Set the namespace of the new agenda to 'Kuali Rules Test' Set the input labeled 'Context ID' to the value 'CONTEXT1' and tab out of the field.   Result: the field for agenda.typeId will progressively render. I created this scenario to test the hypothesis that the field needed to be visible for the progressive render to work. It would be great to fix that, but it would be better still to also enable progressive render based off the value of a hidden field (so it would work without the patch applied).
            Hide
            jcoltrin Jessica Coltrin (Inactive) added a comment -

            double-tagging with 2.0.0-b3 for review.

            Show
            jcoltrin Jessica Coltrin (Inactive) added a comment - double-tagging with 2.0.0-b3 for review.
            Hide
            jcoltrin Jessica Coltrin (Inactive) added a comment -

            Closing since these items are now in the release notes.

            Show
            jcoltrin Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

              People

              • Assignee:
                jkneal Jerry Neal (Inactive)
                Reporter:
                gilesp Peter Giles (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: