Business object application-specific text

The application-specific text in a business object is used to identify where data is located in the application database. This section describes the application-specific text format that the connector expects.

Object application-specific text format

The connector uses application-specific text at the business-object level to determine which PeopleSoft activity the connector uses for that business object. To specify this in application-specific text, use the name-value pair Activity= name. The naming convention for activities is CWbusiness object name. For example, for the Employee business object, the PeopleSoft activity is named CWEmployee. The application-specific text for this is:

[BusinessObjectDefinition]
Name = Psft_Employee
Version = 1.0.0
AppSpecificInfo = Activity=CWEmployee
...

The name parameter in the application-specific text must match the name of the activity in PeopleSoft. This name-value pair is needed only for a top-level business object. The connector also uses application-specific text at the business-object level to determine whether a business object will be processed by the connector. If the AppSpecificInfo field for the business object contains the string NoOp, the business object is not processed.

When using the NoOp string, the Activity name-value pair also needs to be specified. In this case, the Activity name-value pair precedes the NoOp string and is delimited by a colon. For example:

[BusinessObjectDefinition] 
Name = Psft_Department 
Version = 1.0.0 
AppSpecificInfo = Activity=CWDepartment:NoOp 
... 

Attribute application-specific text format

The connector uses attribute application-specific text to retrieve keys for child objects in hierarchical business objects.

As part of the connector installation, message definitions that support business object/verb combinations are imported into the PeopleSoft system. These message definitions can contain one or more special fields that correspond to attributes in a top-level business object. Each special field is associated with PeopleCode that gathers the keys to child objects.

When the connector receives an event notification and queries for the complete set of data for a business object, the PeopleCode executes to dynamically assemble the child keys in the special fields. The connector then retrieves the value of each special field, which is a list of child keys, into the attribute corresponding to the special field. The connector can parse the list to identify the specific key for a particular attribute in a child object. The content of the special fields is not stored in the PeopleSoft database.

The following illustration shows example parent and child business objects and the format of the application-specific text. The Psft_Employee parent business object includes the attribute OtherPhoneKeys, which corresponds to the special field defined in the message definition for this business object. The child object includes the name of the special attribute in application-specific text for the key attribute. The connector identifies the key for the child object attribute from within the application-specific text.




When modifying business objects for the connector, key attributes in child objects must have application-specific text that points to a special attribute in the parent object.

Verb application-specific text format

The connector does not currently use the application-specific property for verbs. Leave this field blank when creating business object definitions.

Copyright IBM Corp. 1997, 2003