Please give details of the problem



    User Guide

  1. Usage Report
  2. Logs Application
  3. Easy Builder
  4. FAQ
  5. User Management
        1. Composite API Design Tab
        2. Composite API Configuration Tab
        1. Providers
        2. Connectors
        3. Processes
        1. Roles entities
        2. Organization
      1. Collections
        1. Project Files Tab
        2. Project Definition Tab
        3. Project Versioned Files Tab
        4. Project Version Tab
        5. Project Description Tab
        6. Version
        7. Project Rights Tab
        8. Project Collection Tab
        1. Web Interface JS Tab
        2. Web Interface Design Tab
          1. Image Widget
          2. FileUpload Widget
          3. StaticText Widget
          4. ProgressBar Widget
          5. TextInput Widget
          6. JavaScript Widget
          7. Section Widget
          8. Geolocation Widget
          9. Checkbox Widget
          10. RadioButton Widget
          11. Tree Widget
          12. Spinner Widget
          13. History Widget
          14. URLInput Widget
          15. Tab Widget
          16. List Widget
          17. Array Widget
          18. HTML Editor Widget
          19. Report Widget
          20. Button Widget
          21. Custom Widget
          22. Captcha Widget
          23. HTML Widget
          24. Multi Checkbox Widget
        3. Web Interface Analytics Tab
        4. Web Interface Collection Tab
        5. Web Interface Implementation Tab
        6. Web Interface API Tab
        7. Web Interface Stylesheet Tab
      2. Revision
      3. Custom Lists
        1. Process Variables Tab
        2. Process Measures Tab
            1. Process Timer Event
            2. Process Start Event
            3. Process Intermediary Event
          1. Gate
            1. Process Task Loop Tab
            2. Process Task Manual Tab
            3. Process Task Email Tab
            4. Process Task Connector Tab
            5. Process Task SubProcess Tab
            6. Process Task Functional Tab
            7. Process Task Script Tab
          2. Process Step Output Variables
          3. Process Step Testing Variables
          4. Process Step Input Variables
        3. Process General Tab
        4. Process Design
        5. Process Input Tab
      1. Home
      2. My Tasks
      3. My Applications
      4. Files
    1. Customer Management
      1. Messages
      2. Scheduled Process
      1. Process Examples
      2. Connectors
      1. Users
      2. Configuration
      3. Usage
      1. Web Interface Reports
        1. Measuring
        2. Runtime Users
        3. Execution Path
        4. Parameters
    1. RunMyApp for Android
    2. RunMyApp for iOS
    3. RunMyApp for Windows
  6. My Settings
  7. App Translator

Project Collections Tab

Allows you to add a collection to your project.

A collection can be :

  • Public (no authentication needed) or private (authentication needed to be accessed)
  • Read only (users with access right "user" on project [i.e. P_user in a process or P_connected_user in a web interface] won't be able to modify it) or not

Name of collection.

URL of collection to be used within REST API.

info1 A collection created or imported while in Test mode cannot then be accessed in Live mode

Allows you to retrieve the first level keys of your collection.

Import/Export of Collections

A MongoDB collection can both be exported as well as imported. You can do so via the corresponding actions in the collection tab as shown below.


When exporting a collection, you can select one of the three runtime modes (Test, Acceptance, Live) as source collection. You also have the choice between an export in JSON or BSON format. The native storage format in MongoDB is BSON, a binary JSON format. BSON is also supported by the native MongoDB "mongodump" tool. Thus if you want to restore a collection in an external MongoDB, BSON will be the format of choice. BSON should also be used for backup/restore purposes within RunMyProcess. If you want to post-process a collection via a script, you may prefer the JSON format instead.


Both the import and export procedures are asynchronous. Depending on the size of the collection, it could take several minutes to perform these actions. Upon triggering an export of a collection, the platform will "just" acknowledge the request. Upon completion of the export procedure, you will receive an email. The email will also contain a link to your dump file in the file storage of the parent project.

The filename has the following format: collection_{collectionId}{mode}{date}.{json|bson}. An example is shown below.


Vice versa it is possible to import a dump file. You can, again, choose between one of the different modes (Test, Acceptance, Live) as target and you have to specify the import format (JSON/BSON). Additionally you can select whether the target collection should be dropped (cleansed) prior of the actual import. Finally you have to select the source dump file from the project's file storage.


As already mentioned, it may take a while till the data is available. You will be informed via email again.

info6 Please note that MongoDB doesn't provide transactions (thus also no rollbacks). If your import fails at some stage during the import procedure, your collection will be in an partially reconstructed state! An import should therefore be handled with the necessary care. Please also note that MongoDB recommends to use BSON data for import. If you have to work with a dump file in JSON format, you should generate an additional dump in BSON format prior of performing the import.

info7 While it is technically possible to import/export a collection on a "hot" application or process, it is best practice to stop all potential activities on the collection prior of performing these actions.