Bookshelf Home | Contents | Index | PDF |
Siebel Developer's Reference > Business Component Classes > CSSBCActivity Class > Dependencies and Limitations for the CSSBCActivity ClassThis topic describes dependencies and limitations for the CSSBCActivity class. Fields That the CSSBCActivity Class RequiresActivities and the calendar require the following fields:
Table 4 describes the fields that the CSSBCActivity class requires.
Date Fields That the CSSBCActivity Class RequiresActivities and calendar items depend on date fields. An action class uses a predefined validation that you cannot configure. It does this to make sure that the date that the Planned Completion field contains occurs after the dates that the Planned fields contain. The Validation or Validation Message properties of these fields does not specify this validation. You can write a script that configures a custom message and more restrictive validation on these fields. To capture updates to these fields and to return a custom message, you can use the BusComp_PreSetFieldValue event for the message. Any other validation that you write in the BusComp_PreSetFieldValue event for these fields must be different from or more restrictive than the validation that the classes specify. You cannot use a script to override or make the validation less restrictive. Siebel CRM runs the validation that the classes specify after the BusComp_PreSetFieldValue event finishes running. For more information about these date fields, see the topic about how Siebel CRM validates start and end dates in Configuring Siebel Business Applications. How an Applet Class Determines Whether or Not the CSSBCActivity Class Is RequiredIf the Class property of an applet contains one of the following values, then the CSSBCActivity class is required:
|
Siebel Developer's Reference | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |