You are viewing limited content. For full access, please sign in.

Question

Question

Workflow error

asked on July 27, 2017 Show version history

Good afternoon,

 

Recently we had installed the out-of-the-box "Contract Management System" in 10.2. We were successful in installing and running several form tests from where this is installed. 

Now we are trying to migrate the whole process to another machine but when I try to import an exported Workflow I get the error "element is an invalid xmlnodetype". 

I also try simply doing a "Save" from the first machine and opening it in the new one but I get the error on the screenshot below and some of the activities get automatically deleted.

Has anyone run into this issue? If you have, how did you get it resolved?

Both WF Designer versions are the same.

UPDATE: the Designer giving us problems is using 10.0.0.249 and the one that works is 10.2.0.216

 

Thank you,

 

Raul Gonzalez

 

 

FROM THE LOGS

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

'Element' is an invalid XmlNodeType. Line 666, position 12.

'Element' is an invalid XmlNodeType. Line 666, position 12.

 

7/27/2017 12:49:38 PM

System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

ThreadID: 1

 

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

Exception

        System.Xml.XmlException:

'Element' is an invalid XmlNodeType. Line 666, position 12.

 

Stack Trace

        at System.Xml.XmlReader.ReadEndElement()

        at Laserfiche.Workflow.Designer.Wfi.WorkflowImporter.ReadWfx(XmlReader xmlReader)

        at Laserfiche.Workflow.Designer.Wfi.WorkflowImporter.LoadExportedWorkflows(String file)

        at Laserfiche.Workflow.Actions.ShowImportWizardAction.Execute()

 

Data items: 1

AlreadyLogged: True

ImportWF.png
ImportWF2.png
ImportWF.png (34.18 KB)
ImportWF2.png (10.91 KB)
0 0

Answer

SELECTED ANSWER
replied on July 27, 2017

This usually happens when a workflow was created with a newer version than the Designer you're running and has features that did not exist in the older version.

1 0

Replies

replied on July 27, 2017

Thank Miruna; that was it. We upgraded the Designer in the destination server and now all it publishing as expected.

 

Thank you,

 

Raul Gonzalez

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.