Bookshelf Home | Contents | Index | PDF |
Siebel Assignment Manager Administration Guide > Working with Dynamic Candidates > Process of Defining Dynamic Candidates > Configuring Join Specifications for Dynamic Candidate Object DefinitionsSiebel Assignment Manager supports complex joins to relate base table with other related entities. The Dynamic Candidate Component object properties define the table and column names used when performing a join from the assignment object primary table to the candidate table to retrieve the dynamic candidates. Using the dynamic candidate feature, you can configure Assignment Manager to identify related business entities and retrieve potential candidates from these entities. For example, you use the dynamic candidate feature when:
Because potential assignees for dynamic candidates can be derived from various related business entities, you must configure the relationship between these entities. This task is a step in Process of Defining Dynamic Candidates. Use the following procedure to configure join specifications for dynamic candidates. NOTE: Before you can successfully use join specifications for creating dynamic candidate definitions, you must have a thorough understanding of database administration and how to use Siebel Tools. Also familiarize yourself with the basics of the underlying Siebel Business Applications architecture. For more information, see Using Siebel Tools and Siebel Deployment Planning Guide. To configure join specifications for dynamic candidates
TIP: If Workflow Policy Object is not visible in the Object Explorer, you can enable it in the Development Tools Options dialog box (View, then Options, and then Object Explorer).
Table 42 provides descriptions of some of the Dynamic Candidate Component properties. NOTE: Each dynamic candidate specified can have only one primary dynamic candidate component. |
Siebel Assignment Manager Administration Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |