Uploaded image for project: 'Runtime'
  1. Runtime
  2. RUNTIME-4187

[External disable conditions] review behavior for repeater entries

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 4.9.1, 4.10.0
    • None
    • None
    • None
    • 4.9.1
    • Oui

      Some behaviors are not OK for external disable conditions on repeaters

      • Let's have an external disable condition on an attribute in repeater
      • ex on exhaustive:
        • repeaterMinSize, disable conditions on minsize-geocode
          • type or
          • one on minsize-string
          • another one on minsize-longmult
        • view default-edition
          • put minsize-geocode
          • put minsize-longmult
          • do not put minsize-string
        • columns of search model, add repeaterMinsize with minsize-geocode and minsize-longmult, but not minsize-string
        • Add some entries on an exhaustive content, in order to have
          • some entries with the geocode enabled,
          • and some with the geocode disabled
      • Forms:
        • disable conditions for existing entries are OK
        • move a repeater entry that have the geocode disabled to a position where the actual geocode is enabled
          • the geocode is still disabled => OK
          • modify the longmult of the same entry (but not to match the condition)
            • the geocode is now enabled => KO
        • If the geocode of last entry is disabled
          • remove the entry
          • add a new entry
            • the geocode is disabled => KO
      • Grids:
        • Open the dialog to modify repeaterMinsize entries,
        • geocodes on both entries are modifiables => KO
        • modifiy the one thaht should be disabled, save your modifications
        • The modifications are not taken into account => OK

            cbayle Caroline Bayle
            cbayle Caroline Bayle
            Caroline Bayle Caroline Bayle
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: