Automation / Efficiency

At the moment, I need to create a separate package for each script I want to use. These packages are then referenced in a Launch Package action. While this approach works, it has a major limitation: it does not allow returning exit codes from the ...

Having the ability to set a maintenance window for either a group or application would greatly improve the application experience. Currently the only solution to this is either manually setting the entitlement during the time or setting a filter b...

We have a golden image proces for our VDI's and use the bootstrapper to issue an deployment. This deployment contains packages like Google Chrome and 7-Zip. These packages may be updated shortly after we have build the golden image. We would like ...

Since version 4.3, Recast Application Workspace introduced the ability for end users to send diagnostic logs to IT administrators. This has proven to be an extremely useful feature in troubleshooting and support scenarios. However, from an IT admi...

A github connector for private and public repos would allow automation and version control

We wish Recast would integrate Right Click Tools to App Workspace (Liquit), at least for adding entitlement (delivery) target resources to a collection or group. Currently, we're using PowerShell script but why can't this just be a right-click UI ...

We want to be able to go to Connectors -> Setup Store Connector -> Release: Publish to Production. By Default it's set to Development when we create this connector through Powershell. Also we want to be able to go to IdentitySource -> Con...

The GUI right now allows you to make custom views were filters and/or collums are enable or disabled. However whenever you leave the page the custom view is removed and the default view is selected. I wish the GUI would either remember my last vie...

Currently it is possible to configure a variable on the level of a context (not inherited) using the web interface but not using powershell. Powershell cmd-lets New-LiquitContext or Set-LiquitContext do not have the possibility to define variables...

In a migration scenario I would be able to get an image (background for example) using a powershell command, but I'm not able to set the image I got using Set-LiquitSetting. Following error is shown: Set-LiquitSetting : Failed to convert value for...