Question

5
Replies
196
Views
Attila Donath (AttilaDonath)
Cognizant
Pega Lead System Architect
Cognizant
CH
AttilaDonath Member since 2016 10 posts
Cognizant
Posted: June 29, 2017
Last activity: October 16, 2018
Posted: 29 Jun 2017 4:33 EDT
Last activity: 16 Oct 2018 12:03 EDT
Closed
Solved

Wrong audit history message when using pxLinkAttachmentToCase

Hi,

I am using pxLinkAttachmentToCase Activity to link a Data-Workattach-File to a case.
I noticed that in the Audit History the messages contain a placeholder instead of the actual filename, like "A file has been attached: {1}." (instead "{1}" the file's name should be shown). See: AuditTrail.png

Digging into the code: there is a Property-Set step in pxLinkAttachmentToCase Activity which assembles the audit history message (pxLinkAttachmentToCase.png):

Param.AuditNote = @(Pega-RULES:String).equals("", Param.AuditNote)? "FileAttached" : Param.AuditNote + "\t" + LinkAttachPage.pyNote

The Param.AuditNote can either be

"FileAttached"

or

Param.AuditNote + "\t" + LinkAttachPage.pyNote

as the ternary expression does not have brackets around it.

Checking an other Activity AttachFile shows that we need the file name parameter after "FileAttached" as well (AttachFile.png), so I suggest to fix the above line in pxLinkAttachmentToCase by adding brackets:

(@(Pega-RULES:String).equals("", Param.AuditNote) ? "FileAttached" : Param.AuditNote) + "\t" + LinkAttachPage.pyNote

Pega versions I checked: 7.2, 7.2.2

If it has already been fixed, please provide the hotfix I need to apply.

Regards,
Attila

***Updated by moderator: Lochan to add BUG ID***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Data Integration Java and Activities Support Case Created
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.