BusinessEvents: Working with Decision Tables

• Click Add to add rows. Enter the data in the new cells or drag and drop the properties form Argument Explorer.
• Click Fit Content to resize the columns so they fit around the text.
• You can search for certain values by entering text in the Search field.
• Click Show Text button to see the contents of the cell, instead of just the values you are comparing with for the attributes you have dragged to the condition and action areas.
• Drag and drop the catalog functions you see collapsed by default on the right side of the application. Drag and drop them to the function area (marked by the ) or to the cell you are editing. For example, if you want to compare some attribute that is of type integer against the rounded value of "39.99", you could say in one of your conditions "< Math.round(39.99)" by dragging and dropping the Math round function from the Standard Functions
  window and then entering the arguments of that function.
• Right-click on the condition area on the properties you dragged there to take a few actions relating to the column you have clicked on. For example, you can move the column, remove it, or change other field settings.
• Click on the drop-down menu on the properties dragged to either the condition or the action area to filter out which rows to show based on the values. For example, if you want to see just the Account.AccountType where AccountType is "current" and you want to filter out all the other rows that do not have this value, select the "current" value from the drop-down list that will show you all the values you have entered so far in that column.
• Click Remove to delete rows. If you add more rows after this operation, the row IDs are not reused.
• Right-click on column headers and choose Remove to delete any conditions or actions from the table. You cannot remove the last condition column because a minimum of one condition column must exist if you have any action columns. When you remove columns, certain rows may also get merged if they now share the same values in their condition cells. If this happens, if you have non-custom actions and the rows have the same priority, the last row to be merged will have its actions be merged and the others deleted.
• Select Table > Show Property, to see meta-data of the entire decision table. You can only modify the effective date and the expiration date.

Read more...

BusinessEvents: Creating a Decision Table

After successfully logging in to the application, some menu options are enabled depending on the roles that your account belongs to User Roles.

When a business user logs in to the Decision Manager application, the following menu options are enabled:

• Project > Checkout/Update/Commit/Show Status
• File > New/Open/Logout/Exit
• Edit > Select All
• Access menu if you also have the RULE_ADMINISTATOR role

As a business user, you can use Decision Manager to create Decision Tables.To Create a Decision Table

1. Open a decision project.
2. From File menu, select New > Decision Table Rule Function, and choose a name for the Decision Table.
3. Select a Virtual Rule Function that you want to implement from the Project Explorer.
4. Click OK.The arguments of the virtual rule function you are implementing are shown in theArgument Explorer view. Expand the Entities (concepts and events) to see theirproperties from Argument Explorer.
5. Decide on which properties you want to use to make a decision table. Drag and drop those properties onto the Condition or Action area.For example, if the arguments are two concepts called BankUser and Application,you can decide to accept the Application based on a users's age and credit score.In this case, drag and drop BankUser's "age" and BankUser's "creditScore"attributes from the Argument Explorer view to the condition area of the decisiontable. Then, you drag and drop the Application's "status" attribute to the Actionarea.
6. When you are done creating the decision table, click File > Save.

• If two rows end up with the same conditions after you make modifications, they will get merged into one row. All actions will also be merged.
• It is invalid to provide a string property value that starts with an integer (such as "12hello" unless you specifically wrap the value around double quotes.
• Blank cells, or cells that have a * in them, as well as disabled cells are all ignored and automatically treated as true.

Read more...

TIBCO BusinessEvents Resources

Access control is enforced for the TIBCO BusinessEvents resources. There are twotypes of access control modes:

• BusinessEvents Resource: This mode is used for populating the Project Explorer view in Decision Manager. BusinessEvents Resource mode is the default mode.


• Domain Model: This model is used for enforcing the Access Control in domain model editor.

The following allows you to create a new domain model entry for any resource which matches the ID AllP.

Read more...

BusinessEvents: Access Control System Overview

The Access Control System manages the permissions to the users based on their roles. Using the access control system, the IT Administrator can restrict business users from accessing or modifying certain resources of a Decision Project.

Access control is role based. Thus, the users belonging to same role will have same access permissions. One user can play different roles in an organization, so the user's permissions are a unification of the permissions that each role the user belongs to gets.

By default, all permissions are denied. Each of the permissions must be grantedexplicitly. Permissions do not have hierarchies. The order in which permissionsare specified is irrelevant.

A role can have zero or more permissions. Each role is represented by a name.A Permission can have one Action and a resource for which the action applies. For example, an action could be Read, Write, or Send. A resource or entity could be arule, attribute, and so on. For example, you could specify Read permission for allattributes of a particular concept.

All of these ACL settings are specified in the

%rms.proejct.location%/%rms.project.name%/config/%rms.project.name

%.acl file as specified in the be-rms.tra file.

Read more...