Using Validation Business Objects

about validation business objects docid 0y8n6cncv7 uueg068u59about pure validation business objects docid 0y8n6cncv7 uueg068u59accessing a validation object docid 0y8n6cncv7 uueg068u59creating a validation business object docid 0y8n6cncv7 uueg068u59adding validation list values docid 0y8n6cncv7 uueg068u59modifying a validation business object docid 0y8n6cncv7 uueg068u59deleting a validation business object docid 0y8n6cncv7 uueg068u59 about validation business objects a validation business object is a business object list that is linked to another object, usually a pick list for example, you can create a list called status to supply a list of possible values to the status field in the order business object these values are applied by the user for each record (via a drop down list) and do not apply globally to the business object the order business object is the validated business object, while the status field contains the status pick list to use a pick list in a validated text field, you must mark the field as unicode also, the data type between the stored field in the named validation list and a validated field must match for example, if the named validation list is defined against a text field, but the user is attempting to use it for a number field, the validation does not work about pure validation business objects pure validation business objects are business objects that are used primarily to drive the drop down fields in other business objects for example, the incidentstatus validation business object supplies the allowable values for the status drop down field for the incident business object pure validation business objects have static record sets; that is, their record sets do not change in the course of normal business logic for example, employee and department are validation business objects, but are not pure validation business objects because their record sets are subject to change as a normal part of business pure validation business objects should not have defined relationships trying to use a relationship defined on a pure validation object is unsupported because the mechanism for copying the data only copies the records in the validation business object, but not the relationship data as well (such as the link table information in the fusionlink table) for example, the values in the team drop down list for the incident business object come from the standarduserteam business object, but because the standarduserteam business object has relationships, it is not a pure validation business object the application only caches pure validation business objects in memory; and not regular business objects as an example, the records in the incidentstatus validation business object are cached, but not the records in the standarduserteam business object one benefit of pure validation business objects is being able to store the record values so that they can be copied over as part of the operations console push in the previous example, if you add new records to the incidentstatus validation business object or update the existing records, these changes can then be captured for later use in the operations console accessing a validation object validation objects shown with a lock icon are default business objects from the configuration console, click build > validation business objects to open the validation business objects workspace click an item from the list to the view its properties creating a validation business object from the configuration console, click build > validation business objects to open the validation business objects workspace click add new\ the application displays the new validation business object page enter information into the fields see creating a business object docid\ prrpnuvje8dmzc oaqymn as a best practice, we recommend creating the pick list before associating it with a validation object see using pick lists docid\ m0dqgjwohw5tbwrbrjumj adding validation list values you can easily add, modify, or delete values from any validation list from the configuration console, click build > validation business objects to open the validation business objects workspace under the values column, click values next to the list to add values for the application displays the values for that validation business object click add the application displays the new dialog box enter a value in the field click save the application adds the value to the list users see the new value when they refresh their windows or when they next log in to edit a value, do the following a click the value from the list b enter the updated value c click outside the text box the application automatically saves the value to delete a value, do the following a hover your mouse over the end of the line b click delete deleting a validation list value c the application displays the delete dialog box d click yes modifying a validation business object from the configuration console, click build > validation business objects to open the validation business objects workspace click an item from the list the application displays the business object page modify the information as needed, as described in creating a business object docid\ prrpnuvje8dmzc oaqymn click save deleting a validation business object you cannot delete default validation business objects (those shown with a lock icon ) use caution when deleting a validation business object business objects that use this validation business object might no longer function as expected from the configuration console, click build > validation business objects to open the validation business objects workspace click the delete icon next to the validation business object to delete the application displays the delete dialog box click yes return to the list view and refresh the window the validation business object no longer appears