Dream Factory by TruBridge Ideas Portal
Add a new idea Subscribe
Status Unlikely to Implement
Categories Technical
Created by Paul Hendrix
Created on Nov 14, 2023

RELATED IDEAS

Formalize CPSI version naming scheme and clarify versions for different systems.

Formalize CPSI Version Naming Scheme

Currently, CPSI's version numbering is inconsistent. For example, if you log into CPSI and go to Special Functions → System Management → Change Management System, there are three different numbers that reference the same version: 210505, 2105.05, and 21.05.05. Ideally, these would all be written the same way.

As an alternative, I believe it would be more useful if they were prepended with the year and month followed by incremental numbers for new versions. For example, the version number 2023.11.000 would tell me that this version of CPSI was released on November 2023 and is the very first version in this month.

This would benefit all department directors who would have context for when an update is/was available just by glancing at the version's number. In the same vein, this style of numbering would help quickly indicate if their system is up to date.

One downside would be the loss of the major.minor scheme that benefits engineers/coders. A workaround could be using a mixture of dates and hierarchies. For example: 2023.11.1.1

Clarify Versions for Different Systems

If you log into Thrive and in the file menu go to Help → About, the version number shown is the Clientware's version, not the system's version. Its label should be "Clientware Version", not "Version" to reduce any confusion.

In addition, it would be helpful if the following was displayed in this same section:

  1. The system's version

  2. Brief explanation of version's naming scheme

  3. A link to view release notes

Screenshot 2023...
Screenshot 2023...
Screenshot 2023-11-14 at 10.49.56.png
Open full size
Screenshot 2023-11-14 at 10.40.46.png
Open full size
Screenshot 2023-11-14 at 10.49.56.png Screenshot 2023-11-14 at 10.40.46.png
  • ADMIN RESPONSE
    Dec 5, 2023

    There is a link to the release notes in Change Management; it is the Details button. The description field in the update is input manually and we have updated the process to be consistent and match the updated name. Due to the limitations of the update creation process and other factors, we are limited to XXXX.XX for update numbers. A change was made at the corporate level to change the update to XX.XX.XX in communications, but this cannot be made at the creation and installation level. We also stopped making updates coincide with the year many years ago because this limited the product development teams and contractually. No change in our update numbering will be made at this time.

  • Attach files
  • Paul Hendrix
    Reply
    |     Dec 5, 2023
    There is a link to the release notes in Change Management; it is the Details button.

    This is appreciated, albeit more difficult to access since Change Management is located behind Special Functions which requires a passcode. I think it would be beneficial to also have this in the Thrive's file menu → Help → About section.

    Due to the limitations of the update creation process and other factors, we are limited to XXXX.XX for update numbers. A change was made at the corporate level to change the update to XX.XX.XX in communications, but this cannot be made at the creation and installation level.

    This is understandable and I suspected as much when it comes to the creation process. However, I'm not sure I understand why communicating the update would use the format XX.XX.XX while the update numbers are actually XXXX.XX. That still seems confusing.

    RE: Clarify Versions for Different Systems, I still believe there is opportunity to further clarify Thrive's About section.