IDM 8.0: Processes ignore changed content of linked script and keep using old version

[Steffi_Warnecke]

Hello fellow IDM people,

I need your help with something. (Surprise! ^^)

System:

IDM 8.0 SP 6 on MSSQL

What's the problem:

I have a package, that contains all my scripts. I link those scripts into jobs and processes, where I need them. So no funny business there, a new way of having global scripts.

Now I updated one of those scripts in the script package, checked the package in. No issue there.

When I checked the linked script in the process I changed it for, the old content was still displayed. I didn't mind much, because I know this happens, just a display error, right? The script itself (in its own package) shows the correct content.

But there is an issue after all, because the processes keep using the old version of the script, even though it's not there anymore. I know this, because I have warnings activated in the new script, so I know when it's used. And most of the time it is not used (and a very few times it is, haven't found out when yet).

What I tried so far:

• Checking both involved packages out and back in: old version is used.
• Deleting the linked script from the package, check the package in, check it out again, re-link the script: old version is used.
• Deleting the linked script from the package, recreating the script as local package script (with same name) and using that in the process: old version is used.
• Changing the name of the local script and use that in the process: new version is used.
• Changing the name back to the original script name and use that in the process again: old version is used.
• Re-Linking the package script in every process that it's used in in this package and checking the package back in: Package dependencies show the new version everywhere, but old version is used.
• Trying to tear my hair out: old version is used.

To summarize:

I have a linked script that I changed and in every process I have linked it to, the old content is still displayed and most of the time, the old content of the script is used instead of the new version.

I'm at the end of my wits and now I'm here hoping that one of you have encountered the same issue and (more important) have found a way to squash this bug or at least found a workaround?

Help. 😞

Regards,

Steffi.

[former_member2987]

BTW: This is the BEST formatted question I have seen in some time.

[thomas_go1]

Hey Steffi,

just an idea: I would take a look into the table "mc_package_scripts" and the B64-coded "mcScriptDefinition". Maybe there is a kind of bug where the entry of your script (the exactly name) never get touched there - no matter what you do. You could also check the "mcScriptHash" there (is it over all packages identical?); or decode the B64 String and get on this way more information on what happens and what not.

Based on your results, I would try to delete the entry / entries with the script name in the table with a delete statement (on a test environment). After the cleanup you could try it again from the beginning.

BR,

Thomas

[Steffi_Warnecke]

Update time, everyone!

Sooooo it looks like the issue is not as bad as I initially thought it is. Lucky me!

.

Yes, the old version of the script is displayed if I look at it in the package I linked it to.

But the new version is used in the workflow, so at least it works correctly.

.

Found that out after adding some more warnings at the start of the new script. So people, there can never be too much output to the log when you work on stuff!

.

Not seeing the correct version when checking scripts where they are linked is not so great, of course. But I'm not going to dive into the database for this kind of thing. Maybe it will be cleaned up with the next service pack (whenever that is going to be).

.

Thanks for the input, though! 🙂

I'm going to close the question, as it's not quite answered, but the issue is a bug at this point and there is no need to keep it open, I think.

.

Regards,

Steffi.

[former_member2987]

Hi Steffi,

I know this goes against the purpose but if you put the new script directly in the package, does it work?

Matt

[Steffi_Warnecke]

Hello Matt,

I have not yet tried to create it as package script in the package I want to use it in. Just directly in the process.

Will give it a try. 🙂

.

Regards,

Steffi.

[Steffi_Warnecke]

Not working with the "package = self" script either, but I might have gotten a step closer to the issue at least, because it seems to be working for another process.

Thanks, Matt!