OneCloud File Resources are text or binary files that are stored in a OneCloud Workspace. File resources can only be used within a single Workspace and any Environment that belongs to that Workspace.
File resources cannot be used across different Workspaces.
File resources are typically in combination with OneCloud Commands. Here are some common examples:
|Example||File Type||Associated OneCloud Command|
|Batch or shell script||Ascii text||Script Runner|
|Calculation script||Ascii text||Execute Essbase Calc Script|
|Configuration files||Ascii text||HFM Export Data|
|Template file||Ascii text||Handlebars|
|Custom executable||Binary||Script Runner|
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.
File resources need to be uploaded into OneCloud. Once they are uploaded, they are then under the control of OneCloud, where 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.
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.
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 resources have versioning to track changes. Use the audit history to see prior and revert to prior versions of a file.
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.
File resources can be used as parameters to many Commands and 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.
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.
Learn how to Integrate Notification.