Siebel Connector for PeopleSoft > Prebuilt Integration Objects > Prebuilt Account Workflows >

Account - Send PeopleSoft Customer


The Account - Send PeopleSoft Customer workflow is used to manage queries from Siebel and writes to an XML file.

Figure 20. Account - Send PeopleSoft Customer Workflow

Click for full size image

Using the two process steps in the above workflow, you can write one or more accounts in the Siebel database to an XML file. The accounts you choose to write to the XML file can be determined by using the Object Id process property of this workflow (Process Properties are discussed below). For example, you can pass the Row Id of the account you wish to obtain into this Object Id parameter. You can do this either programmatically (via Siebel eScript and Data Transformation Engine maps) or via Process Simulator. If you pass a specific value, the account row that matches this row will be returned. If you want all the accounts written to an XML file, leave this Object Id property empty.

Using the XML File Process Property, you can input name and directory location for the XML file. The active fields in the underlying integration object (which is named EAI Account for this workflow) determine the format of the XML file.

Process Properties

The Account Outbound workflow has several process properties. Except for the process property XML File, all others come by default. The XML File process property was created. Of all these process properties, three are a bit more important than others—Object Id, Siebel Message, and XML File.

You can use Object Id to restrict the number of rows returned; leaving it empty will return all the rows. Siebel Message is used to transfer the object related data between workflow steps, in a hierarchical format. And finally, XML File can be used to store the name and location of the XML file to write the results to.

The significance of using Process Properties is that they can be accessed by any workflow step in that given workflow process. In other words, they work as global variables for that entire workflow.

Workflow Steps

This example uses appropriate input arguments for the Write Siebel Message method. Notice that both are process properties. The first argument is File Name. This argument could have been a Literal type instead of being a process property because this variable is not required by other workflow steps.

But this argument makes a process property so that it can be accessed from outside; for example, through another workflow (where this workflow is a subprocess) or through code. Here, you are placing the name of the XML file in this property (for example, C:\AccountOutbound.xml).

The second argument is Siebel Message. The previous workflow step puts the account data into this process property. This workflow step accesses the exact same information (in a hierarchy/property set format), converts it into XML format, and writes it to a file.

This workflow step has no Output Arguments because, once the data is written to an XML file, the job of this workflow process is completed.

This integration involves the following processes:

  1. Query Account from Siebel
  2. In the first step, the Query method of the EAI Siebel Adapter business service is used to get data from the Siebel database. This is a standard business service shipped with the Siebel software. Appropriate values for various parameters must be passed to the Query method.

    As Figure 20 shows, values are passed to two important parameters: Integration Object Name and Object Id. First, a value is passed for the Integration Object Name. This integration object is used to determine which fields need to be queried from the Siebel database. The EAI Siebel Adapter determines this by looking at the various active Integration Components and the active fields within each integration component. As the figure shows, in this case, the underlying integration object is named EAI Account. The contents of this integration object can be seen from Siebel Tools.

    Next, the Object Id value is passed to the method. This property can be used to restrict the account rows written to the XML file. The EAI Siebel Adapter queries using the input parameters and places the output into an output argument named Siebel Message (this is a Process Property), which would then be used in the next workflow step. Siebel Message is a hierarchical data structure that is stored in the memory.

  3. Write Account to XML File.
  4. After data is obtained about a particular account (in the above step), that data is written to an XML file. In the second step, business service named EAI XML Write to file is used. The business service's Write Siebel Message method is used to write the Siebel Message output from the previous workflow step.


 Siebel Connector for PeopleSoft 
 Published: 18 April 2003