Version 6.8.x
Cloud Storage Support—ProfileUnity and the FlexApp Packaging Console now support using FlexApp packages that are stored on cloud storage. The following cloud storage platforms are supported: Amazon S3, Microsoft Azure Blob Storage, and Google Cloud Storage. FlexApp Packages can be created and stored on cloud storage. In addition, FlexApp Streaming allows applications to start while they are still downloading from cloud storage.
Cached Mode Support—FlexApp Packages can be configured to replay using a cached mode on user desktops, which is particularly helpful with inconsistent network connections, SMB shares behind firewalls, and routers that have many hops. In cached mode, ProfileUnity requests blocks of the FlexApp package and stores them locally so the next time the block is referenced, it is read from local storage. This can be set in the FlexApp DIA Configuration Module by selecting the Cache Blocks Locally checkbox.
Liquidware Apps—Liquidware has pre-packaged some popular applications and made them available to all users for immediate use via cloud storage. If a FlexApp package is a Liquidware app, the 
(Liquidware Drop) icon appears in the lower right of the application icon. Liquidware apps can be cloned and edited for use in your own environment. As a general rule, Liquidware apps are intended for deployment to desktops running a 64-bit operating system.
Version 6.7.x
Application Session Isolation—FlexApp has enhanced application delivery support for Citrix XenApp and Microsoft RDSH environments by providing session-based layering. Before, all applications published on a server were visible to all connected users whether they need them or not. Now when FlexApp applications are delivered to a user’s published desktop, other users are not automatically exposed to those applications. Every user’s desktop can remain unique, even for users on the same Windows Server environment.
Click-To-Layer—FlexApp now offers the option to decide which application packages are automatically layered into a user’s desktop environment. Packages can be layered in during the login process or later upon the user’s request. Enabling Click-To-Layer for a package improves desktop readiness times because applications are not mounted until a user actually opens the application to use it. Click-to-Layer extends to published application environments as well with the added benefit that after one user opens an application, that application will only need to be layered into the server environment once for all users. Any subsequent demands to use the application will not experience any delays because the application will have already been mounted in the server environment.
Automatic Reboot Handling—The FlexApp Packaging Console now fully supports packaging applications that need a reboot during the installation process. As part of the packaging process, the FlexApp Packaging Console executes the application’s installer. If an application needs a reboot as part of the installation process, the packaging process is put on hold, the reboot occurs, and then the FlexApp Packaging Console starts back up to seamlessly finish the packaging process.
Package Dependencies—The FlexApp Packaging Console allows users to designate dependencies between other application packages to control the layering process. There might be cases where independent FlexApp packages relate to one another. For example, Microsoft Outlook uses Microsoft Word to create and edit emails. Ideally, Microsoft Word would need to be in place before using Microsoft Outlook. Setting FlexApp package dependencies helps to control how FlexApp packages are layered into the user environment at login. A package will not be made available for use until its dependencies are first layered in and active.
Integrated Cap File Editor—Starting in version 6.7.5, the former, standalone Cap Editor has been fully integrated into the FlexApp Packaging Console. The original Cap Editor allowed administrators to make registry changes to FlexApp packages or layers created with version 6.5.0 and higher. With version 6.7.5, the editor’s functionality has been expanded to include the ability to edit file systems and registry settings.
