6Troubleshooting

Troubleshooting

This chapter describes run-time setup problems in workflows, integration object setup problems, a rollback problem, and an envelope problem.

Run-Time Event Setup Problems in Workflows

The following sections describe run-time event setup problems in workflows.

Workflow is double-triggered

Problem

After configuring a runtime event to trigger a workflow process, the system freezes without returning an error, or it returns the error message, “Try to read or write to the invalid memory address.”

Reason

A workflow may trigger the same runtime event that initially launched the workflow. Therefore, the same workflow that is triggered is triggered again. The result is an infinite loop.

Solution

Use an applet as the event object type instead of using a business component. Doing so restricts the event to a single view instead of multiple views. Business components are reused in many different ways. If it is certain that the selected business component will not be changed during the processing of the workflow, users will not encounter this problem.

Workflow is not triggered

Problem

The workflow is not triggered although the event has been configured.

Solution

Verify that the following settings are correct:

• The branch type within the start step of the workflow is correct.

  If you have defined a runtime event outside the workflow, the branch type within the start step should be “Default.” If you have defined a runtime event inside the workflow (from Workflow Designer), the start step should be “Condition.”

• The process name in the Runtime Event Administration view is correct.

For example, a workflow process name is “ACORD Add Auto Policy Outbound workflow,” as listed in the following table.

Field Name	Field Value
Business Service Name	Workflow Process Manager
Business Service Method	RunProcess
Business Service Context	“ProcessName,”“ACORD Add Auto Policy Outbound workflow”

Note: A blank space is required between “ProcessName” and “ACORD Add Auto Policy Outbound workflow.”

Object Id is not passed to the workflow

Problem

The Object Id is not passed to a workflow correctly when using Runtime Event Management to trigger the workflow.

Solution

The business object name of the workflow is not set up correctly. Please select the business object name desired.

Integration Object Setup Problems

The following sections describe integration object setup problems.

Errors in some component fields

Problem

FINS ACORD XML Transaction Manager returns an error message indicating that an error occurs in some component fields.

Solution

Make inactive all unused integration component fields for internal integration objects created by the FINS ACORD Wizard. In some cases, two or more integration component fields are based on the same table column, which causes an SQL error in the object manager.

Transaction manager cannot create or update a record

Problem

The <MsgStatus> information in the response ACORD messages indicates that the FINS ACORD XML Transaction Manager cannot create or update a record.

Solution

Check to make sure the current User Keys of the integration components are properly configured. User Keys created by the FINS ACORD Wizard may not fully meet a customized situation. Customize the user key combination as necessary to allow the transaction manager to uniquely identify a business component record.

All required fields, not including system fields, need to have an initial value when a new record of a business component is created. Please make sure those fields are properly initialized.

Some required fields are empty in an XML string

Problem

Some required fields are empty in an XML string generated by the FINS ACORD XML Converter.

Solution

Initialize all required fields in the integration component “XML Literal Value” column. Some values are specified in the integration object/component/component field user property. Be sure to customize them to suit your integration needs.

Rollback Problem

The following section describes a rollback problem.

Rollback operation fails

Problem

A needed rollback does not happen. For example, after running an ACORD outbound workflow to add a policy record, if the returning response message contains errors indicating that the operation is unsuccessful, the workflow ACORD Add Policy Outbound Response Workflow With Rollback should delete (roll back) the original record from the database.

Solution

The probable reason is that the rollback operation is improperly defined in the FINS ACORD XML Transaction Manager. Use Oracle’s Siebel Tools to make sure that the rollback operation is defined in the business service user property of the FINS ACORD XML Transaction Manager. The operation name is “SAUpsert_ROLL_BACK”, and the value is “EAI Siebel Adapter/Delete/RollbackOnSame;”. Do not forget to deliver the changes to the integration branch.

Envelope Problem

The following section describes an envelope problem.

Message does not show user-selected information

Problem

A user chooses header elements while generating an envelope integration object, but the resulting message for initial request does not show the chosen header information.

Solution

When a user creates a user-defined envelope integration object, all the user-chosen tags are memorized in the userdefined user property of each integration component of the envelope integration object. The value of this user property of each integration component indicates the names of its child integration components.

In the workflow, find the business service corresponding to the “PropsetToXMLPropSet” method of the FINS ACORD XML Converter. Change the value of the input argument from initsignon to userdefined. Doing so causes the user property userdefined to be used to construct the initial SignonRq header instead of the default value initsignon. The SignonRq header will reflect the user-chosen elements.