Contents Hide
The applications node of a BrightServer instance contains a list of all successfully deployed applications and their deployment numbers on the server. Using this panel, deployments made to the server may be monitored, and downloaded if necessary as a BSP project for editing.
To browse the deployed configurations of a server, connect to the server in BrightBuilder and access the 'Applications' node.
 
This will open the 'Applications' viewer. The left hand side of this panel displays a list of applications which are on the server, which may be tapped to display a read-only deployment history for the particular application.
 
The columns in this table are as follows:
Deploy Version: The version number assigned to the application's deployment, with the highest number being the most recent deployment. Referenced when releasing the application to users in the system.
Time Deployed: Date and time the application's BSP was deployed to the BrightServer instance.
Deployed By: Username of the account used to sign in and deploy the application.
Description: Optional text entered at the time of deployment for the application.
'Get Selected Version' may be tapped to download a selected deployment to a BSP file on the local machine. When tapped, a folder picker dialog will open, which selects the path of the downloaded file.
 
	A dialog confirming the download will appear on success. The naming convention of the file downloaded will be <application name>.bsp.<deploy version>.
 
	The 'Delete Selected Version' button may be tapped with application row selected to delete an application deployment from the repository. Only applications which are not assigned to users may be deleted with this feature.
If an application has a single release, and this release is deleted, the application will be removed from the 'Application Name' table.
Please 
		 note that it is recommend to use this feature to remove deprecated 
		 versions of the BSP projects in this panel. As such, it is recommended 
		 to deploy and assign the updated BSPs first, then perform deletions. 
		 This is to ensure no issues occur with Application Distribution, 
		 which relies on the version number of the project.