nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

External Task transition issue

becool321

My fellow teamsite workflow monks I have an issue transitioning CGI task to an external task.

It appears that transition took place but external task (Regenerate XML) doesn't execute. If I remove the transition task external task runs after clicking next at the task comment screen.

However, my goal is to bypass the external task comment screen. Hence my implementation of the transition task.

My code and screen shots are attached for reference.

Any suggestions on executing external task Regenerate XML simultaneously is greatly appreciated

Find more posts tagged with

Comments

Adam Stoller

Your CGI code does not verify that $taskId is a scalar, numerical value and you have no debugging code present (as far as I can see) to verify what actually happens when the code is run from the workflow. My guess is that you are getting a reference to an array and need to dereference it to get to the actual scalar task id value - which would explain why the transition doesn't occur.

Personally, I wonder why you wrote the code you did instead of using TeamSite::CGI_lite's iwcallback() method? Or, for that matter, why you are even using a CGI Task - since the code you posted seems to do nothing except transition the workflow - and if I am understanding your diagram correctly - this is the code for "Transition Task Attach Dependencies" - which you'd want to have run "immediately" which it will never do if it comes after an external task.

Thus what you are really trying to do is get the actual "Attach Dependencies" CGI Task to run immediately after the "Regenerate XML" External Task - right?

That won't happen.

I don't know what occurs before "Regenerate XML". If it is a User Task or Group Task you could make Regenerate XML a CGI Task and then have it run immediately and transition directly to "Attach Dependencies" which could be set to run immediately (assuming that both Regenerate XML and Attach Dependencies are owned by the same user who owns the preceding user-interactive task) - otherwise you're pretty much out-of-luck using the pre-existing "Attach Dependencies" task and should instead replace it with your own custom External Task version of the task - in which case you don't have to worry about the "immediate" part.

becool321

Thanks for your reply Ghoti. However I only revised the code which was posted as a solution at https://customers.autonomy.com/support/secure/docs/FAQ/Interwoven/56306.html.

Actually I'm trying to get the actual "Regenerate XML" External Task CGI Task to run immediately after the "Attach Dependencies". I agree and will also implement some debugging.

I do have another scenario that uses the same concept in this workflow which works as seen in attachment wf2.jpg pic. I wasn't aware of the TeamSite::CGI_lite's iwcallback() method until now.

Nevertheless the same mechanism works fine for other transition in pic so same concept should be applicable.

becool321

Just did some debugging and I verified taskid is scalar as seen below:

taskId: 23932
task: TeamSite::WFtask=HASH(0x21c4988)
donePage: /iw-cc/base/util/close_or_home.html
url: /iw-cc/transitiontask?taskid=23932&transition=Regenerate%20XML&cgi_transition=true&done_page=%2Fiw-cc%2Fbase%2Futil%2Fclose_or_home.html

So still trying to figure this out.

Adam Stoller

Sorry about my earlier post - I didn't see the arrow-heads and assumed a left-to-right progression (which wasn't the case)

The only reason I can think of, off the top-of-my-head, why an external task would not run immediately after being transitioned to - is if it has the

lock="t"

attribute set and there's something preventing it from getting the locks.

ISCBorisB

Sorry about my earlier post - I didn't see the arrow-heads and assumed a left-to-right progression (which wasn't the case)

The only reason I can think of, off the top-of-my-head, why an external task would not run immediately after being transitioned to - is if it has the
lock="t"
attribute set and there's something preventing it from getting the locks.

ipm shows that Task's "Lock" Property is false. Something is fishy here.

Frankly, I think that the original assumption that "It appears that transition took place..."
is incorrect. Transition to "Regenerate XML" did not happen - for whatever reason.
It is actually easy to test, just log out "Got Called" from the External task before
doing anything else.

becool321

Hi Boris,

Got called away on some urgent task last week to get fixed. Anyway I'm back here again. My external task is using:

//hostname/iw-cc/urlgenerate?dcr=dcr_name&pt=pt_name&output=output_name&override=true

How do I log out "Got Called" from the External task before doing anything else as per your previous post?