Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-178

Global properties portlet needs to be able to exclude multiple module framework properties

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Should
    • Resolution: Fixed
    • None
    • OpenMRS 1.7.0
    • None
    • None
    • Low

    Description

      The global properties portlet allows lets you display ajax-editable text fields with specified global property values. It is configured with 'propertyPrefix' and 'excludePrefix', so a common usage might be for a module's configuration page, like in this example from formimportexport:

      <openmrs:portlet url="globalProperties" parameters="title=$\{title\}|propertyPrefix=formimportexport.|
      excludePrefix=formimportexport.started|hidePrefix=true|readOnly=false"/>
      

      Originally each module had one automatically-added global property called "${moduleid}.started", and the 'excludePrefix' parameter was sufficient to hide that. Now, however, there's both "${moduleId}.started" and "${moduleId}.mandatory", so since 1.5 or 1.6, the given example from formimportexport no longer hides all of the automatic properties that shouldn't be visible to the user.

      This could be tackled in different ways:

      1. Allow excludePrefix to be a ;-separated string, like excludePrefix="fie.started;fie.mandatory"/>
      2. Add a 'forModule' property which automatically does propertyPrefix = "${forModule}.", hidePrefix = "true", and hides ${forModule}.started and ${forModule}.mandatory

      The second option is probably better, but the first could be done at the same time.

      Gliffy Diagrams

        Attachments

          Activity

            People

              raff Rafal Korytkowski
              darius Darius Jazayeri
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: