In my environment, installing Core Data Bundle to network drive ("prepare a network install") runs for hours or days due to network factors. If interrupted, I need to start from scratch again.
These changes would greatly improve the installation:
- Maintain verbose installer log to track progress and confirm that all selected files are successfully installed.
- Add a repair mode to the installer to repair interrupted installations. When run in this mode, only missing/corrupt data files will be re-installed as necessary (much faster than fresh install).
- Support use of a shortcut like "CURRENT" on my network drive to the real installation directory (say "Q3_2017"). This would allow me to point to the latest release and users who "register from a network location" via "CURRENT" shortcut path will always get the latest data files. As an administrator, I have no way to know if my Alteryx users are configured to use an obsolete data set that I want to clean up from my network drive.
- When I prepare a network installation, I'd like to specify an expiry date and warning message that users will see in their workflows if they access obsolete data sets. Example: "Core data set XXX is obsolete as of 12/31/2017. Register current version via \\my-network-drive\alteryx\???\DataInstall.exe...". Nice to have would be a warning date and an error date to provide grace period. This would be similar to the CASS data set expiry date.