Using standard substitution variables in Business Rules; Example: |CVYear|

Hey Chris,

How I would use something like |CVYear| or |WFYear| that is in the data unit in a custom calculate would be to use it in the Data unit section in the Data Managment job. Then in the rule all you need to do is use a api.pov.time.name call for example and you now know what year you are processing. If you want to use a variable that isn't in the data unit then you can pass it through in via parameters section in the Data Mangement job and say somthing like CVUD1=|CVUD1| then in the rule is it just the standard args.CustomCalculateArgs.NameValuePairs("CVUD1") to pull that through into the rule.
I will add I would be careful using say CVUD1 becuase if the CV doesn't have a UD1 defined it in then you run the risk that it will pull it from the Cube POV on the right and that could vary from user to user.

Thanks,

Sam

Hi Sam,

I do not want |CVYear| to be in the Data Unit portion of the Data Management Job.  I will want to compare the Data Unit Time to the variable |CVYear| and calculate depending on the comparison.

I like your idea of passing |CVYear| as a parameter, but it would be nice to access this standard variable directly in the business rule.  That give me something good to try -- I've not passed parameters in before.  Thank you!

Anyone have any thoughts on accessing the value of |CVYear|  directly in a business rule?

Thanks,

Chris