![]() Run in builder and see if your logline happens.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.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.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".A couple of re-starts to make sure dummy is good and working as if you can build etc.I would create and deploy a dummy module in the current version.I would basically without even trying to look at your old version code set up CSIDE on your new version.Here's how I would have tried to work with the current problem. 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.īTW does your old event scripts show up in the WF maps for you to attach it that would mean it is registered? When CSIDE cannot make sense of a compiled module it cannot load it. 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. What I would do is install the eclipse and CSIDE plugin on your version. Kernel Dependencies on the INI module files follows as given below It Just passed the steps without triggering the Event Scripts.Īlso, note that we have not changed any scripting before or after the CS upgrades. ![]() 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. So we tried deploying them from Eclipse and it was ok & we re-built it. 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". 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |