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

Workflow -- not well-formed at line 13

ggan

Hi,

I coded a workflow, everything looks fine. But when i run it from job create form, it keeps telling me--not well-formed at line 13, but either line13 is white line or just cgi_info element which nothing wrong with that.
Could anyone take a look to see what is wrong in the file?
Here is the specification of workflow: after author finish author's task, send to primary reviewer, then pass to 3 concurrent review chain if primary reviewer approved. once all of 3 reviewers approved then go to submit and end this workflow.

Thanks for any replies,

Gary

TS 6.5 SP2, Win 2003 server

Find more posts tagged with

Comments

nipper

Put it in debug mode and then post the output XML, that will be easier to debug

ISCBorisB

Hi,

I coded a workflow, everything looks fine. But when i run it from job create form, it keeps telling me--not well-formed at line 13, but either line13 is white line or just cgi_info element which nothing wrong with that.
Could anyone take a look to see what is wrong in the file?
Here is the specification of workflow: after author finish author's task, send to primary reviewer, then pass to 3 concurrent review chain if primary reviewer approved. once all of 3 reviewers approved then go to submit and end this workflow.

Thanks for any replies,

Gary

TS 6.5 SP2, Win 2003 server

You are new to the Forum, so here is free advise: learn how to do due diligence debugging yourself.
Otherwise, with the questions like that you may incur serious amount of (well deserved) ridicule - in public.

You have a stray quote here (which took me perhaps 5 seconds to find):
<successorset description="Reject: send back to author"">

ggan

Put it in debug mode and then post the output XML, that will be easier to debug

Please check the attached file.

Thank you for your time.

Gary

ggan

You are new to the Forum, so here is free advise: learn how to do due diligence debugging yourself.
Otherwise, with the questions like that you may incur serious amount of (well deserved) ridicule - in public.

You have a stray quote here (which took me perhaps 5 seconds to find):
<successorset description="Reject: send back to author"">

Thanks ISCBorisB for your good advice, i think a lot of people learn from their mistakes even stupid then they can improve themselves.

The small mistake you mentioned didn't fix the problem, still same error came out.

Thanks again for your prompt reply.

Gary

nipper

The error Bo talk;ed about is int eh XML you posted:

<successorset description="Reject: send back to author""/>

ggan

Hi nipper,

The mistake which SCBorisB mentioned was fixed in the code. But I still get same error.

Thank your for your time,
Gary

ISCBorisB

Thanks ISCBorisB for your good advice, i think a lot of people learn from their mistakes even stupid then they can improve themselves.
The small mistake you mentioned didn't fix the problem, still same error came out.
Thanks again for your prompt reply.

Gary

It would have been so much nicer if you followed an advise as well, but one can not ask for everything, I guess. I'll try one more time.

What's Perl-style comments are doing in the middle of XML? Do you think it's well-formed?

<?xml version="1.0" standalone="no" ?>
<!DOCTYPE workflow SYSTEM "iwwf.dtd">
#=====================================================================
#  XML JOB SPECIFICATION SKELETON
#=====================================================================
#  This XML section is used to generate the job specification files based on
#  input provided by the end-user in the job creation form.
<workflow   name = "AAA"
            owner = "iw_user"
            creator = "iw_user"
            description = "zxcz">

CrosstabAlternatingRowHighlightUnevenSequence.rptdesign

nipper

man I skipped right by that.....

ggan

It would have been so much nicer if you followed an advise as well, but one can not ask for everything, I guess. I'll try one more time.

What's Perl-style comments are doing in the middle of XML? Do you think it's well-formed?

Hi ISCBorisB,

I changed all comment by #, but -- still same error with different line number which is white line.

Thank you for your help

Gary

ISCBorisB

Hi ISCBorisB,

I changed all comment by #, but -- still same error with different line number which is white line.

Thank you for your help

Gary

Gary, your "wft" code generates malformed XML. It is that simple. if you do not know what that means get for example here and start reading.
If you do, find where is the violation of *well-formedness* in your generated XML (it is actually called "Workflow Specifications") and modify your wft code to rectify the issue.

Adam Stoller

Here's what I see - some of which has already been pointed out:

<?xml version="1.0" standalone="no" ?>
<!DOCTYPE workflow SYSTEM "iwwf.dtd">

<!-- Do not use Perl comments in XML code without using XML comments
     to hide them
#=====================================================================
#  XML JOB SPECIFICATION SKELETON
#=====================================================================
#  This XML section is used to generate the job specification files based on
#  input provided by the end-user in the job creation form.
-->
<workflow   name = "AAA"
            owner = "iw_user" 
            creator = "iw_user"
            description = "zxcz">
  <!-- In above (and below) - the string "iw_user" is likely a clue to
       badly written WFT code - in XML it should be
       "__TAG__('iw_user');", in Perl it should be
       "__VALUE__('iw_user');" in either case, the result in the
       debugging view should be the actual userid of the person who 
       was trying to instantiate the workflow -->

  <!-- ============================================================ -->
  <!-- ======================== Add Files ========================= -->

  <usertask   name = "AddFiles"
              owner = "iw_user"
              start = "t"
              lock = "f"
              readonly = "f"
              description = "Add any additional files to be deployed">
...
  </usertask>
...
  <!-- ===================================================== -->
  <!-- =================== PrimaryReview =================== -->
  <usertask name="PrimaryReview" 
            owner="bbb"
            description="Primary review files by james" 
            readonly="t">

    <areavpath v='/default/main/TEMPLATES/DEV/WORKAREA/james'/>

    <successors>
      <successorset description="Approve">
        <succ v="Review-1-aa1"/>
 <succ v="Review-1-aa2"/>
 <succ v="Review-1-aa3"/>
      </successorset>
<!-- Extraneous double quote in next line -->
      <successorset description="Reject: send back to author"">
        <succ v="AuthorWork"/>
      </successorset>
    </successors>
    <activation>
      <pred v="AuthorWork"/>
    </activation>
  </usertask>
... 
</workflow>

The above is all without verifying that all the transitions from one task to another are correct.

ggan

Thanks for all of your prompt replies. It really helps.

Gary