RoboFlow: PITA to configure, awesome when it works

I’ve spent the bet­ter por­tion of the last few weeks fight­ing with RoboFlow. My main gripe is the doc­u­men­ta­tion is next to non-existent. What’s there is spotty and you can’t be sure it’s even accurate.

After going back and forth with Canto Sup­port for a few days, I’m pleased to say I’ve got some nifty work­flows in place that would have been next to impos­si­ble with­out cus­tom EJP devel­op­ment work. 

Bot­tom line: This Cumu­lus Add-on has the promise to be an essen­tial cog in your DAM work­flow design if Canto can pro­vide some robust doc­u­men­ta­tion. More to come on RoboFlow later.

5 thoughts on “RoboFlow: PITA to configure, awesome when it works

  1. Hi Andrew,

    I’m going through my own RoboFlow PITA learn­ing curve at the moment too, and agree that some decent doc­u­men­ta­tion could make this a killer fea­ture for Cumu­lus. I’ve man­aged to get my record fields being updated with SQL data, and moving/copying records between cat­a­logues based upon con­di­tional fields, embargo dates, etc, but it’s taken many hours of trial and error.

    How have you gone with using the “Con­di­tion” field within the Para­me­ter file. No mat­ter what I do it doesn’t accept any­thing other than “true”. I want to have one work­flow to copy records to mul­ti­ple cat­a­logues based upon a field value, but I am hav­ing to have 1 work­flow per con­di­tion, which is just clunky…


    • Hi Chris,
      Thanks for com­ment­ing. I haven’t tried to use any of SQL work­flow types yet. The major­ity of my ‘flows are of the hot­col­lec­tion type. I do have a few hotcollection-find-related, hotfolder-redirect-file, and watchcategories.

      Which work­flow type were you work­ing with where there is a Con­di­tion field? Was it in the AutoParam.xml or GUI?

      • Hi,

        I’m doing a “hotcollection-copy-move-record”, and using the “Recor­dAc­tion­Con­fig­u­ra­tion” param.txt file.

        Essen­tially what I thought the “Con­di­tion” could be used for is a Cumu­lus Query, i.e. (“FieldXX” == True), which would then deter­mine the Cat­a­logue that the record is to be copied to, so then you could have mul­ti­ple Rows of:

        (“FieldXX” == True) -> Cat­a­logueA
        (“FieldYY” == True) -> Cat­a­logueB

        I found some good videos by Peter Van de Poele on RoboFlow (, but none of them that I’ve seen so far actu­ally go into the specifics of using the Con­di­tion field.

        • Peter was the guy who orig­i­nally wrote RoboFlow. He’s got some help­ful videos on his youtube chan­nel, which help a lot. (I’ve watched a bunch.) But, they don’t cover every aspect of the appli­ca­tion, alas.

          I just had a peek at the readme screen for that work­flow type… in true RoboFlow style it left me a bit more con­fused then had I not.

          Con­di­tion: if value true if will be executed

          Huh? I’m assum­ing it was sup­posed to be “if the value is true, it will be exe­cuted”. But, it doesn’t say what sort of con­di­tion it’s expect­ing. I would, like you, assume the con­di­tion to be some sort of Cumu­lus Query.

          Prob­a­bly the best thing to do would be to con­tact your Cumu­lus sup­port provider. I’ve found that’s the quick­est way to sort these things out.

          If you get it work­ing, please come back and share how!! Best of luck with your workflow.

          • Well I got the offi­cial response back from Canto, and the Con­di­tion field is only a True/False, so you can only use it for either per­form­ing mul­ti­ple actions at once, or a sim­ple If.. Then.. Else logic, based off of if the Cumu­lus Query returns True or False.

            A pity, but kind of under­stand­able as well. If you could put mul­ti­ple Query con­di­tions in, and com­bine your work­flows into 1, then it sort of gets around their pric­ing struc­ture of mak­ing you pay more if you want unlim­ited workflows…

Put your DAM comment here!