Reindex (Pre-Archive) Script Hook Not saving Keywords?

[Christopher_Per]

Good Morning - 

Recently I have upgraded my Test System from 13.2 to 15.2. One of the things I tested deal with a special VB Script I have running in the background. Basically, if a Keyword is of a certain value, I pop up a message stating that other keywords need to be filled and prevent the user from continuing. What I noticed though is that under the Reindex(Pre Archive) script hook, Onbase automatically reverts to the original keyword values. So if I reindex the document, make some changes to the keywords and forget something, the script will kick in and revert back to the original values of the document instead of keeping the current values. 

Keep in mind that this script works completely fine in 13.2, and when i try to reindex something and I get the message that i need something, the new values are retained. 

So my question is this: has anything changed in this area from 13 to 15? If so, is there a way around it? Anything you can provide would be greatly appreciated. Thank you. 

[Patrick_Sweeney · Accepted solution]

Hello again Chris,

That is indeed the code that should be used to cancel the Reindex process.

After talking to a few other employees it appears that the behavior you're seeing was introduced in SCR #155400, an SCR that was made to resolve a separate bugfix.  A byproduct of that fix appears to be that the Reindex panel is being reset when the process is canceled.  Currently we're investigating this issue and we'll most likely be creating an SCR to address it.  I'll try to update this post to update you if an SCR is created to address this issue or if other action is taken.

Thanks Chris, sorry I don't have a good workaround for you

Update: Okay Chris, SCR #247613 has been created to address this issue.  If you'd like to follow this SCR you can contact technical support to get yourself attached to the SCR.

[Christopher_Per]

Hi Patrick -

Thank you for the response. I do have one question regarding these SCRs:

Currently, our Production System is in version 13.0.2.673 SP2. Our Test System is in 15.0.2.174 SP2. If possible, we would like to have this issue addressed. However, my question is how are we going to receive this update. Is this something like a patch that we install? Is it a new client that needs to be rolled out? Or is it a total upgrade?

[Patrick_Sweeney]

I think your best bet will be to work with your first line of support on that Chris. When the issue is addressed it will most likely be rolled out in a new client or in a service pack update. Support will be able to keep you updated on the status of the SCR and better explain your options for getting the change.