Custom Apps

While incredibly powerful and useful, the Custom App feature is limited since it requires manual interaction in a GUI to create and update applications. This becomes much more burdensome the more custom apps you have. What I would like to see once...

It would be great if we could have permissions on single Custom APPs or Folders within the Portel to give some Users Access to just those Applications. Why? That would mean f.e. our selection tools, the Department could get permission to upload th...

There are several applications (autodesk apps, Mastercam, masterworks, masterspec, National Instruments, solidworks, etc) today that are absolutely ridiculous to package. Given the annoyance and difficulty at packaging and automating the installat...

Currently the Custom App description field only supports ASCII characters. Could you please add support for Unicode characters like german umlauts.

A lot of the apps I've manually packaged for our environment are basically just PowerShell scripts for moving RDP sessions or shortcuts, or mapping SharePoint sites etc. Naturally, the standard (and excellent) installation, detection and uninstall...

The version support for custom apps (xx.xx) might not be suitable for all applications. It does not allow for example 2023a.

During the initial setup, a vendor name was added incorrectly. We need a way to remove any legacy entries in that field.

When creating a Custom App, the *.ico file format is no supported as "app icon". Many applications (e.g. VLC player) provide an ico file inside the setup file (archive). Please add support for this file type, or even better include automatic detec...

Add custom detection scripts for custom apps to support applications that dont add to apps and features

Many application installers don't have the standard exit codes and it would be useful if we could specify successful/reboot exit codes for these apps.