What are you looking for?

    Didn't find what you were looking for?

    Extend your Search in Community

    Got any questions?

    We're always happy to help with questions you might have. Contact Us

    Didn't find what you were looking for?

    Extend your Search in Community

    Got any questions?

    We're always happy to help with questions you might have. Contact Us

Maestro Topics

Business Rule Data Object

   MaestroPreviously known as Transact Maestro.  |   Form Builder |  v5.1 & Higher This feature is related to v5.1 and higher.

A Maestro business rule JavaScript requires a data object In computer science, an object can be a variable, a data structure, a function, or a method, and as such, is a value in memory referenced by an identifier. In the class-based object-oriented programming paradigm, object refers to a particular instance of a class, where the object can be a combination of variables, functions, and data structures. In relational database management, an object can be a table or column, or an association between data and a database entity (such as relating a person's age to a specific person). parameter, passed to it on its invocation, to perform a desired action.

In the example below, a change rule has been set on a field named department. This change rule triggers the debugger. The debugger is inspecting the data parameter that has been passed to the change rule and data is the form data object which will eventually become the form XML when passed to Journey Manager. Also, the value variable has been overridden with Sales.

The example below shows the data parameter being passed to a change rule for a repeating field called firstName:

Notice the rule's 'data' parameter in the inspector is the same object as data.$r[data.$i]. This shows that the object data.$r holds all the repeated data fields for a repeat, and the object data.$i is the index of the repeated field occurrence whose rule is executing.  If you are stopped in the rule code of a repeated item in a debugger, enter 'data.$r[data.$i] === data' without the quotes in the console tab, and the result will be true.

In the example below, data.$p is the parent of the repeating object, data.$r is the array of repeating rows, and data.$i is the index of the affected row. data.$p above is the same as the data object in the preceding non-repeat example, since the item whose rule has fired is a member of a top-level repeating item, rather than a nested repeating item. If this item was nested one more level deep, its data.$p would point to its parent repeat instance, and that item's $p (data.$p.$p) would point to the root form data object (Form.data). In this way, you can get access to the full ancestry chain of repeated items.

A 2-level repeat would look like the screenshot below:

Next, learn about business rule item object.


Did this topic provide the information you need or leave you wanting to know more? Is there some way we can make this topic better? Let us know how we can improve this documentation.

Contact Us


Our Community is a dynamic, user-driven source of information that provides a home for sharing Journey platform knowledge where you can ask questions and get answers quickly.

Explore Community


Temenos is committed to supporting our customers with Journey platform solutions installed in the cloud or on premise. Learn more about our Customer Care Team, and its policies, procedures, and processes.

Learn More