Hi Kai,
I have no idea about that one, I’ve never tried to use RF like that.
It is quite easy to write the .robot file to a temp location and then just tell robot where the .robot file is. the other advantage is when debugging you can dig out the robot file and work out why something is not working or use it in a forum post if you need help.
My next suggestions was going to be to have a keyword library of pre defined keywords specific to your application that your testers could use as their step actions. The user would then write test steps like
| step action | expected results |
|---|---|
| Open xyz application as accountsperson | accountsperson logged in |
| create PO | PO has PO number |
Then your prerunner would include that keyword library, the keyword library would include all the libraries needed for automating your application and keywords that turned these phrases into a sequence of keywords that drive the application.
But if you go down this path with heavily abstracted keywords you will want to be able to grab that generated robot file when you need to debug these keywords.
Dave.