Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.2
    • Fix Version/s: 2.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • Application Requirement:
      KS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      dialogResponse needs to default to #form since its always directly on the form. See KS jira:

        Attachments

          Issue Links

            Activity

            Hide
            lsymms Larry Symms added a comment -

            Spoke with Brian Smith about this and he thinks there's a quick fix for this.

            Show
            lsymms Larry Symms added a comment - Spoke with Brian Smith about this and he thinks there's a quick fix for this.
            Hide
            jkneal Jerry Neal (Inactive) added a comment -

            See related Jira, should be done at the same time

            Show
            jkneal Jerry Neal (Inactive) added a comment - See related Jira, should be done at the same time
            Hide
            shahess Shannon Hess added a comment -

            On 2/8/2013, the p:bindingInfo.bindToForm="true" was added to the Uif-DialogExplanation and Uif-DialogResponse beans, which fixes this issue.

             
             <bean id="Uif-DialogExplanation" parent="Uif-InputField" p:propertyName="dialogExplanation"
                    p:bindingInfo.bindToForm="true" p:render="false">
                <property name="control">
                  <bean parent="Uif-TextAreaControl"/>
                </property>
                <property name="cssClasses">
                  <list merge="true">
                    <value>uif-dialogExplanation</value>
                  </list>
                </property>
              </bean>
            
              <bean id="Uif-DialogResponse" parent="Uif-InputField" p:propertyName="dialogResponse"
                    p:bindingInfo.bindToForm="true">
                <property name="control">
                ...
                ...
            
            Show
            shahess Shannon Hess added a comment - On 2/8/2013, the p:bindingInfo.bindToForm="true" was added to the Uif-DialogExplanation and Uif-DialogResponse beans, which fixes this issue. <bean id= "Uif-DialogExplanation" parent= "Uif-InputField" p:propertyName= "dialogExplanation" p:bindingInfo.bindToForm= " true " p:render= " false " > <property name= "control" > <bean parent= "Uif-TextAreaControl" /> </property> <property name= "cssClasses" > <list merge= " true " > <value>uif-dialogExplanation</value> </list> </property> </bean> <bean id= "Uif-DialogResponse" parent= "Uif-InputField" p:propertyName= "dialogResponse" p:bindingInfo.bindToForm= " true " > <property name= "control" > ... ...

              People

              • Assignee:
                shahess Shannon Hess
                Reporter:
                lsymms Larry Symms
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: