Large numbers of procedure step objects can result in procedure corruption prior to version 11.6.1
Article ID: KB0078954
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Workspace (Windows) | Prior to 11.6.1 |
Description
When importing procedures using the iProcess Workspace (Windows) or editing using iProcess Modeler some temporary files are used to save form contents.
The temporary file name is generated using a calculation that uses a combination of the procedure ID and step ID. If there is a large number of steps in a procedure it is possible that the temporary file names may be duplicated.
The temporary file name is generated using a calculation that uses a combination of the procedure ID and step ID. If there is a large number of steps in a procedure it is possible that the temporary file names may be duplicated.
Issue/Introduction
When importing procedures using the iProcess Workspace (Windows) or editing using iProcess Modeler, procedure corruption can occur if the Step ID reaches a value greater than 2500.
Environment
All supported operating systems
Resolution
Use the "plist -d" command to output the step information for a procedure.
The "Place" column is equal to the step ID.
Sort the "plist -d" output and check if any steps have an ID/Place value greater than 2500.
If there are then it is possible that using the 11.6.0 Modeler could cause the problem.
The "Place" column is equal to the step ID.
Sort the "plist -d" output and check if any steps have an ID/Place value greater than 2500.
If there are then it is possible that using the 11.6.0 Modeler could cause the problem.
Feedback
Yes
No
Powered by
