RuleInput, multidropdown

RE: RuleInput, multidropdown

Rao2022 — Fri, 01 Jul 2022 15:32:22 GMT

We are currently using 21.4.

RE: RuleInput, multidropdown

Mike Schmitt — Fri, 01 Jul 2022 15:21:37 GMT

If you're in Appian 22.2 already, you could try using the "Sync Records" smart service node to force syncing of the child element. Otherwise I'm unsure - my assumption so far was that the Write to DSE Node caused syncing to happen, but I'm unsure how nested CDTs are handled there.

RE: RuleInput, multidropdown

Rao2022 — Fri, 01 Jul 2022 14:52:29 GMT

Hi Mike,

One strange issue which I am facing is, the RecordType which I am using to refer Child CDT is not getting synced once the data is saved through Parent CDT.

If I ran DataSync, manually then I was able to see in the front-end.

Any tips please.

Thanks.

RE: RuleInput, multidropdown

Rao2022 — Tue, 28 Jun 2022 13:42:17 GMT

Thank you so much for all your explanations. I really appreciate.

RE: RuleInput, multidropdown

Mike Schmitt — Tue, 28 Jun 2022 13:40:01 GMT

You can always off-shift your editable grid rows into a local variable instead of directly reading/writing to the Rule Input - in that case you'd declare a "blank" one initially in the local variable definition, then in the "submit" button you'd add an a!save() statemen that mirrors the value of the local variable into the rule input.

RE: RuleInput, multidropdown

Rao2022 — Tue, 28 Jun 2022 00:47:10 GMT

Thanks for your reply.

I don't user input task. I am attaching the SAIL form to the process start node.

Not sure how I can achieve.

RE: RuleInput, multidropdown

Mike Schmitt — Mon, 27 Jun 2022 13:36:12 GMT

You would need to populate it in-process prior to your user input task. Though I don't think it should really be necessary to have a "default row" - just validate that the users add at least one.

RE: RuleInput, multidropdown

Rao2022 — Fri, 24 Jun 2022 23:21:52 GMT

Hi,

Thanks for providing details explanation.

Is there any way we can get a default row in this editable grid. If we try to use ruleInput "ri!parentCdt" for the gird rows, we are not getting default row until we click "New Field" link.

Any idea on this.

RE: RuleInput, multidropdown

Mike Schmitt — Fri, 24 Jun 2022 15:07:53 GMT

Here's a 100% generic form relying on a generic, relatively-freshly-created parent/child CDT pair, which handles the "rows of child CDT per parent row based on multi dropdown value" concept.

a!formLayout(
  label: "Simple Submit form",
  
  contents: {
    a!gridLayout(
      label: "test grid",
      headerCells: {
        a!gridLayoutHeaderCell(label: "label"),
        a!gridLayoutHeaderCell(label: "multiple")
      },
      rows: a!forEach(
        ri!parentCdt,
        a!gridRowLayout(
          contents: {
            a!textField(
              value: fv!item.parentText1,
              saveInto: fv!item.parentText1
            ),
            
            a!multipleDropdownField(
              value: property(fv!item.nestedElement1, "int1", {}),
              saveInto: {
                a!save(
                  fv!item.nestedElement1,
                  a!forEach(
                    save!value,
                    {
                      int1: fv!item,
                      text1: "active"
                    }
                  )
                )
              },
              choiceValues: {1, 2, 3},
              choiceLabels: {1, 2, 3}
            )
          }
        )
      ),
      addRowLink: a!dynamicLink(
        label: "Add",
        saveInto: a!save(
          ri!parentCdt,
          append(
            ri!parentCdt,
            {
              parentText1: "",
              nestedElement1: {}
            }
          )
        )
      )
    )
  },
  
  buttons: a!buttonLayout(
    primaryButtons: {
      a!buttonWidget(
        label: "Submit",
        submit: true()
      )
    }
  )
)

RE: RuleInput, multidropdown

Mike Schmitt — Fri, 24 Jun 2022 14:43:49 GMT

If the child CDT is nested in the parent CDT, you can save directly into its value(s) in the parent row of the editable grid by saving into "fv!item.childCdtPropertyName". That would require one and only one a!forEach level in the saveInto of the multiple dropdown field - looping over every value currently in the "save!value" of the dropdown, and initializing a child CDT entry for it. In this manner you should be able to base the Editable Grid rows directly on the Rule Input CDT and skip the local dictionary stage.

RE: RuleInput, multidropdown

Rao2022 — Fri, 24 Jun 2022 14:34:34 GMT

I have crated appian data type "ALineOfBusiness" with lobkey as an arry, then it created a another table "ALineOfBusiness_lobkey".

After words, I have created respective rule inputs. But, still I was unable to save multiple lobkeys against each Attorney.

RE: RuleInput, multidropdown

Mike Schmitt — Fri, 24 Jun 2022 14:30:17 GMT

I think you will need to simplify this somewhat. At the moment you have a whole 3(!!) levels of nested a!forEach statements, just in the circled portion - you shouldn't need nearly this many, IMHO.

Also: you might consider making the new "aLineOfBusinessLobKey" CDT a child (nested) CDT of your original one. I don't do this very often but this is probably a good use case for that - it would simplify the linking/writing of foreign keys to the child table values at write-time, as far as I remember.

RE: RuleInput, multidropdown

Rao2022 — Fri, 24 Jun 2022 14:20:27 GMT

Hi,

Thanks for your advise. To make it simple, I am trying using the below steps.

Step#1 Created 2 tables ALineOfBusiness & ALineOfBusiness_lobkey (t.txt)

Step#2 Created a data types for each of the above defined tables.

Step#3 Created a separate rule inputs for each of those tables.

I got struck at fitting data into a rule inputs. (sail.txt).

community.appian.com/.../t.txt

community.appian.com/.../8053.sail.txt

RE: RuleInput, multidropdown

Mike Schmitt — Fri, 24 Jun 2022 13:52:36 GMT

If you need the "lobkey" field to be multiple in the context of any single item with the primary key "alobkey", then to store this in the database you'd need to make a secondary linked table, having a many-to-one relationship with the "attourneylineofbusiness" table. This is because a SQL table doesn't handle nesting within individual columns of a single table.

If your need is more low-key, then an alternate way to handle this would be to create a column (let's call it "lobKeyJsonString", TEXT type, and within that, you can store a JSON string which is the result of wrapping your selected "lob key" entries first in a simple array and then converting to a JSON string. that would look something like this:

a!multipleDropdownField(
  label: "LOB" & fv!index,
  labelPosition: "ABOVE",
  placeholder: "Select a Line of Business",
  choiceLabels: index(local!lineOfBusiness, "lobname", ""),
  choiceValues: index(local!lineOfBusiness, "lobkey", ""),
  value: a!fromJson(a!defaultValue(fv!item.lobKeyJsonString, "[]")),
  saveInto: {
    a!save(
      fv!item.lobKeyJsonString,
      a!toJson(save!value)
    )
  },
  required: true
)

RE: RuleInput, multidropdown

Rao2022 — Fri, 24 Jun 2022 01:20:44 GMT

When I try to create lobkey as an array, appian is trying to create one more new table.

Do I need to create another new ruleInput with referring to newly crated table?

RE: RuleInput, multidropdown

Rao2022 — Thu, 23 Jun 2022 22:50:33 GMT

Please find the below attached AttorneyLineOfBusiness CDT image.

Also, my both dropdown values are fixed. Values inside the dropdown won't change.

RE: RuleInput, multidropdown

Mike Schmitt — Thu, 23 Jun 2022 21:07:40 GMT

What is the CDT definition for the "attourneyLineOfBusiness" rule input? Is the "lobkey" property single or multiple?

It looks like every time the multiple dropdown is changed (regardless of the row) you're attempting to overwrite the value of "ri!attourneyLineOfBusiness" with a copy stored in the local!attourneyLOB dictionary where the "lobkey" property is actually multiple values. If your CDT doesn't have that field defined as an array, then it simply won't work. I'd also caution that this might not be the best approach for storing multiple row-related values, though i suppose it could work with some fixes to your existing code (i'd suggest fixing the indentation in your a!forEach loops in your saveInto and consider whether you need to list the "lobkey" property name quite so many times, for one...)