⚠️ File resources cannot be used across different Workspaces.
File resources can only be used within a single Workspace and any Environment that belongs to that Workspace. File resources are typically in combination with OneCloud Commands. Here are some common examples:
Associated OneCloud Command
Batch or shell script
⚠️ File Resources Should Not Store Data
File resources are not designed to store transactional data and should solely be used for file artifacts related to application integration. In some cases, it is helpful to upload a small limited data set (i.e., 10 records) for testing and integration, but should not extend beyond this purpose.
Upload File Resources
File resources need to be uploaded into OneCloud. Once uploaded, they are under the control of the OneCloud platform. As such, the resource can be edited and its audit history can be viewed.
⚠️ File Resources Maximum Size
The maximum file resource size is 10MB, but the OneCloud editor can only display a maximum of 256KB.
File Resource Editor
Text-based file resources can be directly edited and maintained via OneCloud’s simple text file editor. All changes can be viewed in the resource audit history.
⚠️ Binary Files
Note that binary file resources are not editable. If a change is required to a binary resource, then simply upload a new resource to OneCloud.
File Resource Audit History
File resources have versioning to track changes. Use the audit history to view and/or revert to prior versions of a file.
The total number of chains that a resource is being used in is displayed in the upper left. This is helpful in knowing before making any changes or deletes to a resource. Clicking on the Uses brings up a Resource Usage table similar to what is displayed when hovering over the DELETE button.
Deleting File Resources
File resources can be deleted if they are not being referenced and used in a chain within a particular Environment. If a resource is being used (in a particular Environment), then the delete option will be grayed out. To see which Chains and Commands use a particular file resource, hover your mouse over the delete button, and all references will appear.
Using File Resources in Chains
File resources can be used as parameters for many Commands. They are used and selected like Command Outputs. For example, with the Script Runner, a File Resource can be the Command File parameter. In other Commands, the file resource might be required, such as a Hyperion Financial Management point-of-view (POV) configuration file that defines the data extraction to a text file or database.
Promotion of File Resources
Any file resource associated with a Chain is automatically promoted when the Chain is promoted. The file resource will automatically appear in the associated Environment and can be edited independently.
📚 Related Topics: