Technical FAQs

Can I share Web Asset files to other applications?
When you upload a set of ‘Web Asset’ files to your application, you can make the whole set ‘Public’ or ‘Private’. You cannot set these visibility privileges individually to a single file. So, whatever you have set, it will be considered for all the ‘Web Asset’ files.
For each operation performed on the application, logs would simultaneously be written into two files, one which is OreOps-specific and the other, application-specific. Logs specific to your application would be given to the end-user only ‘On-Demand’.
Source-code would be given out to ‘Enterprise’ customers only ‘On-Demand’.

Oreops is not open-source. 

But the apps you develop using OreOPS can be made open-source as per your wish.

Yes.

Once a file is checked-out by a ‘Contributor’, only he will have provision to write to it. It remains restricted to ‘Read’ to the remaining users. When the same file is checked-in, any ‘Contributor’ could check-out and write to it. Every modification made to the file by each ‘Contributor’ is recorded and stored as a separate version.

Yes, through Data Connector. It allows you to connect your database server to retrieve and perform appropriate operations on your data.

OreOps currently allows you to connect to 

  • Oracle
  • Google Sheets
  • MongoDB

You can also retrieve data using APIs.

The minimum requirement to run your application on

  • Android – v5 & above
  • iOS – v9 & above
OreOPS mainly supports 2 browsers – Chrome and Mozilla Firefox. Other browsers Safari, Opera & Internet Explorer can be used (design errors might pop up) but not recommended.