Differences

This shows you the differences between two versions of the page.

--- decimal3d:instructions_for_use:instructions_for_use [2019/08/19 13:11] – created dpatenaude
+++ decimal3d:instructions_for_use:instructions_for_use [2019/08/19 13:12] – [Release Management (Launcher)] dpatenaude
@@ Line 95: / Line 95: @@
-==== Release Management (Launcher) ====
-The astroid Planning App is installed and launched from the astroid Launcher. The Launcher program provides the following functionality in regards to the Planning App:
-  - Ensures that all users at a site are using the same version of the application
-  - Ensures that the local Planning App client stays in sync with the latest release version (as set via Thinknode)
-  - Provides user authentication and password management
-When an application update is available via the astroid Launcher, the users will be required to install the App in the Launcher. This is accomplished by selecting the //Install// button for the specific app. Within a few minutes, the app should be downloaded and installed locally for the current user account. The user will then be able to launch the released app version from the astroid Launcher.
-By using the astroid Launcher, users can log in to multiple realms with each realm using a different app version. This allows for scenarios of using non-clinical or research application versions from the same user account or workstation without the overhead of managing multiple installations. By logging into a realm, the user is required to use the installed client version for that realm.
-Details regarding the specific requirements for computers on which the Launcher and Planning App client applications will be installed can be found on the [[planning:userguide:systemrequirements|System Requirements]] page.
-=== Releasing a new App Version ===
-In order to "push" a new Planning App version to the astroid Launcher, the dev-launcher realm must be updated to include an RKS entry for the new version of the application being released. The //client_version// record references the immutable data for the application package that contains the file system contents for the app versions (executable, dlls, etc.). The RKS hierarchy for this realm should be as follows:
-  * **<client>** (e.g.: planning)
-    * **<client_version>** (e.g: 1.0.0-beta1)
-      * References Immutable: <code>{
-  "reference": "<immutable_id>",
-  "path": "planning_app.exe"
-} </code>
-    * **<client_version>**
-  * **<client>**
-    * **<client_version>**
-For the launcher to register that an application should be installed for a realm, the //client// app with the //client_version// matching the dev-launcher RKS records should be installed into that realm. Please note that since the Launcher uses the //dev-launcher// realm for storing its records, all users of the Launcher will need permissions to read from this realm. Also, permissions to install/change app versions in Thinknode can be limited using Thinknode policies. Specifically, the //iam:realms:installVersions// permission is used to control this accessibility.
-For Example: from the above RKS hierarchy example, the application client named //planning// with client version //1.0.0-beta1// should be installed in the intended clinical realm where users would need to access this version. When a user logs into the astroid Launcher and selects the clinical realm, they will have the ability to automatically install and launch that application version.
 === Release Notes ===