Problem with ST-USG-009 rule

Hello friends!

I’ve been using the Workflow analyzer lately, and I’ve notice a problem with ST-USG-009 rule.

Mainly that this rule is violated when I use variables to map arguments from one Workflow to another.
Should I switch the way that I map values from one workflow to another, or should this rule be changed in some way?

Isn’t the rule saying not that you have a mapping issue, but that you are mapping to a variable that is consequently not used in your workflow?

Yes exactly, the variable job is to map from one workflow value to another, so It is used in someway

Yes, but once it is mapped, is the variable used in any subsequent activity? if not, it will be classed as ‘unused’. For why would you map to something for no follow on purpose?

how else am I going to switch arguments from one Workflow to another?

In one workflow I am getting PDF number pages and in other I am using that information to separate PDF file

I also feel bothered with this in my Error List.
Sometimes I pass the Config dictionary variable to different Workflows without using it to the Main WF,
thus this error remains.

1 Like

Since I have slight OCD regarding warnings I’ve disabled this rule :smiley:

1 Like

Well, it does triggers me to perform “Remove Unused Variables” in the ribbon so it is still helpful for me.
Fortunately, when I use this button, it does not remove the said variables passed around as WF arguments.

Since the “Remove Unused Variables” properly detects them as used variables,
I am hoping that the same will be done for this rule. :pleading_face:

1 Like

Maybe they need to fix it, I am always scared to use “Remove Unused Variables”

Thank you for your suggestion. I added it to our internal ideas tracker for our team to consider.



In addition, this rule is also violated
if I just used the variables in the MultipleAssign activity.
Using them individually using the Assign activity does not generate error.



This rule works incorrectly also when inputting variable into input collection of activity. For example variable “hostname”

which is assigned as default value.

in this xaml it is put into “Add log fields” activity
this rule doesn’t seem to “see” this usage

A little late to the party but tried to replicate the behaviour in latest release (20.10) and no bogus errors are shown for ST-USG-009.

Can you try again? It should be fixed now.

Oh damn this was long time ago :smiley: sure ill check up

1 Like