Copyright © TIBCO Software Inc. All rights reserved.
Copyright © TIBCO Software Inc. All rights reserved.


Appendix D Understanding Audit Trails

Appendix D
An audit trail is a predefined iProcess report that provides a detailed log of all transactions for an individual case of a procedure.
There are two types of audit trail message:
User-defined. See SWDIR\etc\language.lng\auditusr.mes for more information about using this file to define user-defined audit trail messages.
Audit trail messages can be used in two ways:
The following table describes the system-defined messages that can be displayed in your audit trails and what they mean.
The case of a procedure has been started where UserName is the name of the iProcess user who has started the case. See "Starting Cases" in TIBCO iProcess Workspace (Windows) User’s Guide for more information.
StepDescription processed to UserName
The StepDescription work item has been processed to the UserName user. See "Opening and Processing a Work Item" in TIBCO iProcess Workspace (Windows) User’s Guide for more information.
StepDescription released by UserName
The StepDescription work item has been released by the UserName user. See "Opening and Processing a Work Item" in TIBCO iProcess Workspace (Windows) User’s Guide for more information.
Deadline for StepDescription expired for UserName
The deadline set for the StepDescription work item has expired for the UserName user. If the deadline has expired, then the deadline actions will be processed. See "Using Deadlines in Procedures" in TIBCO iProcess Modeler Basic Design for more information.
StepDescription forwarded to UserName
An iProcess user has forwarded the StepDescription work item from their work queue to another iProcess user’s work queue. The UserName is the name of the iProcess user who has received the work item in their work queue.
See "Enabling Steps to be Forwarded" in TIBCO iProcess Modeler Basic Design for more information.
Error - StepDescription not found
The StepDescription work item cannot be found. You may see this message if, for example, the case has been purged and so the work item no longer exists.
Check the sw_warn or sw_error log files to see if any error messages were logged. See TIBCO iProcess Engine System Messages Guide for more information.
Check the sw_warn or sw_error log files to see if any error messages were logged. See TIBCO iProcess Engine System Messages Guide for more information.
The case of a procedure has been terminated prematurely by the UserName user. This means that not all the steps in the case have been completed because the case was terminated prematurely.
See "Closing Cases" in TIBCO iProcess Workspace (Windows) Manager's Guide for more information.
StepDescription released from queue by UserName
StepDescription withdrawn from UserName
The StepDescription work item has been withdrawn from the UserName queue because the deadline expired or as the result of a withdraw action. If the step has been withdrawn because a deadline has expired, the deadline actions will be processed. See "Withdrawing Steps from the Procedure" in TIBCO iProcess Modeler Basic Design for more information.
StepDescription resent to UserName
The StepDescription work item has been resent to the UserName user. See "Resending work items" in TIBCO iProcess swutil and swbatch Reference Guide for more information.
StepDescription event issued by UserName
The StepDescription event step has been issued by the UserName user. See "Using Events" in TIBCO iProcess Modeler Integrating Techniques for more information.
Sub-Case started from StepDescription
A case of a sub-procedure has been started from the StepDescription step. See "Defining and Using Sub-procedures" in TIBCO iProcess Modeler Advanced Design for more information.
Sub-case started from StepDescription completed
A case of a sub-procedure that was started from the StepDescription step has terminated normally. See "Defining and Using Sub-procedures" in TIBCO iProcess Modeler Advanced Design for more information.
Sub-case started from StepDescription terminated abnormally
A case of a sub-procedure has terminated abnormally where StepDescription is the description of the step. You may see this message if a system error has caused the sub-case to terminate abnormally.
Check the sw_warn or sw_error log files to see if any error messages were logged. See TIBCO iProcess Engine System Messages Guide for information.
See "Defining and Using Sub-procedures" in TIBCO iProcess Modeler Advanced Design for more information.
The deadline set for the StepDescription step that is calling the sub-case has expired. This causes the sub-case started from this step to be closed. This means that the deadline actions will be processed. See "Using Deadlines in Procedures" in TIBCO iProcess Modeler Basic Design for more information.
Sub-case started from StepDescription closed
The StepDescription step that called the sub-case has been withdrawn because the deadline has expired. This causes the sub-case started from this step to be closed. This means that the deadline actions will be processed. See "Using Deadlines in Procedures" in TIBCO iProcess Modeler Basic Design for more information.
StepDescription redirected to UserName
The StepDescription work item has been redirected to another user’s work queue. UserName is the name of the iProcess user who has received the work item in their work queue. See "Redirecting Work Items" in TIBCO iProcess Workspace (Windows) User’s Guide for more information.
The case has been suspended by the UserName user. See "Suspending the Flow of a Case" in TIBCO iProcess Modeler Integration Techniques for more information.
The case has been resumed by the UserName user. See "Suspending the Flow of a Case" in TIBCO iProcess Modeler Integration Techniques for more information.
StepDescription Case Jump by UserName
The UserName user has caused the case to jump to this StepDescription step. See "Using GOTOSTEP to Simplify Procedure Routing" in TIBCO iProcess Modeler Basic Design for more information.
SubProcedureDescription Sub-Case started (using array element StepName)
A case of a SubProcedureDescription sub-procedure has been started by a StepName array element step. See "Using Array Fields" in TIBCO iProcess Modeler Advanced Design for more information.
Task count StepName received for Status:StepName
StepName is the name of the graft step
Status:StepName is the current status of the graft step and the graft step name.
See "Graft Step Task Count" in TIBCO iProcess Modeler Integration Techniques for more information.
One of the processes grafted to this StepName step has completed. Status is the current status of the graft step.
See "Graft Step Task Count" in TIBCO iProcess Modeler Integration Techniques for more information.
Sub-Case grafted to StepDescription
The sub-case has been grafted to the StepDescription graft step. See "Using Graft Steps" in TIBCO iProcess Modeler Integration Techniques for more information.
External process ExternalProcessName grafted to StepDescription.
The external process has been grafted to the StepDescription graft step. ExternalProcessName is the name of the external process. See "Using Graft Steps" in TIBCO iProcess Modeler Integration Techniques for more information.
StepDescription initiated
The StepDescription graft step has been initiated by the external system. See "Using Graft Steps" in TIBCO iProcess Modeler Integration Techniques for more information.
External process ExternalProcessName released
The external process has completed. ExternalProcessName is the name of the external process. See "Using Graft Steps" in TIBCO iProcess Modeler Integration Techniques for more information.
StepDescription released, all tasks complete
The StepDescription graft step has been released because all the tasks grafted to the graft step are complete. See "Using Graft Steps" in TIBCO iProcess Modeler Integration Techniques for more information.
StepDescription released, all sub-cases complete
The StepDescription dynamic sub-procedure step has been released. This is because all the sub-cases started from the step are complete.
See “Defining a Dynamic Call to Multiple Sub-Procedures” in TIBCO iProcess Modeler Advanced Design for more information.
Case migrated from Procedure StepName to StepDescription by UserName
StepName is the name of the step.
StepDescription is the name of the form which is displayed when you open this work item.
UserName is the name of the iProcess user who has received the work item in their work queue.
See "Using Version Control" in TIBCO iProcess Modeler Procedure Management for more information.
See "Release a Procedure Version" in TIBCO iProcess swutil and swbatch Reference Guide for more information about migrating cases to new procedure versions.
Sub-cases, grafted to StepDescription, closed
The sub-cases grafted to the StepDescription graft step have been closed. This is because the graft step has been withdrawn because a deadline expired. This means that the deadline actions will be processed. See "Using Deadlines in Procedures" in TIBCO iProcess Modeler Basic Design for more information.
Deadline for StepDescription expired
The deadline set for the StepDescription graft step has expired. If the deadline has expired, then the deadline actions will be processed. See "Using Deadlines in Procedures" in TIBCO iProcess Modeler Basic Design for more information.
Sub-cases, started from StepDescription, closed
The deadline set on the StepDescription dynamic sub-procedure step has expired so the dynamic sub-procedure step has been withdrawn. This has caused the sub-cases started from the dynamic sub-procedure step to close. This means that the deadline actions will be processed. See "Using Deadlines in Procedures" in TIBCO iProcess Modeler Basic Design for more information.
StepDescription withdrawn, outstanding items not deleted
The StepDescription step has been withdrawn because a deadline has expired. However, the outstanding items have not been deleted. If the deadline has expired, then the deadline actions will be processed. See "Using Deadlines in Procedures" in TIBCO iProcess Modeler Basic Design for more information.
No addressees defined for step StepDescription - automatically released
The StepDescription step has no addressees defined for it so it has been automatically released. See "Defining a Step" in TIBCO iProcess Modeler Getting Started for more information.
No sub-procedures defined for step StepDescription - automatically released
The StepDescription step has no sub-procedures defined for it so it has been automatically released. See "Defining and Using Sub-procedures" in TIBCO iProcess Modeler Advanced Design for more information.
StepDescription forwarded by UserName
A StepDescription work item is forwarded by an iProcess user. The UserName is the name of the iProcess user who forwards the work item.
StepDescription EAI call-out initiated (UserName)
The StepDescription step has initiated an EAI call-out to an external system on behalf of a UserName user. The iProcess Suite cannot continue processing the case until the EAI call-out has completed. See "Using EAI steps" in TIBCO iProcess Modeler Integration Techniques for more information.
StepDescription EAI call-out completed (UserName)
The EAI call-out initiated by the StepDescription step has completed. UserName is the name of the iProcess user on whose behalf the call-out was made. See "Using EAI steps" in TIBCO iProcess Modeler Integration Techniques for more information.
Deadline for EAI Step StepDescription expired
The deadline for the StepDescription EAI step has expired. The deadline actions will be processed. See "Using Deadlines in Procedures" in TIBCO iProcess Modeler Basic Design for more information.
EAI Step StepDescription withdrawn
The StepDescription EAI step has been withdrawn because the deadline has expired. The deadline actions will be processed. See "Using Deadlines in Procedures" in TIBCO iProcess Modeler Basic Design for more information.
Commit Point StepDescription reached
The procedure has reached a StepDescription transaction control step. This step is configured to commit the current data at the current point in the business process. See "Using Transaction Control steps" in TIBCO iProcess Modeler Integration Techniques for more information.
The procedure has started a new transaction from the StepDescription transaction control step. See "Using Transaction Control steps" in TIBCO iProcess Modeler Integration Techniques for more information.
The StepDescription step has retried the new transaction. See "Using Transaction Control steps" in TIBCO iProcess Modeler Integration Techniques for more information.
Reason Case data modified by UserName
Case data has been modified by user UserName. Reason gives a description of the reason for the change, as specified in the SW_MODIFY_CASEDATA statement. See TIBCO iProcess Engine Database Administrator’s Guide for your database for details.
stepdescription opened by username
The StepDescription work item has been opened by the user UserName. See AUDIT_OPENKEEP on page 211 for more information.
stepdescription kept by username
The StepDescription work item has been kept by the user UserName. See AUDIT_OPENKEEP on page 211 for more information.
StepDescription EAI call-out failed (UserName)
The EAI call-out initiated from the StepDescription EAI step on behalf of the UserName.
Check the sw_warn or sw_error log files, which is located in the SWDIR\logs directory, to see if any error messages were logged. See TIBCO iProcess Engine System Messages Guide for more information.
See "Using EAI steps" in TIBCO iProcess Modeler Integration Techniques for more information.
Workflow may have an infinite loop (at StepDescription) - reached max actions per transaction (UserName)
See TIBCO iProcess Engine System Messages Guide for more information.
See TIBCO iProcess Engine System Messages Guide for more information.
The run-time plug-in for EAI Type UserName (used by step StepDescription is not registered on all servers or failed to load/initialize correctly.
UserName is the name of the iProcess user on whose behalf the EAI step is running.
StepDescription is the description of the EAI step.
See "Using EAI steps" in TIBCO iProcess Modeler Integration Techniques for more information.
Invalid sub-procedure UserName specified for StepDescription - check sw_warn/sw_error logs
The UserName specified for the StepDescription sub-procedure step (on whose behalf the sub-procedure is being called) is invalid. You need to fix the step so that it uses the correct name.
Check the sw_warn or sw_error log files to see if any error messages were logged. See TIBCO iProcess Engine System Messages Guide for more information.
See "Defining and Using Sub-procedures" in TIBCO iProcess Modeler Advanced Design for more information.
StepDescription and sub-procedure UserName are not based on the same parameter template - check sw_warn/sw_error logs
The StepDescription step is trying to call a sub-procedure whose parameter template is not the same as the main procedure. UserName is the name of the iProcess user on whose behalf the sub-procedure is being called.
Check the sw_warn or sw_error log files to see if any error messages were logged. See TIBCO iProcess Engine System Messages Guide for more information.
See "Defining and Using Sub-procedures" in TIBCO iProcess Modeler Advanced Design for more information.
StepDescription and sub-procedure UserName are not based on the same version of parameter template - check sw_warn/sw_errlogs
The StepDescription step is trying to call a sub-procedure whose parameter template is not the same version as the main procedure. UserName is the name of the iProcess user on whose behalf the sub-procedure is being called.
Check the sw_warn or sw_error log files, which is located in the SWDIR\logs directory, to see if any error messages were logged. See TIBCO iProcess Engine System Error Messages Guide for more information.
See "Defining and Using Sub-procedures" in TIBCO iProcess Modeler Advanced Design for more information.
The procedure has found an error and has reached a StepDescription transaction control step that has caused the transaction to abort.
Check the sw_warn or sw_error log files to see if any error messages were logged. See TIBCO iProcess Engine System Messages Guide for more information.
See "Using Transaction Control Steps" in TIBCO iProcess Modeler Integration Techniques for more information.
StepDescription EAI delayed-release failed (error code (failure_count, BG_action) : error message)
The transaction of delayed release StepDescription EAI step failed.
The error code and error message variables specify the error. The failure_count variable specifies the number of times the delayed release EAI step has failed. The BG_action variable specifies what the BG process does when an error occurred.
stepdescription delivered to Exchange recipient username
stepdescription release received from Exchange recipient username
stepdescription withdrawn from Exchange recipient username
BusinessWorks Activity Audit description processed by username
The action description has been carried out by the user UserName within BusinessWorks. This message is generated by, and the description text is provided by, the BusinessWorks iProcess Audit activity. It is used to audit BusinessWorks activities in iProcess Engine.
See the TIBCO iProcess Connector for ActiveMatrix BusinessWorks User’s Guide for more information about the iProcess Audit activity.
The changes UserName makes to the case data by using iProcess Insight, iProcess Workspace (Browser), or the setCaseData TIBCO iProcess Server Objects interface, rather than by normal step processing.
For more information about changing case data in iProcess Insight, see TIBCO iProcess Insight User’s Guide. For more information about changing case data in iProcess Workspace (Browser), see TIBCO iProcess Workspace (Browser) User’s Guide.

Copyright © TIBCO Software Inc. All rights reserved.
Copyright © TIBCO Software Inc. All rights reserved.