JavaScript is disabled on your browser.

Velocity File Manager

All Velocity files can be organized in directories here. Click Add to create a new directory. Select the Directory menu item.

A new Velocity file can be created from the File menu item.

If you select a Velocity file in the directory structure in the left-hand area of the dialog box, you can click Edit to open the Velocity Editor automatically. You can use this to enter your file contents.

Edit Directory and File Name

You can also open the Velocity file manager via the menu item Edit / Edit Script / Edit Velocity Script. Here you can edit the directory and file names.

To do so, right-click to open the context menu. Here you have the menu items Edit (if a file is selected), Delete, Rename, Copy, and Insert available to you, which you can use to comfortably organize the structure of your directories and the files contained within them.

Security notice

Files with the extensions .vm and .vmi that contain Velocity scripting code are Velocity files. Velocity files can only be executed if they are stored within certain subdirectories of the portal's directory. These subdirectories are:
  • internal/system/vm/
  • internal/layout/vm/
  • internal/application/vm/
  • internal/application/resource/
  • internal/workflow//velocity/
Velocity files that end in .vm can be called up diretly from the web using URL parameters. If necessary, permission verfications must therefore be performed in the code of the VM files, so that unauthorized access to sensitive information is prevented.

Examples

Verify read permissions for a data group: $AccessController.hasDatagroupPermissionFromPage($ProcessingContext, $appGuid, $dataGroupGuid, "read")
Verify access permissions for a page: $AccessController.hasPagePermission($appGuid, $pageGuid, "access")

The file extension .vmi stands for Velocity-Include files. As opposed to Velocity files with the extension .vm, VMI files cannot be called up directly from the web. For this reason, security checks, which have already been performed in the calling Velocity files, do not have to be performed again in VMI files.