Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-5238build agenda tree UI components
      KULRICE-5918styling for selected item in agenda or rule tree is different (incorrect) for the last item in a sibling group
      KULRICE-8270KRMS Agenda Editor: Proposition Tree of Rule does not work properly
      KULRICE-5358Implement cut & paste in agenda editor
      KULRICE-11394DatePicker does not work in a tree.
      KULRICE-13321KRMS agenda editor, field labels not rendered for propositions in edit mode
      KULRICE-9910Agenda editing fails when agenda items already exist
      KULRICE-13320KRMS agenda editor UI handles '>' operator badly
      KULRICE-5712Add status messages on actions that manipulate the agenda tree
      KULRICE-6951Editing an agenda with branching causes foreign key violations on delete
    • Rice Module:
      KRMS
    • Sprint:
      2.4.0-rc1 Sprint 1, 2.4.0-rc1 Sprint 2, 2.4.0-rc1 Sprint 3, 2.4.0-rc1 Sprint 4, 2.4.0-rc1 Sprint 5
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      When editing an agenda, the items in the agenda tree cannot be selected.

      To reproduce:

      1. Go to Rice portal Main Menu tab
      2. In KRMS Rules section, click Agenda Lookup
      3. Click Search
      4. Edit My Fabulous Agenda
      5. attempt to click on any of the agenda items

      Result: nothing is selected after clicking
      Expected: the item that is clicked on will be selected (highlighted) and the Edit button will become active.

        Issue Links

          Activity

          Hide
          Peter Giles (Inactive) added a comment -

          The javascript for agenda item selection is broken due to a change in the rendered output for the hidden data field in the tree node that is supposed to contain the agenda item ID (see the entry in the nodePrototypeMap for AgendaTreeRuleNode in AgendaEditorView.xml). In short, it doesn't anymore.

          It used to be

          <input id="u236_node_0_parent_node_0_parent_node_1_parent_node_0_parent_node_0_parent_root_h0" type="hidden" name="document.newMaintainableObject.dataObject.agendaRuleTree.rootElement.children[0].children[0].children[1].children[0].children[0].data.agendaItem.id" value="T1006">

          and now it is

          <input id="uoms1zk_node_0_parent_node_0_parent_node_1_parent_node_0_parent_node_0_parent_root_h0" type="hidden" name="document.newMaintainableObject.dataObject.agendaItemLine.id" value="">

          In the second case the value is empty.

          Show
          Peter Giles (Inactive) added a comment - The javascript for agenda item selection is broken due to a change in the rendered output for the hidden data field in the tree node that is supposed to contain the agenda item ID (see the entry in the nodePrototypeMap for AgendaTreeRuleNode in AgendaEditorView.xml). In short, it doesn't anymore. It used to be <input id= "u236_node_0_parent_node_0_parent_node_1_parent_node_0_parent_node_0_parent_root_h0" type= "hidden" name= "document.newMaintainableObject.dataObject.agendaRuleTree.rootElement.children[0].children[0].children[1].children[0].children[0].data.agendaItem.id" value= "T1006" > and now it is <input id= "uoms1zk_node_0_parent_node_0_parent_node_1_parent_node_0_parent_node_0_parent_root_h0" type= "hidden" name= "document.newMaintainableObject.dataObject.agendaItemLine.id" value=""> In the second case the value is empty.

            People

            • Assignee:
              Peter Giles (Inactive)
              Reporter:
              Peter Giles (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4 hours Original Estimate - 4 hours
                4h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 4 hours
                1d 4h

                  Agile

                    Structure Helper Panel