Ens.Rule.FunctionSet without parameter?

Question

Question

Scott Beeson · Feb 11, 2016

#Change Management #Perforce #Code Snippet #Ensemble

I'm writing some custom functions for use in a routing rule. I have a few that are working, but right now I'm trying to use one that has no parameters. Typically this would be a sub instead of a function, but I'm not familiar enough with Cache to know what I need to do here.

Here is the code:

Class Custom.MHC.Common.CustomFunctions Extends Ens.Rule.FunctionSet
{

/// Location and Revision of this file in Perforce (Auto-updating)
Parameter SrcVer = "$Id$";

/// Returns the current environment code,
/// DEVELOPMENT, TEST, LIVE
ClassMethod getEnvironment() As %String [ Final ]
{
q ^%SYS("SystemMode")
}
}

And here is what happens in the Rule Editor UI:

What should I do?

Discussion (6)1

Log in or sign up to continue

David Loveluck · Feb 11, 2016

looking at the 2016.2 field test, the red exclamation mark has gone. It normally means the argument is required, so it shouldn't be there, but is doing no harm other than misleading people.

0 0

score 0 · Answer 1 · 2016-02-11T13:09:02-05:00

Scott Beeson · Feb 11, 2016

It seems to function fine, but the ( ! ) bothers me.

0 0

score 0 · Answer 2 · 2016-02-11T13:09:06-05:00

the UI here is not very clear - it suggests that you need an argument, but leaving the box empty should work just fine. No argument will be passed and everything will work fine.

score 0 · Answer 3 · 2016-02-11T13:15:01-05:00

Thank you David. Would it be preferred, or is it even possible, to reference ^%SYS("SystemMode") directly somehow?

score 0 · Answer 4 · 2016-02-11T13:16:22-05:00

Scott Beeson · Feb 11, 2016

And I suppose I could just pass a zero to avoid the warning indicator.

0 0

score 0 · Answer 5 · 2016-02-11T13:22:39-05:00

Scott Beeson · Feb 11, 2016

Good to know it's fixed in a newer version. I'll do my best to ignore it! :)

0 0