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; } } }

WFConstructor

kaalraa

Hi everyone,

I need to create a job specification file dynamically using some inputs from an XML file. I have already read all values of XML thru .ipl file and now i want the info ablut WFconstructor as how to use the module to create the file.

I hope you all understand my query....Thanks, if anyone can give me a hint.

- Achin Kalra

Find more posts tagged with

Comments

Johnny

Read the perl documentation, it's pretty much all there.

IWHOME/iw-perl/bin/perldoc TeamSite::WFconstructor

I believe the solution workflows use this module as well, so you can use them for reference.

After you've done - if you have any specific questions, post them here.

John Cuiuli

Nicholas

Any update on this?

Did you tried the John's suggestions

Thanks Nicholas

kaalraa

Hi,

I have gone through the Perl doc for WFconstructor, but the mail query is when the constructor runs and creates a Job Spec file what would be the physical location of the file and how to invoke that spec file.

As i have already defined a place holder in available_templates.cfg in that name.... but what would be the path. Also what would be the best CLT command to invoke job spec file... Is it iwjobc or any other ??

Thanks for your replies,
- Achin Kalra

- AKS.... the shadow

DisplayAveragesUnderCrosstabOfTotals.rptdesign

Adam Stoller

A lot of it depends on *how* dynamic this workflow is really going to be.
If the dynamics are based on what would otherwise be job instantiation variables - you might consider the use of iwwft_compile.ipl (run perldoc on IWHOME/bin/iwwft_compile.ipl for more information).
If the dynamics affect the entire construction of the wft - then you can either use iwwft_compile.ipl or create a job description file and use iwjobc -i

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Johnny

As per the documentation - the final method to retrieve the job spec just outputs the contents as a string. If you are outside a .wft for your own reasons and need to write this to a file, take the string and write it to a file.

As Adam mentioned - The CLT iwjobc can be used to enter the job into the system.

John Cuiuli

kaalraa

Thanks, John and Fish (Don't know your name), for your replies. It really helps me a lot. but for now .. i used to get a error again and again... and that is "Invalid Workflow at lIne #.. Operation failed".

Could not get out of the error. I have written some perl doc to parse a XML file which gives me inputs for the sequence of workflow to be followed with in <template_script> tag. And after that the workflow and tasks are being declared.

Please provide an option... if you have got the same error or so.

- Achin Kalra

- AKS.... the shadow

Adam Stoller

First - do you know how to write [relatively simple] workflow templates?
Second - do you know how to write job description files?

If you aren't comfortable with either of the above, you need to either do more reading or take some training.

Once you're comfortable with the above - you need to make sure you understand how to debug workflows - again, more reading and/or training

Once you're comfortable with that - you should be able to address your current problem - if not - you need to be much more informative about the code and the problem caused by the code. But if you don't take care of the above 3 pre-requisites, you're doing little more than asking for someone else to write your code for you, and that's generally not appreciated.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

awizardly

Just to give you a bit of a hint look in your available_templates.cfg for references to .wft files and search for those in your iw-home for matchin refernces. You should see the correlation quite readily, but this should also be very evident from reading the WF documentation and following the WF tutorial provided in the WF Development PDF.

Also for specifics on the WFConstructure Perl Module look at the Perl Docs available as part of the library on the support site. The perl doc is pretty basic but atleast gives you valid options for everything. A better reference for actual usage is in the solutions workflows that InterWoven provides like configurable_author_submit.wft.

All of this won't help you unless you are familiar with the basics of workflow though. I think that most people on these forums are willing to help, but not do everything for you.