IPA queue mappings

Users could create IPA queue mappings in any of the existing queues. If the flow definition needed to be one of the mapping criteria, then it could only be created from the application. Currently, there are three mapping criteria available: Actor, Data Area, and Process.

If no mapping criteria were found for a trigger, it would be sent to the IpaDefaultQueue with the priority of that queue.

However, there might instances of conflicting mappings. For example, there is a mapping that said a workunit triggered by Lawson must have critical priority (Mapping 1), and another mapping that said any workunit triggered for a flow definition called testquery must have low priority (Mapping 2).

Table 1. Mapping 1
Field	Value
Actor	lawson
Data Area
Process
Priority	Critical

Table 2. Mapping 2
Field	Value
Actor
Data Area
Process	testquery
Priority	Low

In this scenario, if a workunit was triggered by Lawson for the testquery flow definition, the mapping with the Actor criteria would take priority over the mapping with the flow definition criteria. Therefore, the workunit would be sent to the queue with critical priority instead of low priority.

If there are conflicting priorities, then the Actor mapping would take precedence, followed by the Data Area mapping, and finally the Process (flow definition) mapping.

This table shows the order of priority based on precedence:


Order	Mapping
1	Priority
2	Actor
3	Data Area
4	Process

Whenever a new mapping is created or an existing mapping is updated or deleted, the mapping validation would be run on all the triggers in the table. This would ensure that the queue definition and priority are adjusted accordingly.

Refer to Infor Landmark Technology System Administration Guide for details.