Script Logic v7 & v10 - ReCompile

[Former Member]

Hi,

We have a combination of Constants, Scripts & Drivers in each of our applications/models and each year we "flip" the year for the upcoming budget season.  Part of this includes updating the Constants which contain hardcoded values for the different "time-related" dimensions, along with some other standard logic that the scripts will use.

Whenever we perform this task, we then go into the Constants, Scripts & Drivers (specifically in a dependency order) to validate and save the changes, and re-compile the code in the system.  Is anyone familiar with this process, and do you have alternative methods to make this a less time consuming task?

Thanks, please advise if any other questions / clarification is necessary.

Regards,

Brian

[Former Member]

Hi Brian,

Can you please share the purpose of this activity. We can try and come up with a dynamic solution.

[Former Member]

Thanks Nilanjan,

A basic example of why we do this is we have constants that store our high level Time dimension parameters, so we can pass those "variables" to our scripts.  When we update the constants, the scripts do not reflect the update to the constants until we open them up and re validate and save them.  This is similar to how we change a conversion file and then need to revalidate and save the Transformation files to reflect the new excluded members added to our conversion file.

Altough the task is considered more of an Annual maintenance, it would have been nice if there was an easier way to do this other then opening up each script, etc... and resaving/validating.

I would categorize a solution for this as being a "nice-to-have" and not a high urgency...  😉

Thanks,

Brian

[Former Member]

Hi Brian,

I had understood that you are maintaining some constants in UJFS, and is used in script, from your first post. What I wanted to know was what kind of constants are created and how are these used.

If the constants are maintained like this, then there is no option than validating the logics. What I wanted to see was if we could avoid using these constants.

[Former Member]

Ahhh.... thanks for your help.  That will be a battle we will look to fight through once we get through the current Upgrade and Budget Season upon us! LOL

Have a great day, and thanks again.

Brian

[JohnL]

Hi Brian,

There is package called AdminTask_LogicValidate.dtsx located in the \%Environment%\%Model%\DataManager\PackageFiles\Examples folder.

If you look at the MODIFYSCRIPT variable, it is hard-coded to validate the Default.LGF:

TASK(AdminTask_LogicValidate,DESCRIPTION,AdminTask_LogicValidate)

TASK(AdminTask_LogicValidate,Environment,%Environment%)

TASK(AdminTask_LogicValidate,Model,%Model%)

TASK(AdminTask_LogicValidate,USERID,%USER%)

TASK(AdminTask_LogicValidate,PROCESSMODE,0)

TASK(AdminTask_LogicValidate,LOGICFILE,Default.LGF)

You can try copying and then modifying this package to see if it suits your needs.

HTH,

John