Chapter Eight

Building Actions Using the Tango Builders

How the Tango Builders Work in Application Files

The Tango builders help you create and generate a sequence of actions to perform specific tasks. The builders are added to an application file in exactly the same way you add any other action.

Once you add a builder and configure it, the actions the builder generates are inserted automatically into the application file. Builder information is saved in the application file format, making it cross-platform capable. This means you can use any application file containing a builder across all platforms.

Tango Editor provides two builders.

• The Search Builder builds the actions required to perform a search of database records and to update and delete them.

For details about how to configure the Search Builder, see "About the Search Builder"

• The New Record Builder builds the actions required to add a new record to a database.

For details about how to configure the New Record Builder, see "About the New Record Builder"

The topics covered in this chapter include:

• adding a builder to an application file
• generating builder actions
• details about the actions generated by the builders.

[back to top]

Adding a Builder to an Application File

With a new or existing application file open, you add a builder in the same way you add an action, that is, you drag the builder icon from the Actions bar into the application file window.

When you drag either of the builder icons into an application file window, the corresponding builder window opens. For example, if you drag the Search Builder icon from the Actions bar into an open applicile, the Search Builder window opens so you can immediately set Search Builder options.

In the application file window, the corresponding builder icon appears with a default name, just like with actions. The default name for the Search Builder is "Search_Builder" and for the New Record Builder, "Record_Builder".

Note: Tango Editor can properly process one Search Builder and one New Record Builder in the same application file. If you want to use multiple builders of the same type in a single file, you must handle them using If actions and additional request arguments.

For more information, see "Conditional Action Execution (If Action)".

If you add a builder to an application file that already contains the same builder using the default name, Tango adds a number to the default name and increments it by one for each subsequent addition, for example, "Search_Builder1", "Search_Builder2", and so on.

Note: The title of the builder window is in the same form as an action window, <File name> : <Builder name>.

Within the application file, a builder behaves exactly like an action group. That is, it contains actions that can appear in expanded or collapsed form. In the picture on the previous page, the Search Builder icon represents a group, but the group is empty until its actions are built. Tango Server ignores unbuilt builders.

[back to top]

Building the Actions

Once you have entered all the relevant information in the builder window, you can generate the actions.

To build Search or New Record actions in an application file

1. Open a builder window (if it is not already open), for example:
2. Click Build Actions.

   The builder checks to see if you have entered all the information required to build the actions.

   • If you have not, an error message appears and the build process stops.
   • If you have, it builds the actions required to perform the task.

On completion, the actions appear in the builder group.

You can view the hierarchy of a builder in an application file. Click either the plus sign (+) or minus sign (-) to expand or collapse the builder group accordingly.

When building actions, the builder replaces any existing actions in the group:

• If the builder group is empty, the actions are inserted into the builder group.
• If the builder group only contains the actions that were generated by the builder and those actions have not been modified, the new actions replace the old actions within the builder group.
• If there are actions in the builder group that the builder did not generate, or the actions in the builder group have been modified, a message box appears.
• To replace all actions in the builder group with the new actions, click Yes.
• To stop the build action, click No.