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

Add functionality for custom evaluation via default widgets templates [eDocLite]


    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s:
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-2308Update widgets to support calling two functions when a custom function is passed as a parm to the buttons template.
      KULRICE-2123Modify widgets and/or edoclite1.js to support custom functions on buttonClick
      KULRICE-4809should be able to customize button text in edoclite
      KULRICE-2149Enhance Widgets to render an html id attribute for applicable Edoclite form field types so that prototype and javascript coding is easier/better.
      KULRICE-5408KRMS - Add custom function integration test
      KULRICE-4810edoclite should give message to user when buttons are pressed
      KULRICE-1179Evaluate the work that has already been done on Customizing Doc Searches for how it aligns with this enhancement request
      KULRICE-3794Bug in EDocLite widgets.xml file and inconsistency between DB widgets record and widgets.xml
      KULRICE-5283UIF Framework - Support for custom JSP templates (for group content)
      KULRICE-1982Add parms to widget's page_button to allow 'onClick' events to invoke javascript. Also add a readOnly parm.
    • Rice Module:


      Added code to support the passing of a parameter to default widgets.xml template calls for standard form field definitions. This is helpful in making custom field validation simpler for standard form fields (textarea, textbox, checkbox, radio, select list, etc..).

      This is done by passing a parameter named "customFunction" into the widgets_render template and propagating that parameter down through the respective following template calls. When the actual field is rendered (by input, select, etc..) the value of this parameter is evaluated by an xsl:if statement. If there is a value, the attribute is added onto the rendering line with an event. If no value is found, the attribute is not added and everything proceeds as it did before. (This should not impact previous data/forms).

      Field Types and the associated event handler:
      Textbox: onKeyUp
      Textarea: onKeyUp
      Select: onChange
      Radio: onClick
      Checkbox: onClick
      NOTE: These can be EASILY changed, added, or removed if need be.

      The second issue included in this JIRA is a similar functionality added to the default buttons template. The same basic idea is used there, where you pass a parameter named "fname". When a value is given, the input render replaces the standard onClick="buttonClick(


      )" with onClick="buttonClickFunctionName(


      )" which causes the custom function to fire when it is given. Again, this is ignored if not present so it should not impact previous forms. Note that this utilizes buttonClickFunctionName as implemented in edoclite1.js and referenced in KULRICE-2123

      Both of these changes are included in the widgets.xml file attached to this JIRA.


        Greg Patterson (Inactive) added a comment -

        Completed but not yet committed to the project.

        Greg Patterson (Inactive) added a comment - Completed but not yet committed to the project.
        Craig Solinski (Inactive) added a comment -

        Code has been committed.

        Craig Solinski (Inactive) added a comment - Code has been committed.


          • Assignee:
            Greg Patterson (Inactive)
            Greg Patterson (Inactive)
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Structure Helper Panel