Skip to main content

 –

Creating binary file rules

Suggest edit Updated on July 21, 2021

Enhance and customize your application by creating a binary file rule that stores a graphics file, such as an image, or other non-text file. The binary file rule type provides the security, inheritance versioning, and deployment benefits of rule resolution to a file.

For example, you can upload a custom image to your Pega Platform environment and use the image in your application. You can upload different resources, such as icons, fonts, and locales.
  1. In the header of Dev Studio, click CreateTechnicalBinary File.

  2. On the rule form, in the Label field, enter a name for your rule.

  3. In the App Name (Directory) field, enter the name of the destination web server directory for this file when the system extracts the file from the database.

    For example: To use a subdirectory on the application server, enter webwb.
  4. In the File Type (extension) field, enter the file extension.

    For example: To upload a graphics file, enter jpg.
  5. To change the application layer in which to store the binary file rule, in the Context field, select another built-on application.

    By default, the system stores the rule in your current application layer.
  6. In the Add to ruleset list, select a ruleset and a ruleset version in which to store the rule.

  7. To override the default work item that your application associates with this development change, in the Work item to associate field, press the Down arrow key, and then select a work item.

    For more information about your default work item, see Setting your current work item.
  8. Click Create and open.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us