jFrog Artifactory Integration with PEGA : Dynamic Repository KEY allowed ?
Hi ,
I have configured a jFrog Artifactory (Azure-based) in the jFrog Cloud instance, and the connection has been established with the PEGA server.
Now, a limitation I see in the implementation is , whenever a new file is being pushed to the Repo, it is being pushed to the same master folder, but my requirement is to have different sub-folders created for each Case ID I am using.
Can the Repository KEY be allowed to be dynamic in the Repository configuration ? I see there is a OOTB Data page called D_pxNewFolder , but it is not being used anywhere to allow some form of dynamic behavior.
***Edited by Moderator Marije to add Capability tags***