# Create a Custom Properties Profile element

A custom properties profile contains a custom script that can run on the NGFW Engine.

##

For more details about the product and how to configure features, click Help or press F1.

## Steps

1. Select Configuration.
2. Browse to Other Elements > Engine Properties > Custom Properties Profiles.
3. Select New > Custom Properties Profile.
4. Configure the settings, then click OK.

## Custom Properties Profile dialog box

Use this dialog box to create a Custom Properties Profile element.

Option | Definition
--- | ---
Name | The name of the element.
Type | Select the type of script to use. Custom — You can upload your own customized script. Azure — An advanced, predefined script for use with Microsoft Azure. For more information, see Knowledge Base article 16290.
Comment (Optional) | A comment for your own reference.
Category (Optional) | Includes the element in predefined categories. Click Select to select a category.
Script | The name of the script that you have selected. To select the script file to use, click Browse. To remove the script, click Clear. To copy the contents of the selected script to your clipboard, click Copy to Clipboard.
Scripts attributes table. Add rows to add additional attributes to your script. Click Add to add a row to the table, or Remove to remove the selected row.
Attribute | When the Type is Custom, you can use one of the following: To upload the script to the default location (/data/config/policy/<policyid>/scripts), enter `se_script_tester` as the attribute. To upload the script to a custom location, enter `se_script_path` as the attribute. Add any additional attributes that your script can use.
Format | Select from the following: String — The value is passed to the script as plain text. Encrypted — The value that is passed to the script is encrypted.
- Value | When the Type is Custom, you can use one of the following: To upload the script to the default location, enter `1` as the value. To upload the script to a custom location, enter the path as the attribute. You can also rename the script by adding the new name to the attribute. Example:
      /data/config/hooks/policy-applied/custom_script_renamed.sh
If you added additional attributes, add the corresponding value.