Professional Documents
Culture Documents
Overview
Up to now, you've learned to: Define a business object's data structure Define basic business rules for a business object Create a hierarchy of business objects to allow logic reuse via inheritance Control the various stages of a BO's lifecycle
In this section, you'll learn how to use "options" to control a BO's behavior.
Objectives
By the end of this chapter, you will be able to: Understand how certain MO options must be set up in order for core functionality to operate Understand how the framework uses BO options to implement certain types of business rules Understand how implementation teams can use BO options to extend a basepackage BO's business rules Add additional BO (and MO) options Understand how to inactivate base-package plug-ins by setting up MO and BO options
Chapter 8
27-Jul-12
Review Questions
1. If a base-package BO's MO has a status, you can use BO options to make elements required when an object is created. True/False 2. If a base-package BO's MO doesn't have a status, you can use BO options to make elements required when an object is created. True/False 3. When you add a new MO, you'll almost always have to add options to it. True/False 4. If your design adds a new plug-in spot to a BO, you must add an MO option to tell the system about this new system event. True/False 5. An implementation team can add option values to a base-package MO and they will survive future upgrades. True/False 6. An implementation team can add new option types to a base-package MO and they will survive future upgrades. True/False 7. Assume an option value is defined on a parent BO, one of the child BO's can effectively override the option value. True/False