This page provides information on how to remove Siebel workflow objects from the analysis as it can result in the analysis getting stuck on the same UAX file for a couple of hours as the Siebel Work Flow Objects consist of several children.
Release | Yes/No |
|---|---|
| 8.3.x |  |
| 8.2.x | |
| 8.1.x | |
| 8.0.x |  |
| 7.3.x | |
| 7.2.x | |
| 7.0.x | |
In some occasion, here with Siebel 8.1.1.10, the number of Siebel Workflow extracted is OK, but some of them got insane number of children.
While Extraction and Deploy action went well, analysis can get stuck for a couple of hours or a couple of days on the same single .uax file (10 to 150 MB), defining 1 Siebel Workflow and n number of children.
The workaround is to not analyze these Siebel Workflow objects.
Good point is that they are easy to locate :
- Each .uax contains 1 Siebel Workflow, along with their children.
- Only the .uaxdirectory file matters, no file deletion is required.
To remove these objects manually,
- Backup and then Open Project's DatabaseExtraction.uaxdirectory file, at the root of the Project deploy folder:
- Open Search dialog
- Go to Mark tab
- Check Bookmark line checkbox
- Type SIEBEL_WORKFLOW
6. Press Mark All
7. Scroll at the bottom of the file (where the Siebel Workflow .uax resides usually)
8. Close Search dialog
9. Select menu Search, item Bookmark / sub-item Remove Bookmark lines
10. The bookmarked line are removed:
11. Save .uaxdirectory file
12. Run Project analysis (Take a snapshot, as usual).
13. It will skip 100 000s of object instances, thus a large gain in runtime, and won't affect the quality model, as there are no Quality Rules on Siebel Workflows.
The issue is permanently fixed in 5.2.2 funcrel version of the Siebel Extension.
Ticket # 23356
