As a user, I have little understanding of the internal states of Zenworks bundles. So I prefer either not seeing the internal state data at all or only the data relevant to me:
1. When looking at the application window, I am just interested in whether a bundle has already been installed or is ready to be installed - and this information should be conveyed in a language familiar to me. The current state of displaying "Available" when the bundle is installed, "Downloaded" when it has been distributed and "Not installed" when it has not yet been distributed is definitely not familiar wording. "Installed" and "Not installed" would be, but I'd rather like a smartphone-store-like experience with action buttons for "Install", "Uninstall" and "Open", displaying depending on the bundle state
2. when looking at the "Version" field, I am certainly not expecting the internal bundle version my Zenworks administrator has published but the product version of the software which is being installed. The internal bundle version is not the kind of information I can use in any sensible way.
3. The "Last Associated Time" does not convey any useful information as I have no idea about bundle assignment schedules and refresh cycles
4. When I see "System requirements failed" as a bundle state, I immediately suspect a malfunction of my computer and call the service desk - which I should not since this state really only means that the bundle is not compatible with my device
by: Denis J. | over a year ago | Application Mgmt
Comments
I should add that many of the points mentioned can be addressed by editing zapp_bundles_*.json in %ZENWORKS_HOME%\zapp\i18n and just replacing the default texts with the ones we want. But even with this, we cannot change "Available" to "Installed" as this seems to be hard-coded to the bundle state returned by the agent. Removing fields like last associated time and version is not possible using this approach. Also, the approach is not documented in the official Zenworks documentation and not supported, which is a no-go for larger organizations.
related: https://ideas.microfocus.com/MFI/novell-zcm/Idea/Detail/12424
related: https://ideas.microfocus.com/MFI/novell-zcm/Idea/Detail/14685