6Troubleshooting
Troubleshooting
This chapter describes troubleshooting for the following types of problems:
Runtime event setting
Integration object setup
Runtime Event Setting Issues
You might encounter problems due to incorrect setting of your Runtime Event.
Double Triggering the Same Workflow
The following sections describe problems and solutions.
Problem
After configuring the runtime event to trigger a workflow process, the system did not return or returned with the error message, “Try to read or write to the invalid memory address" at runtime.
Reason
Inside the workflow process, it may trigger the same runtime event, which is the caller of the current workflow. Therefore, the same workflow that was triggered is triggered again for the second time, and results in an infinite loop.
Solution
Use applet as event object type instead of using business component. This will restrict the event to focus on only one view instead of multiple views as business components are reused in many different ways. Users may not encounter the problem mentioned when configuring event using the business component object type only if it is certain that the selected business component will not be changed during the processing of that particular workflow.
Runtime Event Setup
The following sections describe problems and solutions.
Problem
Workflow is not triggered although event has been configured.
Solution
Verify the setting for the process name in Runtime Event Administration view is correct. For example, workflow process name is “IAA outbound workflow".
Field Name Field Value
Business Service Name Workflow Process Manager
Business Service Method RunProcess
Business Service Context “ProcessName", “IAA outbound workflow"
Workflow Process Setup for Runtime Event Support
The following sections describe problems and solutions.
Problem
Workflow is not executed although event has been configured.
Solution
Verify the setting for the branch type within the workflow start step. This should be “Default" unless you have defined workflow runtime event from Workflow Designer, which in this case will be “Condition".
Problem
ObjectId is not passed to the workflow when using Runtime Event Management to trigger the workflow.
Solution
The business object name of the workflow is not setup correctly. Please select the one desired.
Integration Object Setup Issues
Another setting that could cause error in your integration process is your integration object settings.
Inactive All Unused Integration Component Fields
The following sections describe problems and solutions.
Problem
FINS IAA-XML Transaction Manager returns error message indicating error occurs in some component fields.
Solution
Inactive all unused integration component fields for internal integration objects created by the FINS IAA Wizard to solve the problem. In some cases, two or more integration component fields are based on the same table column, and causes SQL error in object manager.
Verify User Keys of Integration Components
The following sections describe problems and solutions.
Problem
FINS IAA-XML Transaction Manager cannot create or update a record.
Solution
Make sure the current user keys of the integration components are properly configured. User Keys created by FINS IAA Wizard may not fully meet customized situation. Hence, please customize the user key combination to allow the transaction manager be able to uniquely identify a business component record.
All required fields, not including system fields, need to have initial value when business component creating a new record. Please make sure those fields are properly initialized.
Setup the Integration Object User Property and Literal Values
The following sections describe problems and solutions.
Problem
FINS IAA-XML Converter generates XML string without some required fields.
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 need.