Question
Lloyds Banking Group PLC
GB
Last activity: 22 Apr 2024 9:13 EDT
Attachment file type restriction
Hi, We are using upload file feature from util pane on right hand side of the case. This is pzManageRecentContent flow action. On click of submit, it is internally calling AttachFile activity.
As per our requirement, we have to restrict a few file types format. We have achieved this by customizing CallVirusCheck activity.
However, after getting error message - if we try to upload a valid file type, it's throwing an error message - "pySameAsCurrentStage"
your advise will helpful. Thank you
Accepted Solution
Updated: 8 May 2024 9:35 EDT
TATA Consultancy Services
IN
We raised an SR recently for this issue and it is resolved now for us.
The fix is in the HistoryAndAttachments harness--- display options tab---
Form levels errors should be changed to in configurable section
Custom error section could be pyCaseErrorSection
JPMC
IN
@VENKATESH GUDEENTI I was able to replicate the issue, I see that they are creating a case of PegaSocial-Document on page AddRecentContent and if there are any errors during attachment processing, error is presented but the page is retained. When we try to upload a different or valid document they are trying to initiate a new case but on the same page which was used earlier (AddRecentContent) which has all the metadata like stage name, assignment, pxflows which seems to be causing this issue.
Request you to raise a SR using MSP portal.
Instellars
SG
Accenture
SG
Have you tried adding the same validation in OnAdd(PegaSocial-doument) validate rule ?
Create a DSS with all invalid file extensions / valid file extensions, in the validate rule check whether the uploaded file extension is there in the DSS list.
Uploaded file details details will be on dragDropFileUpload.pxResults(1)
Thanks,
Vinay
Instellars
SG
Personal
IN
@VinayKumarL16594575 Can u plz help me with the steps or screenshots.. I am facing same issue
Accepted Solution
Updated: 8 May 2024 9:35 EDT
TATA Consultancy Services
IN
We raised an SR recently for this issue and it is resolved now for us.
The fix is in the HistoryAndAttachments harness--- display options tab---
Form levels errors should be changed to in configurable section
Custom error section could be pyCaseErrorSection