Question
Pegasystems Inc.
JP
Last activity: 20 Dec 2016 6:14 EST
pyCaseAttachmentsWrapper does not show attachment link, case id, attachment category if "Work-.pyIncludeSubCases" set to "true"
I am using PRPC v7.2.1.
As attached image shows, pyCaseAttachmentsWrapper does not show attachment link, case id, attachment category if "Work-.pyIncludeSubCases" set to "true". Is this a known issue ? if so is there any work around or hotfix provided?
Below is the expected display of Attachments section
Steps to reporduce the issue.
1. Override pyDefault data transform of a case type then set ".pyIncludeSubCases" to "true".
2. Create a new case and then attache a File to it.
Accepted Solution
Pegasystems Inc.
JP
The issue is solved by customizing the control rule "pyAttachmentFeedDescription" as below.
<%
String createOpName = tools.getPrimaryPage().getString("pxCreateOpName");
createOpName = tools.getLocalizedTextForString("pxRequestor.pyUserName", createOpName);
String workID = tools.getPrimaryPage().getParentPage().getString("pyID");
if(workID != null && workID.length()>0){
//We are NOT looping over AllAttachments page which include attachments of covered cases.
tools.getPrimaryPage().putString("pyID",workID);
}
String clsName = tools.getPrimaryPage().getString("pyClassName");
String note = tools.getPrimaryPage().getString("pyNote");
if(clsName.equalsIgnoreCase("Data-WorkAttach-Note")){
note=tools.getPrimaryPage().getString("pyLabel");
tools.getPrimaryPage().putString("pyNote",note);
}
if(note==null || note.length()==0){
note = tools.getPrimaryPage().getString("pyMemo");
tools.getPrimaryPage().putString("pyNote",note);
}
The issue is solved by customizing the control rule "pyAttachmentFeedDescription" as below.
<%
String createOpName = tools.getPrimaryPage().getString("pxCreateOpName");
createOpName = tools.getLocalizedTextForString("pxRequestor.pyUserName", createOpName);
String workID = tools.getPrimaryPage().getParentPage().getString("pyID");
if(workID != null && workID.length()>0){
//We are NOT looping over AllAttachments page which include attachments of covered cases.
tools.getPrimaryPage().putString("pyID",workID);
}
String clsName = tools.getPrimaryPage().getString("pyClassName");
String note = tools.getPrimaryPage().getString("pyNote");
if(clsName.equalsIgnoreCase("Data-WorkAttach-Note")){
note=tools.getPrimaryPage().getString("pyLabel");
tools.getPrimaryPage().putString("pyNote",note);
}
if(note==null || note.length()==0){
note = tools.getPrimaryPage().getString("pyMemo");
tools.getPrimaryPage().putString("pyNote",note);
}
%>
<a class="Case_tools" title='<p:r n=".pyNote" m="normal"/>' href="#" onclick="pega.ui.HarnessActions.doAttachmentSingleClick('<p:r n=".pxListSubscript" />', '<p:r n=".pxObjClass" />',
'<p:r n=".pxInsName" />', '<p:r n=".pzInsKey" />', null, null, '<p:r n=".pxLinkedRefTo" />')">
<pega:reference name=".pyNote" mode="display" format="pzCMEllipsis">
<pega:param name="CharLength" value="25"/>
</pega:reference>
</a>
<div class="subsidiary">
<p:r n='.pyID' m='normal'/>
<%=StringUtils.crossScriptingFilter(" | "+tools.getPrimaryPage().getString(".pyCategory")) %>
<%=StringUtils.crossScriptingFilter(" | "+createOpName) %>
</div>
Blue Rose Technologies GmbH
BE
Hi Chunzhi,
Thanks for posting your query on PSC.
I created the same use-case as you mentioned and i too got the same result.
When i analysed further, i see that Work- pyCaseAttachments section contains two repeating grids which is differentiated with the .pyIncludeSubCases='true' as you can see in the attachment. As of now , I am not sure of why there it is like this but i will get back to you with update by tomorrow.
Thanks.
Accepted Solution
Pegasystems Inc.
JP
The issue is solved by customizing the control rule "pyAttachmentFeedDescription" as below.
<%
String createOpName = tools.getPrimaryPage().getString("pxCreateOpName");
createOpName = tools.getLocalizedTextForString("pxRequestor.pyUserName", createOpName);
String workID = tools.getPrimaryPage().getParentPage().getString("pyID");
if(workID != null && workID.length()>0){
//We are NOT looping over AllAttachments page which include attachments of covered cases.
tools.getPrimaryPage().putString("pyID",workID);
}
String clsName = tools.getPrimaryPage().getString("pyClassName");
String note = tools.getPrimaryPage().getString("pyNote");
if(clsName.equalsIgnoreCase("Data-WorkAttach-Note")){
note=tools.getPrimaryPage().getString("pyLabel");
tools.getPrimaryPage().putString("pyNote",note);
}
if(note==null || note.length()==0){
note = tools.getPrimaryPage().getString("pyMemo");
tools.getPrimaryPage().putString("pyNote",note);
}
The issue is solved by customizing the control rule "pyAttachmentFeedDescription" as below.
<%
String createOpName = tools.getPrimaryPage().getString("pxCreateOpName");
createOpName = tools.getLocalizedTextForString("pxRequestor.pyUserName", createOpName);
String workID = tools.getPrimaryPage().getParentPage().getString("pyID");
if(workID != null && workID.length()>0){
//We are NOT looping over AllAttachments page which include attachments of covered cases.
tools.getPrimaryPage().putString("pyID",workID);
}
String clsName = tools.getPrimaryPage().getString("pyClassName");
String note = tools.getPrimaryPage().getString("pyNote");
if(clsName.equalsIgnoreCase("Data-WorkAttach-Note")){
note=tools.getPrimaryPage().getString("pyLabel");
tools.getPrimaryPage().putString("pyNote",note);
}
if(note==null || note.length()==0){
note = tools.getPrimaryPage().getString("pyMemo");
tools.getPrimaryPage().putString("pyNote",note);
}
%>
<a class="Case_tools" title='<p:r n=".pyNote" m="normal"/>' href="#" onclick="pega.ui.HarnessActions.doAttachmentSingleClick('<p:r n=".pxListSubscript" />', '<p:r n=".pxObjClass" />',
'<p:r n=".pxInsName" />', '<p:r n=".pzInsKey" />', null, null, '<p:r n=".pxLinkedRefTo" />')">
<pega:reference name=".pyNote" mode="display" format="pzCMEllipsis">
<pega:param name="CharLength" value="25"/>
</pega:reference>
</a>
<div class="subsidiary">
<p:r n='.pyID' m='normal'/>
<%=StringUtils.crossScriptingFilter(" | "+tools.getPrimaryPage().getString(".pyCategory")) %>
<%=StringUtils.crossScriptingFilter(" | "+createOpName) %>
</div>