Custom Event Scripts doesn't work after the Content Server Upgrade from 16.2.7v to 20.4v

Sidhi_RJ · 2021-03-19T18:07:16+00:00

There was an error rendering this rich post.

Hello All,

We are facing an issue where we had existing custom event scripts created for our Workflow milestone steps which it help us to validate or generate a popup error messages if we pick have a wrong workflow attribute while clicking on send on or Approval.

While upgrading them from CS 16.2.7 to 20.4v we got an error stating that " failed trying to open D:/OTHOME/module/Custom_Script/Custom_Script.oll". So we tried deploying them from Eclipse and it was ok & we re-built it.

Testing -

Initiating new workflows we tried to execute the steps which it had event scripts helps us to display error message or validate against the attributes after send on or approval in the workflow but it didn't work as expected. It Just passed the steps without triggering the Event Scripts.

Also, note that we have not changed any scripting before or after the CS upgrades.

Kernel Dependencies on the INI module files follows as given below

[dependencies]

requires_1={'kernel',16,2}

Appreciate all of your inputs !!!

Thanks in Advance,

Sidhi RJ

Find more posts tagged with

Comments

Appu Nair

What I would do is install the eclipse and CSIDE plugin on your version. Bring the module from the old system change anything like Kernel so you can at least install it.Now after creating a Oscript project and making sure all the loaded modules show up in module explorer look and see if your customer module is showing in the list of the active modules. When CSIDE cannot make sense of a compiled module it cannot load it. So I fore see many problems. If you rebuilt it does it show a new timestamp in the OLL and does the old module show up in module explorer then you can debug by putting a break in your script.

BTW does your old event scripts show up in the WF maps for you to attach it that would mean it is registered?

Here's how I would have tried to work with the current problem.

I would basically without even trying to look at your old version code set up CSIDE on your new version
I would create and deploy a dummy module in the current version.
A couple of re-starts to make sure dummy is good and working as if you can build etc.
If that holds orphan the Workflow event scripts like before starting from scratch and create a child eventscript and call its something that you know maybe "WILL CALL"
Create a Logger line in that script pretty verbose so you know that by saying "WILL CALL GOT CALLED at" put some DateTime variable form oscript in that echo statement.
Make sure you create a two-step workflow and put the event script not at the start step but something that is on entry to the first assignee step after the start.
Run in builder and see if your logline happens
Run in services and look at which thread printed it.
This would prove that OT Development is allowing Event scripts Dev like before. otherwise, complain to OT asking if they changed any development parameter viz a viz EventScripts...

If all that panned out see if you can port your old version code into this dummy module :) keeping CSIDE on 16.2.7 on one screen and 20.4 on another screen laboriously cutting and pasting code. Not fun...Unfortunately.

I don't have a 20 built otherwise I could have checked similar aspects but I do not think OT would change something as basic and useful as an event script. In fact, OT's RM program bundles a bunch of Event Scripts so if you have CSIDE on 20 or 21 you could see the paths and registration stuff of RM

#AOTDEV0D

Sidhi_RJ

Thanks Appu for your response.

Old Scripts are registered and we are able to select them from the workflow Screens.

And moreover what you have suggested it worked to trigger the event, But it didn't display the error messages. Do you have any thoughts on that ?

Regards,

Sidhi RJ

Appu Nair

And moreover what you have suggested it worked to trigger the event

What do you mean by what I suggested? as in put a log line? or something else? If your scripts are registered if you run CSIDE and put a break it will break...

If you are in CSIDE can you put a screencap showing on the module explorer your custom module appearing in RED?

John Simon

I had to write a patch for a customer because event script failures were not being handled properly by OT code. You might check with support to see if a bug has been logged (fixed). Sorry I do not recall the details (like what version the customer was on) just the high level problem.

Cheers...

Nizar Ghazal

Sidhi, concerning: "But it didn't display the error messages. Do you have any thoughts on that ?"

Please go to the admin pages for the instance you're testing against, and go to log settings. Set thread logs to debug. If you don't see Echo() statements in the console of CSIDE, it's usually going to be because of this suppressing logged messages. I think EchoError() might not echo in the console window, so you could probably just read it in thread0.out. (Make sure to reduce log size so you don't eat up all the HDD space of your test box)

Otherwise, I'd suggest just doing what Appu said, use break-points so you can read the data, in-flight.

Alexandr Arzamastsev

We've managed with creating a patch for this [dis]functionality.

Sidhi_RJ

Hello All,

We found out this module was built with the older version 10v & below given steps made us to resolve the issue.

Installed CSIDE on the existing CS Version & imported the Custom Module with Event Scripts.
Exported the module on CSIDE from the existing version.
Installed the Exported module to the latest version of Content Server 20.4v from Admin Pages.
On the Previous version there were few variables which were not declared and after declaring them in the new version.
Reboot the Content Services & we got the issue resolved.

Thanks All for your response.

Thank Appu for your comments which helped us a breakthrough..

Regards,

Sidhi RJ