Siebel Business Process Designer Administration Guide for Financial Services > Predefined Business Services > Predefined Business Services >

Data Transfer Utilities

This business service allows you to transfer data from a source business component to a destination component. For example, a user can enter data in one view, then use a toolbar command to navigate to another view. Data entered in the first view will be automatically entered in the second view.

Data Map Objects

Data map objects indicate the data that is being transferred from the source business object to the destination business object. You can use the Application Administration > Data Map Administration screen to define data map objects. Only Siebel administrators should have access to this screen. Data map objects are described in Table 98.

Table 98. Data Map Objects
Object
Description
Name
The name of the data map object. You should enter a unique name.
Source Business Object
The name of the source business object. You must define this name in the Siebel Repository file.
Destination Business Object
The name of the destination business object. You can specify the same business object as both source and destination business object.
Inactive
Check this box to make the data map object inactive.

TIP:  Data map objects are cached in memory. Whenever you make changes to an existing data map object, click the Clear Cache button to refresh the cache so that your changes appear.

Data Map Components

Data map components define the mapping at the child business component level. Each data map object can contain multiple data map components. You can arrange data map components in a parent-child hierarchy, but you must specify a parent for all except one data map component. The parentless data map component is called the root data map component. Data map components are described in Table 99.

Table 99. Data Map Components
Component
Description
Name
The name of the data map component. You should enter a unique name for each data map component in a data map object.
Source/Destination Business Component
The name of the source or destination business component.
If you specify a parent for this data map component, you must define this business component in the Siebel repository file as a child of the source or destination business object to which the parent data map component is mapped.
Parent
The name of the parent data map component.
If you specify a parent, the parent is mapped to particular source and destination business components. You must map the child data map component to a child of those source and destination business components.
If you do not want to specify a parent, enter "Null" to indicate that this is the root data map component. Each data map object can have only one root data map component.
Inactive
Check this box to make the data map component inactive.

Data Map Fields

Data map fields define the field-to-field mapping. Data map fields are described in Table 100.

Table 100. Data Map Fields
Field
Description
Source Field
The name of the field from which data will be transferred. You can transfer either:
  • The field value that is defined for the source business component in the Siebel repository file.
  • The result of a calculated expression. A calculated expression must include at least one of these characters:
  • [ ] Evaluated at the source. The result of the evaluation is transferred at run time.
  • ( ) Evaluated at the source. The result of the evaluation is transferred at run time.
  • " " Evaluated at the source. The result of the evaluation is transferred at run time.
  • + Evaluated at the source. The result of the evaluation is transferred at run time.
  • { } Evaluated at the destination business component.
Destination Field
The name of the field to which data will be transferred. The destination field value can be either:
  • The field value that is defined for the source business component in the Siebel repository file.
  • The result of a calculated expression. If the destination field value is a calculated expression, then:
  • The source field value is transferred to the destination field. The destination field's calculated expression is evaluated at run time.
  • The result of the evaluation is transferred back into the source field. The destination business component is not updated.
Key
Matches destination records with source records.
For example, the Update operation updates the record in the destination business component whose key destination fields all match those of the corresponding source fields.
Each data map component should contain at least one key field. If the destination business component is populated with an associated list business component, at least one key field is required.
Source /Destination Multi-Value Link
This link indicates that the source and destination fields are multi-value fields.
Data is transferred from one multi-value field to another by dividing data map fields into several subcomponents. All entries with the same source and destination multi-value link constitute a subcomponent. You should specify a key for each subcomponent.
Note: Data transfer from a multi-value field to a single value field is not allowed.

Data Transfer Utilities Methods

The Data Transfer Utilities business service methods are described in Table 101.

Table 101. Data Transfer Utilities Methods and Arguments
Method
Description / Arguments
Data Transfer
Transfers data from the source business component to the destination business component.
Input Arguments:
  • Data Map Object (Required): The name of the data map object that defines the mapping.
  • Operation (Required): Valid entries include Insert, Update, Delete, and Upsert.
  • Goto View (Optional): The name of a view that appears to users after the data transfer operation.
  • Option (Optional): A text field that allows you to specify additional options for the operation. The only option that is currently supported is NewBusObj. NewBusObj allows you to instantiate a new destination business object.
Output arguments:
  • MockMethodReplied: Y or N.
FAFireEventxxx
A hidden method that you can use to create a toolbar command. "FAFireEventxxx" invokes the method "EventMethodxxx" on the primary business component of the active view. "EventMethodxxx" triggers the event manager, which invokes either a workflow or a business service.
GetActiveViewProp
Auxiliary function to retrieve the active view's properties. It does not take any input arguments.
Output arguments:
  • Business Object: The name of the business object.
  • View: The name of the active view.
  • Screen: The name of the active screen.
  • Thread Applet: The name of the thread applet.
  • Is Administration Mode: Y or N
  • View Mode Code: an integer representing Siebel view mode.
  • 0: SalesRep View
  • 1: Manager View
  • 2: Personal View
  • 3: AllView
TryMockMethod
Advanced auxiliary function for administration of tool bar button workflow. It does not take any input arguments.
Output arguments:
MockMethodReplied. Y or N.


 Siebel Business Process Designer Administration Guide for Financial Services 
 Published: 22 May 2003