Hello dear Appianistes,
I have a gap between how my app reacts in development tools (build) and in the site,
Site :
After using AJOUTER button :
Builder :
Any guesses ?
buttons: a!buttonLayout( primaryButtons: { a!buttonWidget( label: if(ri!isUpdate, "Enregistrer", "Ajouter"), saveInto: { /*sous-periode*/ a!forEach( items: local!sous_periode, expression: { a!save( ri!sous_periode[fv!index]['recordType!{77c00203-ec59-4d91-815a-0f6334649b51}alan_r_sous_periode.fields.{38d14ae2-8fd9-40ee-a277-dbc90afc6266}dateDebut'], local!sous_periode[fv!index]["deb"] ), a!save( ri!sous_periode[fv!index]['recordType!{77c00203-ec59-4d91-815a-0f6334649b51}alan_r_sous_periode.fields.{368c8cd0-aeff-4d35-b85f-e83787ea7fa8}dateFin'], local!sous_periode[fv!index]["fin"] ), } ),
Discussion posts and replies are publicly visible
simonr2949 said:in the site
What exactly does this mean?
Inside the Interface Editor, all rule inputs can store data. When you use that same interface in a process start form or user input task, you have to assign process variables or node-local variables to allow storing data.
Some info here: community.appian.com/.../data-flow-in-process-models
I mean in the 'web site', in the user view.
Yes yes, every thing was working with my 'etapes' (steps) and I did the same to add my 'sous-périodes' my PM isn't the problem I think.. I don't know if I understand your answer correctly,
When starting with Appian, things can be confusing. I had the same problem 15 years ago :-)
In the "Start Form" configuration of the Process Model Properties, make sure to assign all rule inputs from the Interface to a process variable.
Then, in the "Site" object, did you add the interface itself, or the process model as content?
Oh yes ! Sorry I forget to update my "Start Form" it's working now ! The error was baiting me that my code was wrong when it was a problem in the PM, my bad, thanks !
About the site I was not meaning "Site" object so everything is good ! :)
Have a nice day !