Yes - we added checks for blank (and not blank) strings to the job characteristics. I will update the original post.
Is there an update for this problem, or a new feature in FFcore , because now we use tests to verify if the field (in MAX) is empty, so we have many test in the workflow, and we have a big workflow.
If a new feature exist I am very interesting.
Guy Le Pecheur Field Engeeneer
Customer : ARKEA
If you have a column that will either have text or the path to an image then you will need to create a branch for the text and another for the image. You should be able to route between them by checking the text in the variable to see if it is an image (e.g. contains .pdf or contains .jpg, etc.)
About the phone number example:
A variable may or may not have data so you should not need separate branches for the cases in which there's a phone number that's not there for some recipients. If you are seeing other behavior (which would be a bit surprising) please engage the hotline.
Thank you for your reply, I just had this installed and I am using 188.8.131.52
I don't believe your solution would work for me as on one form I am bringing in a title (Text) for a cover along with an Attn line of the recipient in one version and a Graphic in the alternate version in the same location depending on the need.
I also have some stand alone information that I do not have for every recipient. Example would be a phone number. Normally this would remain blank which would be as i intended, now however I need to create a branch now to accomplish the same task.
Any thoughts are welcome.
There's another difference between FFProM and FFCore that might be relevant to this case...
From the FFCore Help document:
Newline control characters (\n and \r\n) are replaced by carriage returns.
So - instead of having two MAX columns for Address and Address2 you could submit both values in a single MAX column and prepend the newline control characters to the value in Address2 (if any).
This would also open up some possibilities that are not available in FFProM.
I asked development to add the check for whether a string is blank in response to this thread on the forum. It could not be done when I posted the reply above.
Let me make sure that I understand your concern:
If you have a manifest field mapped and use a variable somewhere in the workflow then the job will error if that field happens to be blank. This is different vs FFProM which would not fail the job.
Is the above correct? Also, where are you using the variable?
I have recently been changing over from FreeFlow builder to FreeFlow Core and JavierM I found your answer here to be confusing.
3. If you do not want to do any scripting at all then you could use the Job Characteristics to check the content of Address2. You can't check for whether the field is blank but you can check to see if it uses a vowel or a number as a proxy for checking to see if it is blank. You then use that job characteristic to route between two different watermark presets - one that uses Address2 and one that does not
One of my frustrations with Core is the programs failure to process with a Max field blank. (Unless I am missing a setting) Which requires me to create branch paths for using multiple watermarks. I have a conditional that looks for wether a cell is blank or not which you say here can't be done. (unless this is a later version).
I was going to write something but here's a picture:
Jusy make sure you set things so that Any Condition and Any Set ar met for the job characteristic to be considered true for the job.
I'd like to use option 3 but I don't see how to "check to see if it uses a vowel or a number as a proxy for checking to see if it is blank"
I create a new Job Characteristics, I add a new condition, I select MAX>Address2 contains : what exactly ?