SA-19511

Summary

Incorrect behavior in Audit trail because of History-Add method. Resulting behavior did not match the method description from documentation. Following records were added to Audit after the flow execution.

pxCommitDateTime pxAddedByID pyPerformer pyMemo pyTaskName
22.12.15 System name1 This is a test audit record Test Audit 2
22.12.15 name1 name2 name3 This is a test audit record Test Audit 1

From documentation:

"Parameter:
ForOperatorID

Description:
Enter an Operator ID value (literal or property reference) to be recorded in history. Typically, enter pxRequestor.pyUserIdentifier to record the current user."

According to History-Add method description, the system must get operator details from ForOperatorID parameter. Fields pxAddedByID and pyPerformer contain values from the second row. The value in pyPerformer must contain login name passed from parameter ForOperatorID. The result is incorrect.

Error Messages

Not Applicable

Steps to Reproduce

1. Create Utility-activity (TestActivity) with one step inside History-Add.
2. Pass parameters listed below:

• ForOperatorID: login of current operator
• HistoryMemo: "This is a test audit record"

3. Create flow with five shapes:

• Start
• Utility TestActivity - "Test Audit 1"
• Wait
• Utility TestActivity - "Test Audit 2"
• End

4. Specify wait interval for one minute in the Wait shape.

Root Cause

Custom change in the default behavior of History-Add method, which puts Full Name of the current operator instead of its operator ID, was required.

Resolution

Append a white space with the current operatorID (can be property reference), and pass that as parameter to the History-Add method.
This method cannot detect the current operator in this case, and does not pass the Full Name.