The Applications area shows all available software installation packages inside your account.
The table shows the following information:
This is the vendor for the application.
The name of the application.
The version from the application installer or executable.
The revision of the deployment script.
The target operating system.
Remember: We always create application installations for specific operating systems in our extensions. That makes it easier to maintain installation files for and after migrations to other operating systems.
The architecture of the installation.
There are three possibilities: x64, x86 or any.
This is the language of the installation package.
Can be everything from: EN, DE, ES, RU… or ANY, if the language doesn´t matter.
This is a classification that we are using for PSADT packages because you could use the framework for other purposes than application installation as well.
Possible values are:
- APP - Application
- DRV - Driver
- USR - User Configurations
- SYS - System Configuration
This is the author of the installation script.
This is the time of the application upload via our infra.XO frontend.
The actions column shows the currently supported actions that are available for an application.
The application information is automatically integrated during the PSADT upload process and is directly connected to the variables area in the deplyo-application.ps1 scripts:
[string]$packageName = "APP_Citrix_DiagnosticsFacility_7130_W10_x64_Any" [string]$packageType = "Application" [string]$appVendor = "Citrix" [string]$appName = "Diagnostics Facility" [string]$appVersion = "188.8.131.52" [string]$appArch = "x64" [string]$appLang = "Any" [string]$appRevision = "06" [string]$appScriptVersion = "1.0.0" [string]$appScriptDate = "01/07/2018" [string]$appScriptAuthor = "Sinisa Sokolic" [string]$appTargetOS = "Windows 10" [string]$appTags = "Citrix" [string]$installName = '' [string]$installTitle = ''
These are the currently available actions.
Downloads the PSADT zip file from the backend.
This action is used to create a custom application configuration.
Deletes the PSADT package from the backend.
Be carefull with this action, as it is irreversable and the package must be uploaded again afterwards.
By deleting a node it is detached from the backend. The node is not deleted physically or virtually, only the reference in the config.XO frontend is removed and the node won´t get any configuration updates anymore until you re-register the node.