InterSystems Ideas

Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.

The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.

💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.

🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.

Start by sharing what could be better - the community and our teams will help take it from there.

Add a new idea Subscribe
Status Future consideration
Categories InterSystems IRIS
Created by Alex Woodhead
Created on Jun 6, 2023

RELATED IDEAS

Envrionment variable support in System Default Settings

Docker commonly passes settings via environment variables.

It could be useful if when resolving settings for production configuration this could also evaluate environment variables instead of deployed static values.

Thus the container drives the behavior of the production.

When productions are packaged and deployed the environment variable names are transprted with the export as with static values for production settings.

Ref: https://docs.intersystems.com/irisforhealth20232/csp/docbook/DocBook.UI.Page.cls?KEY=EGDV_deploying

A suggestion from community is for System Default Settings to:

1) First try using the named environment variable if defined

2) Otherwise fallback to a given "Settings Value"

In first case, the REPORT on what settings are in effect should be expanded to indicate is from Operating System Environment Variable. See attached.


EnvSettingsForP...
EnvSDS.png
EnvSettingsForProductions.png
Open full size
EnvSDS.png
Open full size
EnvSettingsForProductions.png EnvSDS.png
  • ADMIN RESPONSE
    Nov 20, 2024

    Thank you for submitting the idea. The status has been changed to "Future consideration".

    Stay tuned!

  • Post comment
  • Steve Pisani
    Nov 21, 2024

    If the current field 'Settings Value' interpretted and evaluate embedded expression: for example:

    {$System.Util.GetEnviron("iris_production_shutdown_timeout")}

    The original poster's requirement would be met, and, if users want to evaluate the setting based on an expression in order to support multiple instances from one code base - for example, I want all HL7 interfaces' archive path folder to be go to a common folder with subfolders by server and instance, I coudl potentially specify - for archive path:

    //commonUNCPath/hl7Archived/{$TR($System,":","/"}/{$$ItemName}

    $TR($System,":","/") would resolve to hostname/irisinstancename and $$ItemName will resolve to the production components item name resulting in this effecctive setting, calculated during the Initialisation phase of the component Hl7SourceA, running in instance IRIS, on hostname myPCName.

    //commonUNCPath/hl7Archived/myPCName/IRIS/HL7SourceA

    Other special variables like $$ItemName, can be $$ProductionName, $$HostClassName. User defined class methods can also be able to be used, within the expression {}.

    Reply
  • Admin
    Vadim Aniskin
    Nov 15, 2023

    @Alex Woodhead, you have a comment on your idea. Please answer it to help your idea to be promoted.

    2 replies
  • Steve Pisani
    Jul 28, 2023
    I always felt that it would be good if one could define apart from a value for a setting, an EXPRESSION to call in order to resolve the value. An expression can invoke a method which can look for an environment variable, and also resolve more complex setting values, for example, where your setting needs the production namespace (eg for centralised archiving : archive path = /archives/($ZN)/.. which will work in all deployments, or other run-time specific values.
    Reply