CloseMe doesn't save
AnsweredHi
I have noticed that the Close Me action doesn't save the project even with the Botflow set to: Save changes when executed through FoxHub. Is this a known bug?
Before running:



After running


-
Hi Andrius and Jesper,
you can't save a project when running thru FoxHub. FoxHub compiles a project and "sends" it to the bot. It will transfer the script over to that bot in a temporary state and then execute it. So the original script won't be modified. This is done intentionally to keep the original script untouched. Imagine if multiple bots are running the same project and each of them is saving the changes. Chances that something will be lost are high. So that means that if you need to reuse something as a result of running the project, it needs to be saved outside the project. -
Thank you both for the answers.
One follow up question, does it mean then, that Save action (under 'Me' -> 'Botflow') wound't save the project as well executed through FoxHub?
Since this is done intentionally, is there an easy way to save all the variables to excel, csv or something, since the only option I found to extract everything is saving a Report, however the problem with this one is that it cuts the names, for example I want to save the path to the trigger file, but in the report I can only see ('C:/ProgramData/Foxtrot...') which is not the most helpful thing.
Here is an example from one of the PDF Variable Reports I have:

-
Correct, if a project started from FoxHub - Save actions won't work.
As for your question - if you want to reuse the values or log them for reporting purposes then the easiest way is to use Write File or Write Log. Then you can import the data next time the project is run and use those values. Or just keep writing to the log file with every run to be able to track the process.
Please sign in to leave a comment.
Comments
4 comments