Error Message with little value

[Anonymous]

I had edited a workflow. The result was a message that there was an issue with a custom script.

So, I checked all of the workflow transitions and no custom scripts were assigned. That didn't clear up the issue, I removed and recreated the transitions, hoping that this would clear it up. No... that didn't fix it either.

So, I drug the first transition from the start position to the second box in the workflow, then back again to the first box.

It was after doing so that I got this error...

The page at... [URL here] says:

The requested action caused an error. Please contact Support.

Nice... "no comment" on the value of this message...

Anyone else have experience with it?

[JohnCHill]

Hello,

Can you provide screen shots of the workflow and the properties of the transition you are seeing an issue with?  We can see an error with the createMileStones script, line 42 in your tenant logs.   Is there an item open as if you change the script it will still try to run if it is loaded in the Workflow tab?

[Anonymous · Accepted solution]

Unfortunately I deleted the workspaces exhibiting this issue. I wasn't liking the way they were set up anyway.

Looking over in the scripts I saw, at the bottom, I could view a log file - ah, clues!! The file states:

[createMileStones (line 42, col 0)] org.mozilla.javascript.WrappedException: Wrapped java.lang.RuntimeException: [02] In-Progress is not the short name of a workflow step in the relevant workspace (createMileStones#42)

I had cloned the NPIMileStones script and attempted using it at one time. The variables in the script were out of date and didn't reflect the workflow states - by name (short name - whatever that is).

Line 42 in the createMileStones script is setting milestone properties: 

                            mStones[stateKey].setWorkflowState(stateKey);

As I look further, 'statekey' appears to be the name of the workflow state for which properties are being created. Thus, my "out-of-date" script has errant workflow state names.

Lesson: Before ever creating/assigning scripts, get the workflow hammered out so I don't later make changes that send scripts into spasms.