Can we use the Audit log search feature to lookup non pre-populated fields against BC-EDI transactions, like the EDI "Document Reference Number" element?
Article ID: KB0090885
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Resolution:
BC Audit log allows to fetch transactions based on certain predefined fields like Operation ID, Trading Partner, Interchange ID , etc.
However, if you need to query transactions based on the "Document Reference Number", you can leverage the XEngine Commit feature. This will instruct the XEngine to populate this additional field for audit purposes.
To add the XEngine commit rule to an element.
1) Open the relevant EDI guideline in SpecBuilder.
2) Select the element you would like to be present in the audit logs.
3) Select the Rules tab from SpecBuilder and click the "New Rule" icon located on top.
4) Select XEngine Commit from the populated set of rules.
5) Specify the value name for the rule created.
6) Save the guideline and upload it into the associated EDI operation definition.
7) When possible, restart your BC engine for the new change to take effect.
** Notes **
a) A Specbuilder screen shot is attached to this article.
b) Using "File reference" will not work. Any changes made to the XEngine Commit Rule will require restart of the BC Engine for the changes to take effect.
BC Audit log allows to fetch transactions based on certain predefined fields like Operation ID, Trading Partner, Interchange ID , etc.
However, if you need to query transactions based on the "Document Reference Number", you can leverage the XEngine Commit feature. This will instruct the XEngine to populate this additional field for audit purposes.
To add the XEngine commit rule to an element.
1) Open the relevant EDI guideline in SpecBuilder.
2) Select the element you would like to be present in the audit logs.
3) Select the Rules tab from SpecBuilder and click the "New Rule" icon located on top.
4) Select XEngine Commit from the populated set of rules.
5) Specify the value name for the rule created.
6) Save the guideline and upload it into the associated EDI operation definition.
7) When possible, restart your BC engine for the new change to take effect.
** Notes **
a) A Specbuilder screen shot is attached to this article.
b) Using "File reference" will not work. Any changes made to the XEngine Commit Rule will require restart of the BC Engine for the changes to take effect.
Issue/Introduction
Can we use the Audit log search feature to lookup non pre-populated fields against BC-EDI transactions, like the EDI "Document Reference Number" element?
Attachments
Feedback
Yes
No
Powered by
