Hidden variables within a translate

This topic has 4 replies, 5 voices, and was last updated 7 years, 3 months ago by Robert Milfajt.

Creator

Topic
May 18, 2017 at 2:16 pm #55395

Tim Zwieg
Participant

I am trying to eliminate some “TEST ONLY” code in a translate so that it does not need to be re-edited prior to moving to production.
Creator

Topic

Viewing 3 reply threads

Author

Replies
- May 18, 2017 at 5:12 pm #85167
  
  David Barr
  Participant
  
  You could probably write a TCL XLTP to copy $::HciSite or [info hostname] to an Xlate variable.
- May 18, 2017 at 6:07 pm #85168
  
  Mark Thompson
  Participant
  
  Hi Tim,
  
  Cloverleaf 6.2 introduces “global variables” – not to be confused with any other global variables – that would work very well for this. Probably still need an xltp proc to read the global variable and use it to set your xlate variable.
  
  - Mark Thompson
  HealthPartners
- June 6, 2017 at 4:46 pm #85169
  
  Rob Abbott
  Keymaster
  
  ~~Mark Thompson wrote:~~
  
  Hi Tim,
  
  Cloverleaf 6.2 introduces “global variables” – not to be confused with any other global variables – that would work very well for this.
  
  Rob Abbott
  Cloverleaf Emeritus
- June 6, 2017 at 10:45 pm #85170
  
  Robert Milfajt
  Participant
  
  Rob, would we only be able to do the COPY you specify with 6.2? Just curious how to specify a global variable to an Xlate? That is pretty cool stuff! 🙂
  
  Robert Milfajt
  Northwestern Medicine
  Chicago, IL
Author

Replies

Viewing 3 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.