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

Question

Question

workflow won't retrieve fields from xml file

asked on January 23, 2020

I am importing an xml file with import agent 9 into Laserfiche 10.4.1. A workflow is to pick up the xml and populate a template. I receive the error "Value cannot be null. Parameter name: The argument 'entry name' can not be null. [0103-WF6]"  However if I open my xml all the fields are populated, also if i manually drag a file into laserfiche and populate the fields the workflow runs as expected.  It seems to not be able to read the xml. I will attach a sample xml file that my workflow can't read.

This was working before, I moved Laserfiche to a new VM on a new Domain all other workflows work and this one works if I don't use the import agent xml file      Any ideas would be appreciated

0 0

Answer

SELECTED ANSWER
replied on January 27, 2020

You do not import the XML file into the repository.  You put the XML file into the folder that Import agent monitors.  Import Agent then reads the file and imports the PDF file referenced by the XML and applied the metadata from the XML to the imported PDF.

If import Agent is importing the XML instead of the PDF, then either the file does not have the correct extension, the file is incorrectly formatted, or Import Agent is not configured correctly to handle the XML.

The issue (at this point) is not with workflow.

2 0

Replies

replied on January 24, 2020

Your workflow is not configured to read the XML, it is reading the template field values

1 0
replied on January 23, 2020

Also import agent is working it is pulling the xml file into laserfiche, but the workflow doesn't process it 

0 0
replied on January 23, 2020

Hi Wendi.

 

In my mind, it looks like the error is in your workflow, not in your file.

Please open your Workflow Designer , then go to the Window "Current Search".

 

Select your workflow and find the last one with the error message.

 

Double click on and see where is the error.

 

Copy/past a print screen.

 

In my mind, your workflow try to retrieve a value from the tag "A" but in your xml, the tag "A" doesn't exist or is empty. Then the return is NULL. So, if you try to rename a Laserfiche File by the tag "A", you'll have the error.

 

 

 

 

 

0 0
replied on January 24, 2020

Hi Olivier, Thank you very much for replying, I am attaching a screenshot of my error on WF activities. The WF does work correctly if i manually drag a file into laserfiche and fill out the fields.  It only errors when I import the xml file from import agent. But when i view the xml file all the fields are there but WF is not picking them up.  This all worked fine before I moved Laserfiche to a new VM. Also when I moved LF i did upgrade it from 10.2 to 10.4.1.  So I'm wandering if something changed in with upgrade. I did not upgrade import agent that is version 9.0.0.  Any advise would be appreciated.  

WFerror.PNG
WFactivities.PNG
WFerror.PNG (29.35 KB)
WFactivities.PNG (50.02 KB)
0 0
replied on January 24, 2020

Hi Bert, can you please let me know what I'm missing, how to make it read XML?  It worked before.  Thanks!

0 0
replied on January 24, 2020 Show version history

You said in your original post that a workflow is to

pick up the xml and populate a template

The workfolw image above is retrieving the field values and creating folder structure.  Do you have another workflow that does the field population?  If so, that workflow needs to run before the workflow shown above.

 

** EDIT **

I just looked at the attached XML file.  It is an Import Agent Import List file that directs Import Agent to import the "Sales Tracking System Template.pdf".  Import Agent should import the PDF with the Template and Fields assigned from the data in the XML file.  The workflow should be running on the imported PDF file and not an XML file, and it files the PDF based on the field values.

What is the extension of the original XML document?  If it is not XML, change it to .xml and re import it through Import Agent.

0 0
replied on January 24, 2020

Hi Bert, thanks for the quick reply.  I do not have another workflow that populates the fields. I don't understand as this workflow worked in LF 10.2  did something change in 10.4.1?  The workflow retrieved the field values from the XML and populated the fields and created the folder structure.  The xml is being pulled into Laserfiche by import agent I have attached a sample xml.   This all worked before the 2 things that changed are LF was moved to a new VM and was upgraded.

1retrieve fields.PNG
2pulled Sales Person Name and created folder.PNG
0 0
replied on January 24, 2020

see my edit in the post above.

0 0
replied on January 27, 2020

Hi Bert, I am attaching another xml file. This is how it is supposed to be. I changed import agent to assign the template just to see if that would make it work. Originally the xml files were like the one i just attached.  The process of the entire workflow is you go to web page and fill out a form (not LF Form) you can attach files on the web page. This creates the xml list file that workflow is to pick up and apply the fields and sort the documents.  Again this worked perfectly in LF 10.2 did something change in 10.4.1? I did not upgrade Workflow that is version 9.0. I don't understand why i'm getting the error attached, does workflow not read the xml file the same way from 10.2 to 10.4.1?

workflowError.PNG
stsWorkflow.PNG
stsWorkflow.PNG (35.92 KB)
0 0
replied on January 27, 2020

Did you move Import Agent too? Like Bert says, there is nothing in your workflow that processes XML. So it sounds like Import Agent used to be set up to use an XML list file to configure how to import documents, but now is importing the XML itself.

0 0
replied on January 27, 2020

yes I did move import agent to the new VM  but I did not upgrade it, it's still version 9.0

0 0
SELECTED ANSWER
replied on January 27, 2020

You do not import the XML file into the repository.  You put the XML file into the folder that Import agent monitors.  Import Agent then reads the file and imports the PDF file referenced by the XML and applied the metadata from the XML to the imported PDF.

If import Agent is importing the XML instead of the PDF, then either the file does not have the correct extension, the file is incorrectly formatted, or Import Agent is not configured correctly to handle the XML.

The issue (at this point) is not with workflow.

2 0
replied on January 27, 2020

Thank you very much Bert, i will look into this.

0 0
replied on January 29, 2020

Thank You Bert for pointing me to import agent for this issue. This has been resolved by editing the IA profile on the general tab under Filter /Determine which type of files....   I did have the All files selected, however in the box grayed out xml was there. So i selected the only those files.... radio so I could edit the box and removed xml  then reselected the All files radio and it starting working again.

Thanks again for your help!!  Respectfully, Wendi

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

Sign in to reply to this post.