A Imaging Solution Tables

This appendix describes the AXF and business application configuration tables used for the Imaging solution, including commands, web user interface tools, and example implementations. This appendix covers the following topics:

A.1AXF Tables For the Imaging Solution

This section describes the following AXF tables.

Note:

Running an AXF and an Oracle BPM Worklist session at the same time can result in the session first opened ending. For example, launching an AXF session with an Oracle BPM Worklist session open ends the BPM Worklist session.

This conflict occurs because console session information is retained in browser cookies whose names are domain specific, but default to the same initial value. To prevent this conflict, set cookie names unique for each domain. To set cookie names, use the console on the advanced section of the Domain Configuration/General page.

Note:

If modifying AXF table values in a running system, either execute Clear DB Cache from the Driver page or restart the AXF application within the Application Server for the changes to take effect. For information about the Driver page, see "Verifying the AXF Installation with HelloWorld" in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.

The diagram that follows displays the AXF configuration tables and their relationships.

The fully qualified class name in which the command is defined. This class is loaded and the execute() method representing the command is executed. For information about a specific task, see the specific task listed in Section A.3.

A.1.3.2Example Implementation

This example shows commands defined for the Invoice Processing solution.

Used to implement the command. Specify the complete package name of the implementation class. This namespace path provides the physical Java class to instantiate. The namespace also differentiates commands within the same solution namespace.

PARAMETER_KEY

Specifies the parameter key to use in the AXF command. For parameter details, see the specific command or web tool:

A.1.4.2Example Implementation

This example defines the StartInvoiceProcessing command for the Invoice Processing solution. The first row specifies that the task list be displayed, using the RedirectCommand and corresponding URL. The remaining rows call the task list (in the CONFIGURATION_NAMESPACE column) and define its behavior.

A.1.5 AXF_ACTION_MENU Table

Use this table to insert and customize an action menu on an AXF web page such as the Task Viewer or Task List screen. A common use is to display a Task Actions pane in the Task Viewer for users to click action links related to the displayed task, as shown in Figure A-2. Use the AXF_ACTIONS Table to define a specified menu's actions.

A.1.5.1 Column Description

Table A-9 Column Description for AXF_ACTION_MENU Table

Column

Description

MENU_ID

Specifies a primary key to the AXF_ACTIONS Table, identifying the menu in which to place menu actions.

Specifies where on the screen the menu is displayed and its type. (LEFT_SIDEBAR displays a side pane leftmost on the screen.)

TASK_FLOW_ID

Specifies the active task flow with which to associate the menu. For example, to add a side menu to a task list display, specify a value of axf-tasklist-tfd, which identifies the page that shows the menu.

Defines the order in which the menu is displayed when multiple menus are set for display.

A.1.5.2 Example Implementation

This example table implements a pane entitled Task Actions in the left side of the Task Viewer for the Invoice Processing solution.

Table A-10 Example AXF_ACTION_MENU

MENU_ID

DISPLAY_TEXT

MENU_TYPE

TASK_FLOW_ID

VIEW_ID

SOLUTION_NAMESPACE

MENU_ORDER

0

Task Actions

LEFT_SIDEBAR

axf-taskviewer-tfd

null

InvoiceProcessing

0

A.1.6 AXF_ACTIONS Table

This table defines the task actions used in an AXF solution. You can display action menus on AXF web pages such as the Task Viewer page (see Section A.2.2) or a Task List (see Section A.2.1). This table links to the AXF_COMMANDS Table.

A.1.6.1Column Description

Table A-11 Column Description for AXF_ACTIONS Table

Column

Description

DISPLAY_TEXT

Specifies the name of the action (link, for example) in the pane.

COMMAND_NAMESPACE

Specifies the command called as a result of the action, as defined in the AXF_COMMANDS Table.

MENU_ORDER

Specifies the display order of the action in the pane.

ELEMENT_TYPE

Specifies how to render the action on the page, where LINK displays an HTML link.

ACTION_HANDLER

Determines who/what handles the action. COMMAND is the currently available handler.

Note: If left (null), this value defaults to COMMAND.

REQUIRES_CONVERSATION

Specifies whether the action requires a conversation ID to already be initialized.

A.1.7.2Example Implementation

This example follows an XPATH attribute specified for an AssignProcessingGroupEdit command in the AXF_SOLUTION_PARAMETERS table. The PARAMETER_VALUE column contains an XPATH: prefix, indicating that the attribute value comes from the AXF_XPATH_ATTRIBUTES table.

Fields not shown: SOLUTION_NAMESPACE=InvoiceProcessing

Table A-14 Example AXF_SOLUTION_PARAMETERS Table

COMMAND_NAMESPACE

CONFIGURATION_NAMESPACE

PARAMETER_KEY

PARAMETER_VALUE

AssignProcessingGroupEdit

oracle.imaging.axf.web.EnumerationPicker

ATTRIBUTE_NAME

XPATH:InvoiceProcessing_ProcessingGroup

In the AXF_XPATH_ATTRIBUTES table that follows, the corresponding XPATH column displays the XPATH expression used to locate the value in the payload.

Table A-15 Example AXF_XPATH ATTRIBUTES Table

ATTRIBUTE_KEY

XPATH

InvoiceProcessing_ProcessingGroup

//task:processingGroup

In the AXF_NAMESPACES table that follows, the XMLNS_URI column displays where within the XML file to locate the processingGroup task information.

A.2.1Task List Web Tool

The Profile list uses standard BPEL views to restrict the task list view based on user/group, BPEL Process versions, and BPEL payload attribute values. (Use the BPM Worklist application to create views and share them with other users or groups.)

Users can select a task from the table by clicking its View Task link, which retrieves the workflow task from a specified BPEL server and process, claims it and displays it in the Task Viewer. After users complete the selected task, they return to the Task List.

When autotask mode is selected, the AXF solution automatically claims and opens tasks as users complete them, until all of a user's tasks have been processed or the user chooses to stop processing tasks by returning to the Task List. Users activate autotask mode by clicking Auto Task.

Users can release an assigned task by clicking the Release button. The task is then released back into the pool of available tasks. If the user clicks Release but did not previously acquire the selected task, a message indicates that the task cannot be released.

You can configure the Task List to include a side pane action list with links.

A.2.1.1Task List Parameters

Specify a COMMAND_NAMESPACE to execute when a user clicks the View Task link on the Task List web page.

CMD_AUTO_TASK_BUTTON

Specify a COMMAND_NAMESPACE to execute when a user clicks the Auto Task button on the Task List web page.

NO_OF_LINES

Specify the maximum number of tasks to display before displaying multiple pages.

VIEW_LIST

Specify the list of views (defined in the Human workflow system) displayed to users in the Profile field.

DEFAULT_VIEW

Specify the default profile. If used with the VIEW_LIST parameter, this value must also be listed in the VIEW_LIST value.

A.2.1.2Example Implementation

This example defines the StartInvoiceProcessing command for the Invoice Processing solution. The first row uses the Redirect Command to display the task list. The remaining rows define the task list's behavior.

A.2.2Task Viewer Web Tool

The AXF Task Viewer web tool is a reusable web interface that displays the content associated with a Human Workflow Task. In a typical configuration, a business user displays the Task Viewer on one monitor, and keys values shown in the image into a business application on another monitor.

If configured, users can select actions in the side Task Actions pane, which invoke a solution's AXF commands. You enable the Task Actions pane in the AXF_ACTION_MENU Table, configure the action links to invoke AXF commands in the AXF_ACTIONS Table, and the commands themselves in the AXF_COMMANDS Table. If autotask mode is selected, users disable it by returning to the Task List, typically by clicking a Return to Task List link in the Task Actions pane.

If configured, users can view a Summary section that displays metadata values about the task. You configure these items for display in the AXF_METADATA_BLOCKS Table and AXF_METADATA_ATTRIBUTES Table. You can also configure the section's title and the task payload values displayed.

If configured, users can view a Comments section that displays comment fragments and provides icons for displaying full comments or adding them for the task. You configure comments for display in the AXF_METADATA_BLOCKS Table.

Specifies the metadata label displayed to users in the metadata section (for example, Status in a Summary section).

When a dynamic data table is specified, this label becomes a column header.

ATTRIBUTE_KEY

This attribute is updated in the BPEL task when a user clicks the OK button on the Task Viewer page. The attribute value is either a system attribute name (see Section A.3.6.2) or prefixed with XPATH, which uses the XPath table to find the value. Only XPATH is supported for a dynamic data table.

If the IS_XPATH value is TRUE, the attribute_key value comes from the AXF_XPATH_ATTRIBUTES Table and is the XPATH to update the value in the task payload.

IS_XPATH

If TRUE, the attribute value comes from the XPATH in the BPEL payload. If FALSE, the value comes from system attributes or flex field attributes.

DISPLAY_ORDER

Specifies the order in which the metadata label/value display in the metadata section.

A.2.3Enumeration Picker Web Tool

The Enumeration Picker web tool enables users to select a choice from a list of values configured in AXF tables. For example, the Enumeration Picker shown in the graphic that follows displays a Processing Group dropdown field containing North, South, East, and West values.

After the user selects a value, the value is updated into the BPEL payload before the configured command executes, typically a command to return to the Task Viewer or to complete the command.

Specify the literal value to store in the payload. This value is often the same as the DISPLAY_LABEL's value, but can differ.

LIST_ORDER

Specify the order in which to list the value in the picker field.

Example Implementation

This example defines the items for the ProcessingGroups, SupplierMaintenanceCodes, SpecialistExceptionCodes, and RescanCodes enumeration pickers defined in the AXF_ENUM_TYPES Table.

Table A-30 Example AXF_ENUM_ITEMS Table

ENUMERATION_ID

ITEM_ID

DISPLAY_LABEL

ATTRIBUTE_KEY

LIST_ORDER

1

1

North

North

1

1

2

South

South

2

1

3

East

East

3

1

4

West

West

4

2

5

No Supplier

No Supplier

1

2

6

No Supplier Site

No Supplier Site

2

3

7

Duplicate Invoice

Duplicate Invoice

1

3

8

Invalid Invoice Number

Invalid Invoice Number

2

3

9

No PO

No PO

3

3

10

Invalid PO

Invalid PO

4

3

11

PO Overbill

PO Overbill

5

4

12

Poor Image Quality

Poor Image Quality

1

4

13

Pages Out of Order

Pages Out of Order

2

4

14

Pages Missing

Pages Missing

3

4

15

Other

Other

4

A.2.4Identity Picker Web Tool

The Identity Picker web tool enables users to select one or more users or groups from an identity store configured for BPEL. Typically, a related action is taken after choosing an identity; for example, a task is assigned or delegated. The action to take after selecting an identity is configured in the AXF_SOLUTION_PARAMETERS Table.

Note:

The command updates the task payload when the user clicks OK. The BPEL process is responsible for using this information to delegate the task.

Note:

The Filter and Search Attribute settings use the BPEL Worklist views configuration. To change these settings, use the BPEL Workflow application.

A.2.4.1Identity Picker Parameters

Specify the command (COMMAND_NAMESPACE) to execute when a user clicks the Cancel button on the Identity Picker page.

CMD_ON_OK

Specify the command (COMMAND_NAMESPACE) to execute when a user clicks the OK button on the Identity Picker page.

IDENTITY_FILTER

Define how the identity picker searches, where:

USER: The picker searches for user information defined in BPEL.

GROUP: The picker searches for group information defined in BPEL.

Note: Specify USER or GROUP for a command. To allow both search types, create an additional command that uses the other type to open the identity picker. For example, you might create AssignByGroup and AssignByUser commands.

IDENTITY_ATTRIBUTE

This attribute is updated in the BPEL task when a user clicks OK on the Identity Picker page. The Attribute value is a constant as defined under System Attributes; see Section A.3.6.2.

If the value has an XPATH: prefix, then the value comes from the AXF_XPATH_ATTRIBUTES Table and it is the XPATH to update the value in the task payload.

A.2.4.2Example Implementation

This example shows an InvoiceApprovalEdit command that searches for user information stored in BPEL, and updates the BPEL task using an XPATH variable.

A.3.1Open Task Command

This command acquires a task from BPEL (human work flow) for a given task ID; the specific task is likely selected from the task list. If the task can be acquired by the user, the command obtains the details of the task and displays the specified web page.

A.3.4Complete Task Command

The Complete Task command updates the list of attributes and outcome for a specified task in the human task workflow. This command also takes the parameters defined for the Update Task Command.

In addition, the Complete Task command can update BPEL payload attribute values using request parameters to the command. You can also configure this command with actions to execute after it is complete, using CMD_AUTOTASK_ON and CMD_AUTOTASK_OFF parameters.

A.3.5.1Redirect Command Parameters

This URL is returned in the response command upon executing this command. It is either:

a task flow String corresponding to a task flow ID which loads one or more pages on the task flow.

a standard URL string that redirects to the specified URL.

EXTERNAL

If this has a value of TRUE, then the redirect page does not have a CID and PID appended to it. The re-direct URL is an external Web site and all request parameters are appended in the URL.

A.3.5.2Example Implementation

Fields not shown: SOLUTION_NAMESPACE=InvoiceProcessing

Table A-42 Example Redirect Command in AXF_SOLUTION_PARAMETERS Table

COMMAND_NAMESPACE

CONFIGURATION_NAMESPACE

PARAMETER_KEY

PARAMETER_VALUE

StartInvoiceProcessing

oracle.imaging.axf.commands.system.RedirectCommand

EXTERNAL

FALSE

StartInvoiceProcessing

oracle.imaging.axf.commands.system.RedirectCommand

REDIRECT_URL

taskflow://WEB-INF/taskflows/axf-tasklist-tfd.xml#axf-tasklist-tfd

A.3.6Update Task Command

The Update Task command can update one of the following: the list of attributes in the BPEL task, values in the XML payload using XPATH, or system attributes. (For an XPATH example, see Section A.3.6.3.)

You can create your own parameter keys for the Update Task command and use either a system attribute or an XPATH for the parameter value. AXF searches the request parameters and finds all the values that match the parameter keys (besides outcome), and pulls parameter keys for the list of attributes to use in that task payload.

To update a non-payload attribute in the BPEL task, use a system attribute from those listed in Section A.3.6.2. For example, the UpdateTask command can take the value of outcome (defined as PARAMETER_KEY) from the request parameter and update the OUTCOME (defined as PARAMETER_VALUE) attribute value in the task.

A.3.6.1 Update Task Command Parameters

Table A-43 Parameters for UpdateTaskCommand

Parameter Key

Description

OUTCOME

Specify the outcome defined for the human work flow system. APPROVE and REJECT are available by default in any BPEL process; the process designer can create others.

A.3.6.2System Attributes

System Attributes

ACQUIREDBY

APPROVERS

ASSIGNEDDATE

ASSIGNEDGROUP //Cannot be updated

ASSIGNEDUSER //Cannot be updated

CREATEDATE

CREATOR

DATEATTRIBUTE1-DATEATTRIBUTE5

EXPIREDDATE

ENDDATE

FORMATTRIBUTE1-FORMATTRIBUTE5

FROMUSER

NUMBERATTRIBUTE1-NUMBERATTRIBUTE5

OUTCOME

OWNERGROUP

OWNERUSER

PRIORITY

STATE

TASKID

TASKNUMBER //Cannot be updated

TITLE

TASKDEFINITIONNAME

TEXTATTRIBUTE1-TEXTATTRIBUTE10

UPDATEDBY

URLATTRIBUTE1 - URLATTRIBUTE5

A.3.6.3Example Implementation

This example shows two attributes updated by the same comand_namespace, UpdateHelloBPEL. For more information about HelloBPEL, see "Verifying the AXF Installation with HelloBpel" in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.

A.3.9.1Validate Task Command Parameters

Table A-47 ValidateTaskCommand Parameters

Parameter Key

Description

ATTRIBUTE_TO_VALIDATE

Specifies the attribute in the BPEL task to validate. This can be either a system attribute or a payload attribute. If specifying a payload attribute, use a prefix value of XPATH: and reference a value from the AXF_XPATH_ATTRIBUTES Table.

REGULAR_EXPRESSION

Defines a standard Regular Expression for validating the specified attribute.

CMD_ON_PASS

Specifies the command to execute after this command, if the validation is successful.

CMD_ON_FAIL

Specifies the command to execute after this command if the validation fails.

FAIL_MESSAGE

Specifies the message to display if the validation fails.

A.3.9.2Example Implementation

The following configuration validates that the invoice has been saved (Invoice Transaction ID is not 0). If it is 0, the command reports the error message specified in the FAIL_MESSAGE parameter. For steps to add a validation, see Section 5.4.4.

The following diagram shows how the tables used by the Oracle E-Business Suite system in AXF solutions are related.

A.4.2AXF_CONFIGS Table (Oracle E-Business Suite)

Use the AXF_CONFIGS table to enable the AXF solution on various Oracle E-Business Suite Forms. This table provides a fine level of granularity when selecting which Forms to AXF-enable, up to the Data Block level.

Form events are automatically invoked when an action is performed on an Oracle E-Business Suite Form. The AXF_CUSTOM.pll makes all events available, such as POST-INSERT, for customization. You can decide which events to use, and how and when to use them.

When an action occurs, the customized code launches the specified solution and command configured for the event. In the case where the same form is being reused, such as Invoice Entry and Invoice Query, FORMFUNCTION and DATABLOCKNAME uniquely identify each Form.

Note:

You can enable all datablocks on a form rather than a specific datablock, by specifying AXF_DEFAULT for the DATABLOCKNAME parameter. This allows AXF to be notified whenever a POST-INSERT event occurs for the form, regardless of its datablock. Note, however, that setting the DATABLOCKNAME parameter to AXF_DEFAULT enables specified ZOOM or SPECIAL commands on all screens related to the form. (Set ZOOM and SPECIAL commands in the AXF_COMMANDS Table.)

A.4.2.1Column Description

Table A-49 Column Description for AXF_CONFIGS Table

Column Name

Description

FORMID

Specifies the primary key of the table.

FORMFUNCTION

Distinguishes each Oracle E-Business Suite Form based on the form's functionality.

Specify the menu type to display to users in Oracle E-Business Suite. You can choose:

ZOOM: Displays a Zoom menu in the toolbar.

ZOOMANDSPECIAL: Displays both a Zoom menu and a Special menu. (Enter a special key in the SPECIAL column.)

SPECIAL: Displays a Special menu on the toolbar. (Enter a special key in the Special column.)

SPECIAL

Create new menu entries by entering a unique number for the Special type menu, where:

SPECIAL1-15 creates entries in the Tools menu.

SPECIAL16-30 creates entries in the Reports menu.

SPECIAL31-45 creates entries in the Actions menu.

(Consult the Oracle E-Business Suite Documentation for further information.)

RESPONSIBILITY

Reserved for future use.

A.4.3.2Example Implementation

This example shows two commands invoked from the Zoom menu (Attach Supplemental and Process Invoices). Each command is listed twice because the commands enable the same functionality, but on two different screens.

In addition, the solution has been configured to invoke the SaveInvoice command during the POST-INSERT event, which specifies that whenever an action inserts a new Oracle E-Business Suite transaction record, the integration automatically invokes the SaveInvoice command on the back-end, performing the actions associated with the command. Note that POST-INSERT is not called by a subsequent save of the same transaction record in Oracle E-Business Suite.

Data Source for the parameter value. You can specify Data or Constant.

DATABLOCKNAME

Data Block of the Form from which the value is fetched.

FIELDNAME

Field Name in the form from which the value is fetched.

CONSTANTVALUE

A constant value for the parameter.

A.4.4.2Example Implementation

The example that follows contains two parameters sent for EventID 2: a constant value (InvoicesByVendor) and a data value (VENDOR_NAME) in the INVOICES_QF Data Block.

The COMPLETE command requires that a conversation be established between Oracle E-Business Suite and AXF. A Conversation is a session unique ID that allows communication between Oracle E-Business Suite and AXF Framework.

If a command requires a separate window to open, then Oracle E-Business Suite opens another instance of the browser. Users may then take additional steps in the newly created window.

Table A-54 Example AXF_COMMAND_PARAMETERS Table

PARAMETERID

EVENTID

PARAMETERNAME

DATASOURCENAME

DATABLOCKNAME

FIELDNAME

CONSTANTVALUE

1

2

SearchName

CONSTANT

(null)

(null)

InvoicesByVendor

2

2

VendorName

DATA

INVOICES_QF

VENDOR_NAME

(null)

18

11

InvoiceTransactionID

DATA

INV_SUM_FOLDER

INVOICE_ID

(null)

21

14

InvoiceTransactionID

DATA

INV_SUM_FOLDER

INVOICE_ID

(null)

20

15

InvoiceTransactionID

DATA

INV_SUM_FOLDER

INVOICE_ID

(null)

22

16

InvoiceTransactionID

DATA

INV_SUM_FOLDER

INVOICE_ID

(null)

A.4.5AXF_PROPERTIES Table (Oracle E-Business Suite)

Use the AXF_PROPERTIES table to define properties for AXF integration with Oracle E-Business Suite.

A.4.5.1Column Description

Table A-55 Column Description for AXF_PROPERTIES Table

Column

Description

PROPNAME

Specifies properties to use. Properties include:

SecureMode: To enable SSL, set this property to ON, and set values for AXFWalletPath and AXFWalletKey properties.

AXFWalletPath: Certificate location (path).

AXFWalletKey: Specify the key for the AXF wallet password, to be retrieved from the Oracle E-Business Suite vault.

AXF_VERSION: Specify 1 for AXF 10g, or 2 for AXF 11g.

AXF_SOAP_POLICY: Specify the name of the SOAP policy to use. The currently supported policy is USER_NAME_TOKEN.

AXF_SOAP_SECURITY: Specify TRUE to enable SOAP security, as described in Section 2.2.1.

AXF_SOAP_USER: Specify the SOAP userid used in the SOAP header for authentication, as described in Section 2.2.1.

AXF_PAPERCLIP: Set to TRUE to enable the paperclip option, or FALSE (default) to disable it. Also see Section 5.4.8.

PROPVALUE

Specifies the property's value.

A.4.5.2Example Implementation

This example table shows the default properties values.

Table A-56 Example AXF_PROPERTIES Table

PROPNAME

PROPVALUE

SecureMode

OFF

AXFWalletPath

file:walletpath

AXFWalletKey

AXFWalletKey

AXF_VERSION

2

AXF_SOAP_POLICY

USER_NAME_TOKEN

AXF_SOAP_SECURITY

TRUE

AXF_SOAP_USER

weblogic

AXF_PAPERCLIP

TRUE

A.5 Oracle PeopleSoft Tables For the Imaging Solution

Configuring the adapter for Oracle PeopleSoft requires configuring AXF-related tables in Oracle PeopleSoft. For more information, see Section 3.4.

A.5.1About the Oracle PeopleSoft AXF Tables For the Imaging Solution

The following diagram shows how the tables used by the Oracle PeopleSoft system in AXF solutions are related.

Note:

All AXF table fields require non-null values. You can include a space for fields that do not apply.

A.5.2PS_AXF_CONFIG Table

Use the PS_AXF_CONFIG table to enable the AXF solution on various Oracle PeopleSoft components. This table provides a fine level of granularity when selecting which pages and components to AXF-enable.

Events are automatically invoked when an action is performed on an Oracle PeopleSoft page. The AXF_PS_Integration project component catches PRE- and POST- save events and makes them available for customization. You can decide which events to use and how and when to use them.

The default service operation is AXF_EXECUTE. You can set up and use other connections.

AXF_VERSION

Specifies the AXF version of the connection. Available values include:

10g

11g

A.5.2.2Example Implementation

This example defines that the VCHR_QUICK_PNL component is AXF-enabled.

Table A-58 Example PS_AXF_CONFIG Table

AXF_CONFIG_ID

AXF_COMPONENT_NAME

AXF_CONNECT_NAME

AXF_VERSION

1

VCHR_QUICK_PNL

AXF_EXECUTE

11g

A.5.3PS_AXF_COMMANDS Table

Use the PS_AXF_COMMANDS table to describe the actions to take based on user activity. This table works with the PS_AXF_CONFIG Table.

A.5.3.1Column Description

Table A-59 Column Description for PS_AXF_COMMANDS Table

Column Name

Description

AXF_CMDS_ID

Specifies the primary key of the table, used to identify the unique command.

AXF_CONFIG_ID

Specifies the foreign key to the PS_AXF_CONFIG Table, which associates this unique command with a particular page and component.

AXF_EVENT_NAME

Specifies the event being executed. The AXF_EVENT_NAME corresponds to the subpage that is incorporated into an existing Oracle PeopleSoft page, such as the button, link, or menu that is added to an Oracle PeopleSoft page to invoke AXF functionality such as the Image Viewer or Task List. Available options include:

AXF_BUTTON_1, …, AXF_BUTTON_5

AXF_LINK_1, ..., AXF_LINK5

AXF_COMBO_1, ..., AXF_COMBO_5

AXF_PRE_SAVE_SBP

AXF_POST_SAVE_SBP

AXF_SELECT_LABEL

Defines the name displayed on the page for the selection field. This is used only with the COMBO event.

AXF_DISPLAY_NAME

Defines the name of the button or link to display on the Oracle PeopleSoft screen.

AXF_SOL_NAMESPC

Identifies the solution namespace for the command to execute.

AXF_CMD_NAMESPC

Identifies the command namespace for the command to execute.

AXF_PSFT_ROLE

Identifies the Oracle PeopleSoft roles with access to the command. It is a comma-delimited list with each role enclosed in single quotes (for example, 'Role1','Role2','Role3').

AXF_SORT_ORDER

Specifies the order of items displayed in a selection field. Sort order applies to selection fields only.

AXF_REQ_CONV

Specifies if a conversation is required to this command before execution. For example, execution of the UpdateTask command requires a conversation be running in order for the user to select a current task.

A.5.3.2Example Implementation

This example shows two commands added to an invoice processing page. One inserts a button that when clicked initiates invoice processing. The other inserts a link that when clicked initiates a search of Oracle I/PM for duplicate invoices.

In addition, the solution has been configured to invoke the SaveInvoice command during the SAVE_POST_CHANGE event, which specifies that whenever an action inserts a new Oracle PeopleSoft transaction record, the integration automatically invokes the SaveInvoice command on the back-end, performing the actions associated with the command. Note that SAVE_POST_CHANGE is not called by a subsequent save of the same transaction record in Oracle PeopleSoft.

You must specify an Oracle PeopleSoft Role in the AXF_PSFT_ROLE field to give permissions to use the commands. If a person does not have proper permissions to use the commands, the commands do not display. If the commands display but do not function, this indicates that the commands are not properly configured.