Constructing Non-Persistent Dynamic Rules › Non-Persistent Dynamic Decision Tables › Constructing Decision Table Actions › Multiple Domain Action (MDA) Actions

Multiple Domain Action (MDA) Actions

This type of action is the most complex. First, each MDA Action selector must be created as an instance of the DIMember class. It is then necessary to create a list of pointers to these instance that describes the set of actions making up the MDA Action. To designate a selector cell with no value, include a pointer with the value of NULL in the list.

To describe an MDA action row that looks like the following example

Use the list (pSetStatus, NULL, pSoundAlarm, pSoundAlarm), where each pointer points to the appropriate DIMember instance.

Multiple Domain Action actions require two pieces of information:

• A description (a user chosen name for the MDA Action)
• The list of selectors (pointers to domain interface actions)

Again, should any Action require an instance binding, including those domain interface members created as selectors of an MDA Action, the binding must be established during this Action construction phrase or passed as an argument in the non-persistent decision table posting method, see ValueAction Selector Format.

The above procedure must be repeated for each Action in the decision table.