Details

      Description

      We neglected this aspect so far. Adding a "form-name" attribute to the field element of the lookup fixes it.

      The value of "form-name" attribute must be the name of the "parent form", ie the 1st form (the one with skip-end="true") which precedes the current form (which has skip-start="true").

      If you use a related description field (using the "description-field-name" attribute of the lookup element) you need to put the "form-name" attribute in this field element too.

        Issue Links

          Activity

          Hide
          jacques.le.roux Jacques Le Roux added a comment - - edited

          Fixed in
          trunk r1665535
          R14.12 r1665540
          R13.07 r1665543+1665560
          R12.04 r1665544+1665561

          Show
          jacques.le.roux Jacques Le Roux added a comment - - edited Fixed in trunk r1665535 R14.12 r1665540 R13.07 r1665543+1665560 R12.04 r1665544+1665561
          Hide
          jacques.le.roux Jacques Le Roux added a comment - - edited

          While testing the feature, Pierre Smits wanted to have form-name dynamic by using

          form-name="${name}"

          . Then the form-name attrbute should support FlexibleStringExpander. This could be another Jira...

          Show
          jacques.le.roux Jacques Le Roux added a comment - - edited While testing the feature, Pierre Smits wanted to have form-name dynamic by using form-name= "${name}" . Then the form-name attrbute should support FlexibleStringExpander. This could be another Jira...
          Hide
          pfm.smits Pierre Smits added a comment - - edited

          Having to have the form name hard coded in the field as in:

          <form name="RequestItemProduct" type="single" skip-start="true" skip-end="true">
                  <field name="productId" title="${uiLabelMap.CommonProduct}" form-name="EditCustRequestItem">
                  <lookup target-form-name="LookupProduct" description-field-name="productName" show-description="false"/>
                  </field>
                  <field name="productName" form-name="EditCustRequestItem" position="2"><text read-only="true"/></field>
                  <field name="quantity" title="${uiLabelMap.CommonQuantity}"><text size="10"/></field>
              </form>
          

          leads to a degradation in functionality. Such a form can be used only with one start form.

          With dynamic form building whereby the start-form might be conditionally defined (based on parameter values), the form name required in the lookup fields of the injectable sub-forms should change accordingly.

          Show
          pfm.smits Pierre Smits added a comment - - edited Having to have the form name hard coded in the field as in: <form name= "RequestItemProduct" type= "single" skip-start= " true " skip-end= " true " > <field name= "productId" title= "${uiLabelMap.CommonProduct}" form-name= "EditCustRequestItem" > <lookup target-form-name= "LookupProduct" description-field-name= "productName" show-description= " false " /> </field> <field name= "productName" form-name= "EditCustRequestItem" position= "2" ><text read-only= " true " /></field> <field name= "quantity" title= "${uiLabelMap.CommonQuantity}" ><text size= "10" /></field> </form> leads to a degradation in functionality. Such a form can be used only with one start form. With dynamic form building whereby the start-form might be conditionally defined (based on parameter values), the form name required in the lookup fields of the injectable sub-forms should change accordingly.

            People

            • Assignee:
              jacques.le.roux Jacques Le Roux
              Reporter:
              jacques.le.roux Jacques Le Roux
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development