Your options are:
Customer Space - Temporary disk storage on the server
Document Repository - Permanent disk storage on the server
If temporary will work for you, then you should/could look into pass global variables around by way of fabricating new session objects based on a common mapping naming convention.
E.g., I want to store/retrieve the CSQ with the most waiting contacts in it. So I create a new session, map it to a name of "csq data", and in each script, read from it, the variable named "contacts waiting count", and if my quantity of contacts waiting is greater than that retrieved value, update the variable named "contacts waiting count" and the other variable "contacts waiting csq," with my CSQ name. Otherwise, don't update it, because I have less contacts waiting.
If you need permanent storage, then you will definitely need the repository for your storage. You will however require a username and password of a callmanager end user, so that you can authenticate them, and upload the document as them. You know, for AAA reasons I suppose. Which brings me to, why would I want to let just any old callmanager user update my contact center documents? Oh well, at least you have the get user info step available, and can make sure they are at least and agent/sup/admin.
E.g., You have a Call Center status IVR, for which a supervisor can call into it, and set the Call Center into a "meeting" mode. Your actual Call Center script can then reference that file from the repo, and make routing decisions based on it.
In neither case, do you actually need the create file step though. In fact, I cannot think of a time in the last 5 years, that I have ever used the create file step. But then again, I also have never used the create url document step either, and I call external URLs quite often. Hint: Set http_response = url[http://www.google.com/]
