Previous	Next		Contents	Index	Glossary

Note: When the Workflow Engine encounters an external Java function activity, it places an entry on the 'Outbound' queue. To continue executing the activity, you must run the Java Function Activity Agent, which calls the appropriate Java function and places the result on the 'Inbound' queue. You must then run a background engine to process the 'Inbound' queue and complete the function activity. See: Setting Up the Java Function Activity Agent, Oracle Workflow Administrator's Guide and Setting Up Background Engines, Oracle Workflow Administrator's Guide.

Activity Attributes

• Event--choose the item attribute of type event that contains the event message from which you want to retrieve data.

• Tag--the tag set within the event message from which you want to retrieve data. Specify the tag set in XPath notation. For example, for an XML document containing a purchase order, the XML path for the order number tag could be specified in the following format:

		/order/header/ordernumber

The following example path locates the ITEMNO node on the third line of the purchase order document:

		/order/orderlines/line[3]/itemno

The following example path locates the COST node on the second line of the purchase order document whose currency attribute is set to "AUD." The notation // indicates that the specified node is located among the descendants of the root node.

		//line[2]/cost[@currency="AUD"]

For more information, see the W3C Recommendation XML Path Language (XPath).

• Item Attribute--choose the item attribute of type date, number, or text where you want to store the data. The type of the item attribute must match the type of the data that you want to retrieve.