Posted: 8 Aug 2017 11:06 EDT Last activity: 11 Aug 2017 8:00 EDT
how to pass file name to attach content smart shape dynamicaly
I have a flow and there is attach content shape inside. The attach content will retrieve the file from binary file rules. the requirement is based on different condition, the binary file name will be different.
try to assign a parameter to it but always complain file not found. it seem it only accept hard code name only.
***Edited by Moderator Marissa to update categories***
The concept is pretty same in both the versions of pega, the only important point to notice is the value of the property which you are using to initialize the value of param.FileName in connector properties. When the execution comes to this flow the value of the property you are using need to be initialized with the file name, so that it will be initialized to Param.FileName as shown in attachment.
Note: May be you can write a data transform to initialize the filename of your source property before the execution of this flow so that the value of file name will be available in the property you are using by the time of Connector properties.
I did exactly same as your instruction. but still get the error message " invalid file name mentioned in attachment". I traced it, the file name is passed in but it complained application name. if use the file name inside the shape, system can find out application name internally. but using param, no name found. even I tried to pass AppName as param, no lucky. I attach screenshot for your ref.
Thanks for sharing the screen shot of your use case, after my analysis of your document noticed that you are selecting the wrong Attachment Category name i.e. Documents instead of File. FYI, pega-7-logo is a file type category, kindly try to change the category in Attach Content settings to File then try.
Run the use case with tracer on then click on Save in the tracer window which downloads the tracer file in XML format. Copy the whole text into text file and share it with us for our further analysis as this issue looks pretty strange at your environment.
Thanks for sharing the tracer file. After analyzing the tracer log noticed that the BinaryFilePage is still holding the same old stale data as shown in the attachment. Because of this wrong Attachment Category the FileType property also wrong.
Suggestion: Change the Attachment Category from drop down with value File as explained above then try to test your behavior with the new work object.
If still its not working then i would request you to raise an SR with GCS for further investigation on this issue as its needs screen share to understand further.