Stefan Cameron on Forms
Building intelligent forms using Adobe LiveCycle Designer

Designer ES2 Scripting Reference

This is one of the references I find the most useful when writing scripts and it’s now available for Designer ES2.

What’s more, you can now find all of the ES2 Developer and Programmer documentation all in a single place just like all ES2 documentation (which includes the Dev and Prog docs from the former link). Great sites to bookmark and nice to finally have it all in one spot!

This all comes to you due to the recent LiveCycle Developer Center site refresh in conjunction with the recent release of LiveCycle ES2. Check it out!

Posted by Stefan Cameron on November 12th, 2009
Filed under Designer,LiveCycle,Scripting
Both comments and pings are currently closed.

2 Responses to “Designer ES2 Scripting Reference”

  1. Duane on November 16th, 2009

    Hi Stefan,

    Wondering if you can point me in the right direction (or take up my cause with the XFA/XTG team).

    The resolveNode() method has one of two behaviors:

    xfa.resolveNode(somExpression) will start at the root node and search downwards through the xfa tree to find the node matching somExpression.

    myStartNode.resolvenode(somExpression) will start at myStartNode and search UP through the xfa tree.

    It would be very useful to extend the resolveNode function to allow the search to begin at myStartNode, and search DOWN through it’s children.

    I realize this could be accomplished by using .nodes, and recursively iterating through all children while doing a comparison by Name, but I imagine that a built-in resolveNode function would be far quicker than this approach for large forms (would also help if resolveNodes is also covered, as a custom solution to that with .nodes would require each match to be stored to an array, and could get messy).

    Has this been covered before by anyone? Any chance of seeing this in the next XFA version?

    Thanks

  2. Stefan Cameron on November 19th, 2009

    Duane,

    In XFA SOM Expressions, there’s a “..” syntax that might actually do what you want. You can use this in conjunction with resolveNode(). See “Selecting Descendants At Any Level”, page 103, in the XFA Specification Version 3.0 (though this syntax has been supported in XFA for a long time now).