Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
1 Reply
DavidU54339-XRX
FreeFlow Production Workflow Moderator
FreeFlow Production Workflow Moderator
‎02-11-2020 02:43 PM

Re: Job Metadata variable not working in Save node

I have been able to recreate the problem in 5.4.1. It did not exist in 5.1.2.0 (Silverlight). I have written a SW BUG against the issue.

It would also be helpful if you could generate a bug report (SPAR) by contacting Xerox Customer Support at (888) 550-6336 .

0 Kudos
Reply
ChrisBeech
Premier Partner
‎02-10-2020 04:15 PM

Job Metadata variable not working in Save node

I am currently migrating from Core 5.1.0.10 (silverlight) running on W2012-32 to Core 5.4.1 running of W2019-64. Running 5.4.1 as a trial until workflows have been migrated. 

I am running into an issue using a metadata variable in the file naming. I have existing workflows in 5.1.0.10 that are using the $FFwfJob.documentGroupCount$. The jobs are submitted using a MAX file, and have the resulting files joined using a Join Node. 

Under 5.4.1, the variable is always populated as "1" instead of the count of documents submitted. In a test case, I have a 4 line MAX file so know the resulting count should be 4. The page count $FFwfJob.totalImpressions$ is working correctly. 

How can I go about troubleshooting this? Is this possibly a bug in the latest version understanding that there has been a major rework of the enviroment between the 2 version. 

I need to make a decision on whether this is something that can be resolved before making to move to complete the migration. 

Thanks in advance. 

0 Kudos
Reply