The good news and the bad news are the same: we are upgrading from Version 8 to Version 11.
One of the major challenges that we see are the number of functions whose operation changed between the versions (most notably from V8 to V9) and how to approach identifying and making the needed object modifications across all of our clients. After review of theRelease Notes Version 11.2and predecessors and focusing on modifications we have a list of about 20 functions that may need to be addressed. As an example, here are three changes that will most likely affect us:1. The Values of Script Variables That Are Set with :PSET Are Now Only Passed on to the Next Workflows One Level Above
2. :RSET statements automatically create object values
3. Static Variable objects now include 5 value columns. For the script element :PUT_VAR, this means that values that include one or several commas and should be written in one column must always be enclosed in single-quote or double-quote characters.
Automic has provided SQL to perform queries for some of the changes to help with impact analysis but unfortunately they have not offered an all-inclusive set. We can obviously use the UI’s Search dialog to locate base usage of Script statements and functions in the Process tabs. Also we will most likely use Philipp Elmer’sSQL: grep in Process tabsand maybe a few others from his excellent site.
However there is little offered by Automic to assist in actual analysis of how something is used and then actually making the required object modification. This appears to leave us in the position of using brute force to accomplish the needed changes. All that they appear to offer for the actual remediation is referencing phrases like “. . you will have to adjust the affected objects manually . .” and “. . recommends renaming all existing script and object variables with this name . .” I am not faulting them as I cannot even conceive of a means to do this programmatically.
We have a bit less than 150,000 objects in our single production client. We have seven other non-production clients that contain copies of some or most all of the production objects plus ones that are unique to those clients. Obviously performing this kind of analysis and remediation manually across our entire inventory is rather daunting.
I would really appreciate hearing about how others have addressed this issue when upgrading versions or any ideas or approaches that you can offer.
Thank you very much, Mark