Workflow Modeler problems

yanSi

Attached is a sample modeler file called Test.ipm. It starts off with a review task. After a minute, if the Review task is not performed, a reminder email should be sent out. To simplify things, I did not use an EmailTask; instead, I used a dummy task which transfers back to the Review task right away once the imaginary email is sent. Once the Review is completed, it either goes through the approved branch or the rejected branch and then my test workflow ends.

This test workflow illustrates some bugs that I may have found with workflow modeler:

1. If you look at the Task Details page for the Review task, there are 3 buttons that correspond to the 3 possible branches out of the task.
a)Approve
b)Reject
c)Timeout
Timeout should not have a corresponding button since it is an automatic transition and a user should not be allowed to push this.

2. The timeout transitions don't happen

3. You are not allowed to pick 0 hours and 0 minutes (+000000) if you try to set it as a configurable variable in the modeler, but it should be a valid value.

Do you all think these are bugs or did I miss some property settings?


I'm also trying to convert some old wft files which had Perl code that dynamically generates a TAG_info section. For example, if a user attaches more than 25 files, the instantiation form displays ONLY an error message. If the input to the workflow is normal, then the normal instantiation form is displayed with text fields and drop downs... I don't suppose it's possible to dynamically generate a workflow instantiation form with Modeler is it?

Bill Klish

I am seeing the exact same issue right now, where the timeout link is appearing as a timeout and a successorset, along with the timeout value not being transferred correctly. It is set as 24 hours in the modeler, but the output of iwgetwfobj returns:

[html]






















[/html]

There is no mention of this in the release notes for the latest patch 3. I will test this on the latest patch 3 and let you know if it is fixed, but in the general non patched release of 6.7.1, this fails.