Russell,
I want to confirm that you are running the Process Flow and not just the Job? That sounds like
the behavior if you were just running the Job as the subvar #number (ie: #1) is undefined outside
of a Process Flow.
Ed.
Ed Knowles Email:
eknowle@siue.edu<mailto>
Assistant Director, IT Phone: 618-650-3813
Production Control & Enterprise Reporting
ITS - Southern Illinois University Edwardsville
From: Russell Brown [mailto:automicsoftware+
d11381-s5019921@email.vanillaforums.com]
Sent: Friday, January 5, 2018 12:25 PM
To: Knowles, Edward <eknowle>
Subject: Re: [Automic Community] Using a input parameter value in a substitution variable
[Automic Community]<https></https>
________________________________
Russell Brown commented on Using a input parameter value in a substitution variable
Edward,
Thanks for the response! I'd been playing around with using the always true --> set subvar condition. But I just can't seem to use the value from prompt #1 into the condition. Example, I'm using the following syntax for the set subvar command: #affiliated_term={#1}
When I run the job, I enter 201810 for prompt 1, but the value of #affiliated_term just keeps being set to literal #1. I think/hope it's just a syntax problem - I'm not able to properly get the handle for prompt 1 and use it in the #affiliated_term subvar. Eventually, once I'm able to get that value, I'll use decode almost the same as you have in your example.
Thanks again for your response,
Russell</eknowle></mailto>