|Bookshelf Home | Contents | Index | PDF|
Assignment objects contain a lock assignment feature that, when activated by checking the Lock Assignment column on the assignment object's list applet in Siebel Tools, prevents Siebel Assignment Manager from assigning or reassigning a position or candidate to that object. You can use this feature to exclude an object (such as Account or Opportunity object) from being reassigned by Assignment Manager. By setting the column defined in the Exclude Column for the assignment object, Assignment Manager excludes (ignores) the object for assignment.
The Lock Assignment parameter for activity objects is, by default, set to TRUE. This setting does not allow Assignment Manager to assign these objects. Therefore, Assignment Manager does not assign activity records.
However, the Field Service Activity object is the one exception and is, by default, available for assignment (the Lock Assignment parameter is set to FALSE). Other activity objects must have the Lock Assignment parameter set to FALSE or NULL for assignment to occur. (The lock assignment feature for activity records, except those for Siebel Field Service, defaults to Y.)
The behavior for the Field Service Activity object is due to a setting in the Post Default Value property for the Action business component's Assignment Excluded field (Business Component, then Field, then Assignment Excluded). The value in the property is:
Expr: "If ([Class] = LookupValue(""FS_ACTIVITY_CLASS"", ""Field Engineer Activity"") OR [Class] = LookupValue (""FS_ACTIVITY_CLASS"", ""Repair Activity"") OR [Class] = LookupValue(""FS_ACTIVITY_CLASS"", ""Preventive Maintenance""), ""N"", ""Y"")"
|Siebel Assignment Manager Administration Guide||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|