Closed
Connect-File and AWS S3 Repository
When configuring the connect-file rule Destination Path as with a File Listener (file://S3Connection:/folder) - testing the connect-rule and running an activity using it will return a message that the Destination Path does not exist.
Overall result
Status
Fail
Message
No such Directory or Folder: file://S3Connection:/folder/
Steps performed
|
***Edited by Moderator: Pooja Gadige to add platform capability tag***
To see attachments, please log in.
Posted: 4 years ago
PEGA
Pegasystems Inc.
IN
Posted: 4 years ago
Evonsys
Evonsys
IN
Hello Keith,
Did you find the resolution on the above query ?
We also have the problem statement.
Thanks,
Vaibhav Gupta
@KeithS73Hello , I don't think Connect-File is currently supported in PEGA AWS Cloud if that where your application hosted. Have you tried looking in to some of the PEGA OOTB repository APIs instead?
https://community.pega.com/knowledgebase/articles/data-management-and-integration/85/create-file-api
Below articles also might help you -
https://collaborate.pega.com/question/replace-file-connector-point-pega-application-pega-storage-repositories
https://community.pega.com/knowledgebase/articles/data-management-and-integration/84/repository-apis
https://community.pega.com/knowledgebase/articles/pega-cloud/cloud/pega-cloud-services-file-storage
https://collaborate.pega.com/question/connect-file-0