Uploaded image for project: 'EMR API'
  1. EMR API
  2. EA-145

Clean up inconsistents in conditions privileges naming conventions

    XMLWordPrintable

Details

    • Enhancement
    • Status: Closed
    • TBD
    • Resolution: Won't Fix
    • None
    • None
    • Undetermined

    Description

      In EMR-API, where privileges were first introduced, the privileges to view and edit privileges were names as follows:

      "Get conditions"

      "Edit conditions"

      when they were migrated to core, they were changed to:

      "Get Conditions"

      "Edit Conditions"

      The latter is the correct standard, however when upgrading to Core 2.2 the privilege names aren't updated (assumedly because the test to see if the privilege already exists is case-insensitive).

      This has been problematic, because it looks like some of the privilege checks are case sensitive.

      The core checks should be make insensitive, which has been ticketed in TRUNK-5444, but it would also be nice to clean up the underlying inconsistency.

      One way to do this would be change the privileges names in EMR-API, and add a changeset to update the privileges in the database... this would be potentially a little tricky as privilege names are used as primary keys.

       

      Gliffy Diagrams

        Attachments

          Activity

            People

              Unassigned Unassigned
              mogoodrich Mark Goodrich
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: