About TIBCO iProcess Client

The TIBCO iProcess Client is the single focal point for defining and managing procedures.

The TIBCO iProcess Client consists of:

• The Work Queue Manager
• The Procedure Manager

The Work Queue Manager displays user's queues and work items and the Procedure Manager displays all of the procedures currently available.

From the Procedure Manager, you can:

• create and edit procedures. The TIBCO iProcess Modeler is started from theTIBCO iProcess Client.
• organize and manage your procedures as a hierarchical structure of procedure libraries, in the same way as, for example, you manage files and directories.

Read more...

Integrate your own custom functions with TIBCO BusinessEvents

TIBCO BusinessEvents allows you to write your own custom functions in Javaand add them to the function registry, making them available from within thefunction registry along with the prepackaged functions in the rule editor.The steps below summarize the tasks required to integrate your own customfunctions with TIBCO BusinessEvents:

1. Write your custom static function in Java and compile it.
2. Create functions.catalog, an XML file that makes it possible to access yourcustom functions from the functions registry within the rule editor. The XMLcan also include information for a tool tip for each function.
3. Create a .jar file that includes your .class file and functions.catalog.
4. Add the location of the .jar file to the class path for the BusinessEventsServer and Workbench. Also add locations for any dependent classes.

Read more...

BusinessEvents: Validating a Decision Table

Validate the decision table before testing or committing it to RMS. To validate,from Table menu, select Validate. If there are any access control violations orsyntax errors in the tables, they are shown in the Problems View tab at the bottomof the application. Take corrective actions and then validate the table again untilall errors are resolved.

NullPointerExceptions are silently ignored when a condition throws such anexception because you passed a null String to a function that does not check fornull, or because you accessed a property of a null contained concept(parent.child.property and child is null).

If a condition table cell is empty, it is skipped and thus considered to be evaluatedas true.

While working on the decision project, you can create multiple virtual rulefunction implementations by creating multiple decision tables. However, before committing the decision project to RMS, you should only commit one decisiontable per virtual rule function. During testing you can have multiple tables so youcan decide which ones to deploy to the engine and test. However, if you commitall implementations, only the last one will take effect if all of them are deployed.

Read more...

BusinessEvents:Importing a Decision Table from a Microsoft Excel File

You can import data from a Microsoft Excel file to create a decision table. For some examples see BE_HOME/DecisionManager/examples/ExcelFiles.

To import data:

1. Open the Decision Project.
2. From File menu, select Import. A browse window is displayed.
3. Click Browse to select the Microsoft Excel file to import, and name your decision table.
4. Select the virtual rule function you want to implement with your decision table, and click OK.The data imported from the Microsoft Excel file is saved to the decision table and you can continue modifying the data or add new data.

For custom conditions, and custom actions to be imported from Excel, mark the header names as "CustomCondition" and "CustomAction" respectively.

Read more...