Workflow custom configuration through a cgi task

akalies

Hi All,

I need to configure a workflow to different workareas throug an CGI task,
what i have done is, I have created folders for the workareas in the iw-wa workarea and copied the tailored custom_config.xml for that workarea.
finally i have the xml in correct place
"..\iw-wa\Config\myworkflow\....\workareafolder\custom_config.xml"

And then i submit it using iwsubmit.

Now the configuration is not getting reflected because it being shown as "OUTDATED" in the workflow configuration page. I dont know why it is shown as outdated.

Looking for some help ...

Thanks a lot.

Adam Stoller

Hi All, I need to configure a workflow to different workareas throug an CGI task, what i have done is, I have created folders for the workareas in the iw-wa workarea and copied the tailored custom_config.xml for that workarea. finally i have the xml in correct place "..\iw-wa\Config\myworkflow\....\workareafolder\custom_config.xml" And then i submit it using iwsubmit. Now the configuration is not getting reflected because it being shown as "OUTDATED" in the workflow configuration page. I dont know why it is shown as outdated. Looking for some help ... Thanks a lot.

You seem to have two different things going on here.

One: The desire to "configure a workflow to different workareas through a CGI task"[indent]A CGI task is part of an instantiated workflow process - you specify the workarea to which it will be associated when you define it as being a task - generally speaking, it is the same workarea where all the rest of the tasks of the workflow operate - but it can be hard-coded to something else if desired. Alternatively, you could have some other task (external, url, cgi) whose script can be used to alter the path associated with the CGI task before it becomes activated [again?] --- however this begs the question: Why?[/indent]
Two: You're mucking around with configuration files for WFM[indent]This is for controlling aspects of the WFM before it becomes instantiated - whereas the previous part of your post seemed to indicate a desire to control aspects of the job instantiated from your WFM after it became instantiated - Which is it?[/indent]
In either case - I think you have to be much clearer about what you are attempting to do, and why you are attempting to do it -- a "use-case scenario" would probably help explain it.