Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Sizing and Platform Requirements
  9. Application Components
  10. IDD Security Configuration
  11. Data Security
  12. Example Role-Based Security Configuration
  13. Data Masking
  14. Siperian BPM Workflow Engine
  15. Locale Codes
  16. Troubleshooting
  17. Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Automatic Task Assignment

Automatic Task Assignment

Automatic task assignment is controlled through a server daemon that runs as part of the Informatica MDM Hub.
The frequency with which this runs is controlled by the value of the sip.task.assignment.interval property in cmxserver.properties. By default, this is set to 0, meaning that the daemon is disabled. It should only be enabled if you are running IDD applications and require task assignment. To enable the daemon, set sip.task.assignment.interval to a value in minutes. A value of 1 will cause the daemon to run once a minute. This daemon has two jobs:
It will assign any tasks that have no owner (null rowid_user) as configured in the task assignment configuration of the IDD application.
It will examine all match table entries associated with a configured subject area's primary table and create tasks to assign to available IDD application users.
An
available user
(a) has fewer than the configured maximum number of tasks currently assigned to them, and (b) is assigned the role specified in the task assignment configuration. You can configure the maximum number of tasks that can be automatically assigned to an IDD application user by specifying the sip.task.maximum.assignment property in the cmxserver.properties file. The default maximum number of tasks to assign per user is 25.
When tasks are automatically assigned, IDD application users from the configured role are selected for task assignment in a round-robin fashion until there are no more users who have fewer than the maximum allowed tasks assigned. Each time the assignment daemon runs, it will assign any unassigned tasks that it can. If there are not enough users to receive all unassigned tasks, there might be unassigned tasks remaining after the daemon runs (which will be assigned once space becomes available in a target IDD application user's task queue). When automatic task assignment is occurring, the IDD application user who receives a specific task cannot be predicted with certainty. If a task needs to be assigned to a specific user, then manual assignment should be used.

0 COMMENTS

We’d like to hear from you!