another thought though: since your fields have a default value (0), I think making these field "required" will visually show it, but it won't force the user to change the value of the field.
I guess you could create a loop running through each object, i.e. from 1 thru 13, create a string variable to specify the targeted object and set the mandatory status using the resolveNode property. Something like:for (var i=1; i<=13;i++){ var sTarget = "object"+i; if(this.resolveNode(sTarget).kpi...
I don't know why the avg function would return -0.01 as default, but I think the test you tried is scripted in JavaScript, not in FormCalc and I doubt you can mix both languages in the same event.
Reacting to @radzmar recent comment about scripting a field's visibility instead of setting the visibility in the object properties:I have designed forms that can be either filled in directly in the form or by importing data into the form. The problem I had with that is that importing data would no...
The pages you see on your screenshot are Page1, testpage and Page2:Page2 is hidden due to the following scriptpmp::docReady - (JavaScript, client)Page2.presence = "hidden"; To see Page2, remove that script
Sorry It looks like in the preview, it displays only one of the 2 pages (page2 or test page) … not sure why. so the second page you see in your screenshot is page3 which is still set as positioned, hence the overlapping.
As a general suggestion, I would highly recommend you watch some tutorials on LiveCycle/AEM Designer as there are lots of features that are tricky to figure by yourself and the Adobe documentation tends to be overwhelming considering both its extensive coverage, and its conciseness. They are still v...