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

Error while using WFTs

gopi123

Hi,
i am trying to submit some files using workflow.But when i select the workflow and click on "submit" i am getting the following error attached in "Screenshot1.doc".Can anybody please help me out to solve this problem.
Thanks in advance.

Find more posts tagged with

Comments

Jcse

Hi,
i am trying to submit some files using workflow.But when i select the workflow and click on "submit" i am getting the following error attached in "Screenshot1.doc".Can anybody please help me out to solve this problem.
Thanks in advance.

Do mention the environment.It helps to give a solution approach.

ISCBorisB

Hi,
i am trying to submit some files using workflow.But when i select the workflow and click on "submit" i am getting the following error attached in "Screenshot1.doc".Can anybody please help me out to solve this problem.
Thanks in advance.

Your WFT code generates malformed Job Specifications. Set WFT Debug mode to "On", get generated XML
and analyze it using any XML Editor or just a Browser. Corresponding Parser will show you XML errors,
their locations etc

Migrateduser

Best way I found to get a reasonable error message when you have a cryptic error on instantiation is to create a job spec in pure XML. You can do this in a WFT by adding this to your TAG_info section:

[HTML]TAG_info(
iw_output_file => "",
);[/HTML]

Then run your job spec through iwjobc and you should get a much more useful error message. That's a good place to start. For whatever reason, you get much better error messages from iwjobc than in the GUI.

Using Debug mode and then trying to look at the XML to find an error when you have no clue what it might be is really tedious and would be a last resort for me.