- 29 Nov 2022
- 12 Minutes to read
- Updated on 29 Nov 2022
- 12 Minutes to read
The Packages configuration is where you'll manage everything related to the packages (Apps) you make available to your users.
You'll be presented with a list of all the configured packages in your Liquit system. Click on the 'Add' button to create a new package.
There are a lot of different options to choose from, so we'll detail them in the next sections.
The details screen provides basic options to configure the package.
|Name||The technical name for the package|
|Type||A type for the package|
|Icon||The icon associated with the package|
|Priority||This field is used to determine the execution order when multiple packages are assigned to an event (on a user or device entitlement), the order of execution is from low to high|
|Enabled||Determines whether or not the package is enabled and available for use|
|Agent Required||Determines if the package is only available when an agent is running|
|Offline||Determines if the package is available for end users that use the offline mode of the Liquit Workspace Agent, this causes the package content to be distributed on login/refresh, to ensure that the package is available for launch/installation actions|
|User auto launchable||When enabled, gives users the option to start this package on logon. For this to function, the agent should not have events disabled.|
The "Events" tab displays all events that are associated with the package.
The following columns are available:
|Type||The type of event associated with the package|
|Status||Shows wether or no the the event was completed succesfully|
|Identity||The user that triggered the event. Example given the user whom initiated a package launch|
|Device||The device the user was connected on when the event was triggered|
|Package||The package asssociated with the event|
|Time||The time the event has triggered|
The "Entitlements" tab allows you to assign packages to identities by using entitlements. This grants users or devices access to an application. The list allows you to add and remove entitlements. You can edit an entitlement by double-clicking it.
|Identity||User, Group, Device, Context or Device Collection for this entitlement|
|Stage||Release stage (or higher) that is used for this identity, only available for Release & Patch license|
|Publish||Package icon can be published in one of these initial stages:
|Native Icons||Publish an icon for this package within the OS (Windows), an agent is required on the device.
|Approver||When set gives this identity the rights to accept an application request (from other users). When atleast one of the identities on a package has been assigned with Approver rights, this will automatically active the approval system on this package.|
|Managed||A managed entitlement can not be modified and is received from a connector that manages the package.|
An event can be configured to trigger an action on this package. The following events are available:
|Liquit Logon||Trigger when a user is logged in to the Liquit Workspace.|
|Refresh||Trigger when an automated refresh is triggered.|
|Session connect||Trigger when a remote desktop session is connected/reconnected|
|Session disconnect||Trigger when a remote desktop session is disconnected/interupted|
|Session lock||Trigger when a desktop session is locked|
|Session unlock||Trigger when a desktop session is unlocked|
|Agent startup||Trigger when the agent service is started. This event is only available on device assigned entitlements|
|Device startup||Trigger when the device is started. This event is only available on device assigned entitlements|
|Device shutdown||Trigger when the device is shutdown. This event is only available on device assigned entitlements|
|User login||Trigger when a user logins in on the device.|
|User logout||Trigger when a user logs out on the device.|
|Network change||Trigger when a network (interface / adapter) change occurs. The changes are grouped together when there is less than 5 seconds in between them, grouping will happen over a maximum time frame of 20 seconds.|
The catalog screen provides basic options to configure the manner in which the application is offered to the end user.
|Display name||A friendly name for the application, this name is used to display the application title to the end-user.|
|Featured on the catalog||When checked the package will be featured on the catalog.|
|Excerpt||A shorter version of the application description, this will be shown in the catalog.|
|Description||A description for the package, this is used to offer a synopsis for the application.|
|Website||Allow users to visit a website associated with the application, this can be the official website or for example a knowledge base article within the organization.|
The reviews screen let’s you manage the reviews made for the application, these can be moderated or deleted.
The media screen allows you to add images which are displayed within the end user catalog.
- YouTube Videos
To add a YouTube video to a catalog item you need to provide it's url (for example: https://www.youtube.com/watch?v=nHfUTbstZnQ).
For the YouTube videos to load properly you need to add the following url to CORS and CSP in the security settings:
The FAQ allows you to add the Frequently Asked Questions to the end user catalog.
When you choose the “Add question” button, a dialog will popup which allows you add the Frequently Asked Questions in question and answer form.
The “Tags” tab shows a list of tags associated with the package. The list allows you to add and remove Tags. You can edit the Tag by double-clicking it.
The “Licenses” tab shows a list of tags associated with the Package. The list allows you to add and remove Licenses. You can edit the License by double-clicking it.
The "dependencies” tab allows you to view the Dependencies and Dependents of the Package. It lists all the packages it references or where it is referenced by. When you double click a entry the referred action is displayed.
An individual package can have different package snapshots in different stages, the available stages within Liquit Workspace 3.0 are: Development, Test, Acceptation and Production.
Packages can only be modified at the development stage and can be deployed to development devices for testing purposes, before they are published to one of the other stages.
Which stage gets published to the user is determined by the package entitlements, where an entitlement based on user, group, device or context can be configured within a certain stage.
This allows you to control which users or groups have access to specific stages on a per package basis.
Packages staging allows you to:
- Test updates in multiple stages of the application lifecycle before its deployed to all users in the Production stage.
- Updates coming from Liquit Release & Patch can be applied in a test stage, or order be tested on a selection of devices before rolled out in production.
Shortcuts allows you to define multiple icons for a single package that are published within the Workspace, but are listed as a single item in the Catalog.
Shortcuts for packages has been added since Liquit Workspace Server 3.7, please upgrade to Liquit Workspace 3.7 or higher when you need this functionality. Shortcut behavior is only available when Agent 3.7 is installed.
When creating a new shortcut you get the following options:
|Name||The short name of the shortcut. Only characters that can be used to identify the shortcut are: a-z, 0-9, - and _. This is a techincal name that will be used to identity the shortcut.|
|Display name||Name used to display this shortcut to the end user.|
|Icon||Icon used for this shortcut, if not set, will use package icon.|
|Enabled||Defines if the shortcut should be published to the end user.|
|Description||Describe what this shortcut is for.|
The behavior of shortcuts can be defined within Actions, this is done by creating a new Launch Action Set for a specific shortcut.
A "primary" shortcut is always available on a package and can't be removed. The primary shortcut controls the icon to access the package itself. A display name can be configured that overrides the Catalog display name. The catalog name will be used when display name is not configured on the Primary shortcut. Primary shortcut can also be disabled, which will hide the primary shortcut when the application is added to the Workspace.
Variables give you the tools to be as dynamic as possible.
Variables can currently be defined on different levels, the inheritance flows top-down and support local override. This means a variable defined on system level, can be used in contexts and packages. That same variable could be overriden on for example package level, to provide dynamic customization based on the entity.
This allows very dynamic setups while using a simple mechanic.
To use variables, you add them as illustrated below:
For a variable named 'MY_CUSTOM_VAR' you would use the following notation in fields that support variables:
Filters allow you to define when a package is available for a user/device based on certain requirements. For example: only enable a package if a certain file is available on the device that is used to access the Liquit Workspace.
Filters are contained by Filter Sets, it is possible to use these sets in a OR or a AND clause.
Action define what a package does when a end-user starts an application. Actions themselves are contained by Action Sets. When creating a new Action Set you get the following options:
|Name||The friendly name for the Action Set|
|Enabled||Determines if the Action Set is enabled|
|Type||The type of the Action Set determines how the Actions are executed the following options are available:
|Shortcut||Shortcut selection is only available on a Launch Action Set. Select the shortcut that this action set belongs to.|
|Process||Determines the way Actions contained within the Action Set are executed, the following options are available:
|Frequency||Depending on the Action Set type there will be different options:
|Filters||Here you can filter if the action set should be executed.|
When an Action Set is created Actions can be created within it, for a complete list of the Actions please review the package actions documentation. Actions can also be deleted or copied by clicking on the corresponding icons.
The recycle bin for packages has been added sing Liquit Workspace Server 3.5, please upgrade to Liquit Workspace 3.5 or higher when you need this functionality.
When you remove a package the package will be placed in the recycle bin. All archived packages will remain in the recycle bin until the "Clean packages" scheduled task has been successfully executed.
You can access the recycle bin by clicking the "Recycle bin" icon in the package list.
When you access the recycle bin you are able to perform the following actions:
|Restore||When you have selected one or more packages you can choose to restore them. Whenever Liquit Workspace encounters a package with the same name a window will ask you to rename the packages which are duplicate within the system. When the package(s) are successfully restored they will be placed back to the list of active packages and can be assigned and edited like any other package.|
|Remove||When you choose to remove packages from the recycle bin, they will be permanently be removed from the recycle bin. There is no way to restore them after they are removed from the recycle bin.|
The release dashboard for packages has been added sing Liquit Workspace Server 3.7, please upgrade to Liquit Workspace 3.7 or higher when you need this functionality.
You can view the Release Dashboard by clicking the "Release Dashboard" icon in the package list.
The Release Dashboard shows a overview of all packages. In this list you can find the version numbers corresponding with the Development, Test, Acceptance and Production stages. Additionally you can find the source for the application (The Liquit Setup Store for example). This view makes it easy to determine which packages need to be updated.