File storage and knowledge management repositories store assets and provide versioning and metadata support. Pega Platform can communicate with common repository technologies and can also act as a binary repository.
You can use repositories as follows:
- In a continuous integration and delivery pipeline, to provide centralized storage for software that is to be tested, shipped or deployed. Pega Platform can browse, publish, or fetch artifacts that are created whenever an action creates a RAP: for example, exporting an application, product, branch, or component.
- In case processing, to store and source file attachments.
Pega Platform includes wizards to create the following repository types.
- JFrog Artifactory
- Amazon S3
- File system
- Microsoft Azure
- Pega Platform
You can also create custom repositories that behave in the same way as the repositories shipped with Pega Platform. For more information, see Creating a custom repository.
The repository is an instance of the Data-Repository class which holds all information required to connect to a repository.
Access to repositories is controlled by roles:
- PegaRULES:RepositoryAdministrator – The user can create, modify, and delete repository instances and browse and fetch contents from the repository. The PegaRules:SysAdm4 role includes this access.
- PegaRULES:RepositoryUser – The user can view repository instances and browse and fetch contents from the repository.
- File and content storage
You can control where case and Pulse attachments are stored and sourced for your application. There are different types of content storage types that you can use. The storage type is based on the content storage vendor that your business uses, your expected file size, and the number of concurrent uploads/downloads.
- Viewing file storage destinations
The file specification, also called the file spec, is the path to the file storage destination. View the structure and the contents of the file storage location to help in troubleshooting.
- Creating a repository
Create connections between Pega Platform and repositories to provide centralized storage, versioning, and metadata support for file storage in your Pega application. For example, you can store and source file and case attachments, or for use in a DevOps pipeline configuration.
- Using repository APIs in your application
Interact with any defined repository by using the default repository APIs that are included in Pega Platform.
- Map eForm rules
The SmartForms capability enables your applications to work with PDF files. Your application can extract field data from incoming PDF forms and can generate PDF forms and documents.
- Secure file transfer in Pega
Pega Cloud services and on-premises users can securely transfer files to or from any Pega Platform application by using two file transfer protocols (FTP).
- Using file listeners
Use a file listener with a file service to import and process files from another system or that have been created by application users. For example, you can import data that is used to create a work object.