File Manager

Enter the new directory name here and click on OK.

Please follow these rules for valid names:

Allowed characters: letters, numbers, underscore (_).The name may not begin with a number.

When adding files, please note: Velocity Includes that are only used on the server and may not be directly requested from the Internet should be given the file extension .vmi. Otherwise, they should be given the extension .vm.

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/<GUID>/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.