Advanced Update/Patch Management & User-Controlled Update Experience

On the advice of Ben from support, I am submitting the following feature request:

We would like to request a major enhancement to the software update capabilities in Recast / Liquit Application Workspace. The goal is to provide a modern, user-friendly, and flexible update experience, similar to the Software Center model used in Microsoft Endpoint Configuration Manager, while still ensuring IT retains full control over compliance and security.

Requested Functionality

Ability to Push Software Updates to Clients
A native mechanism to push updates directly to endpoints, either immediately or according to a schedule. This should allow IT to:

• Deploy updates proactively

• Ensure critical patches are delivered without user dependency

• Trigger updates per device, per group, or globally

This is essential for security-driven environments where waiting for user-initiated actions is not acceptable.

“Updates” Tab / Update Overview for End Users
Introduce a dedicated Updates section in the Workspace interface where users can view:

• Available updates

• Installed updates

• Deadlines

• Update descriptions

• Required system restarts

This would greatly improve transparency and adoption.

“Available From” Date/Time for User-Controlled Installations
Allow an update to become available at a specific date/time, after which:

• The user may install it at any convenient moment

• Users remain informed but not forced immediately

• IT can prepare updates ahead of time but expose them only when appropriate

This improves user experience and reduces disruption.

Deadline Enforcement for Mandatory Updates
In addition to "available from", we propose a deadline field:

• If the deadline passes, the update is automatically and forcefully installed

• Ensures compliance for high-priority or security-sensitive updates

• Provides balance: user freedom first, enforced compliance later

This aligns with modern update management patterns.

Device Collections Based on WMI Queries / System Inventory
To support targeted deployments, we need the ability to build dynamic device collections based on system data collected via WMI queries.

This requires:

• A central data warehouse storing device inventory

• Regular sync of system properties (installed software, versions, OS build, hardware state, etc.)

• Ability to create collections such as:

  • “All systems with Notepad++ installed”

  • “All devices running version X of software Y”

  • “All laptops with battery health < 40%”

This enables highly accurate and safe deployments.

Use Case 1: Targeted Software Updates (e.g., Notepad++)
We want to deploy a Notepad++ update only to systems where Notepad++ is installed.
Without WMI-based collections or inventory data, we must rely on workaround filters like “file exists”, which is functional but:

• Not as reliable

• Less scalable

• Harder to manage at scale

• Requires IT to force-install patches rather than offering controlled rollout

Use Case 2: Security Vulnerabilities
When addressing urgent vulnerabilities, we cannot rely on users clicking Smart Icons.
We need:

• Immediate ability to push updates

• A visible update entry in the Updates tab

• Forced installation at deadline

• Clear communication to the user

This ensures security while still offering a better user experience when urgency allows.

Use Case 3: Improved User Experience & Reduced Friction
Users can decide when to perform non-critical updates while IT decides if the update is mandatory.

This hybrid model provides:

• User autonomy

• Reduced workplace frustration

• Lower helpdesk load

• Better scheduling around meetings and workload

• Still full compliance when deadlines hit

Implementing this feature set would result in:

• A modern, intuitive update workflow

• Stronger security posture due to forced deadlines and push capabilities

• Reduced operational workload for IT

• Targeted, accurate deployments based on system inventory

• Consistent user experience aligned with industry standards

• More trust and transparency for end users