Accessing "Description" in a scheduled PROTOCOL:up

This topic has 5 replies, 2 voices, and was last updated 19 years, 7 months ago by Charlie Bursell.

Creator

Topic
May 11, 2005 at 2:23 pm #47735
Mark Thompson
Participant
In version 5.3, the PROTOCOL:upoc actually works nicely as a timer to trigger events within the engine. The designers of the Advanced Scheduling option very wisely included a “Description” column to document what this particular timer call is supposed to be doing. My question: Is there any way for Tcl to access the description when the upoc timer triggers the event?

- Mark Thompson
HealthPartners
Creator

Topic

Viewing 4 reply threads

Author

Replies
- May 11, 2005 at 3:38 pm #56567
  Charlie Bursell
  Participant
  Not without reading the NetConfig from your Tcl proc. The name is for reference only.
- May 12, 2005 at 12:24 pm #56568
  Mark Thompson
  Participant
  Charlie,
  
  Great suggestion. I don’t have a problem reading NetConfig — there are several nice tools for that. How can I tell which event# triggered the call?
  
  - Mark Thompson
  HealthPartners
- May 12, 2005 at 1:15 pm #56569
  Charlie Bursell
  Participant
  You would pass %A to the Tcl proc which is the text if the alert.
  
  I don’t see why you would go to the bother of reading the description from NetConfig. In the Alerts configuation under action, when you call the proc, simply pass it in.
  
  myproc “%A” “My Description”
  
  Don’t forget to put the $A in quotes since it has embedded spaces.
  
  Charlie
- May 12, 2005 at 1:20 pm #56570
  Mark Thompson
  Participant
  I’ve done quite a bit with alerts and the %A is very helpful. Can it also be used with the scheduled events in a PROTOCOL:upoc thread discussed in this topic?
  
  - Mark Thompson
  HealthPartners
- May 12, 2005 at 4:10 pm #56571
  Charlie Bursell
  Participant
  No, it is used in the Alerts only. Its generated by the Alert engine.
Author

Replies

Viewing 4 reply threads

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