Exporting/Importing Dynamic Versions [Deprecated]

It is possible to export one or more dynamic versions of an app and import it into another MobileCaddy installation, this guide will cover the steps between the export and import.

  1. To start, ensure you are in the Startup Tab. Choose “Export Full App or Single DV”screen-shot-2016-12-06-at-13-09-11
  2. Select the latest document structure you wish to export using the drop down list.
  3. Click “Select” Under the “Select Mobile Application” heading tick the app you want to export.screen-shot-2016-12-06-at-13-10-50
  4. Click “Select”
  5. Tick the boxes next to the according Dynamic Versions you want to export. This is under the heading listed as “Optionally Select DV’s”.
  6. Select “Export Selected DV’s”, shortly after, a message will then appear on screen.screen-shot-2016-11-15-at-17-07-02
  7. Select “Continue”
  8. A page will be displayed containing a summary of the export, select “Continue”.
  9. The IFK page will be displayed. Select “Continue”
  10. The document should have successfully been created, hence, a confirmation message should appear.
  11. Click on “Home” and go to “Setup” to find the queued job.
  12. Search for “apex jobs”, here you can see the status of the job.
  13. Click on the “All Tabs (+)” button and go to “Documents”.
  14. Select “MobileCaddy – Data Population” in the “Folder” drop down list under the Document Folders heading and click “Go!”screen-shot-2016-12-06-at-13-18-10
  15. Select the relevant document. This will take you to a page displaying the document detail.screen-shot-2016-11-15-at-17-12-27
  16. Right click on the “View file” link and choose “Save as” to save the file locally.
  17. Switch over to the targeted organisation, the place you want to import your document to. From here click on “Startup”.
  18. Click on “All tabs(+)”, then select “Documents”.
  19. Next, using the folder drop down list, choose “MobileCaddy – Data Population”
  20. Select the “New Document” button.
  21. Fill out the details accordingly.screen-shot-2016-12-06-at-17-29-12
  22. Select choose file, and select the file that was previously saved. screen-shot-2016-11-15-at-12-57-29
  23. Click “Save”. The document is now in the destination org.
  24. Click on startup and select create/install mobile application button. Fill out the details accordingly.
  25. Set the “User Provisioning” drop down list to “All users”.screen-shot-2016-12-06-at-17-32-48
  26. Set “OS Version Provisioning” to “Any OS Version”.
  27. For the template type, choose “Seed Application”.
  28. Choose the relevant template on the drop down list.
  29. Select “Save”.
  30. Message should appear confirming it is being created in the background.
  31. Go to setup, search for apex jobs to see the status of the job.
  32. Click “Startup”. The new app is under the mobile applications heading.
  33. Click on the new applications’ record to see further details.

Next we need to migrate the VisualForce pages and Static Resources that form the basis of the logic and UI of our application.

As an initial guide these fall into the following Categories:

  1. App Start Page – this is a VisualForce Page which will be called YourApp_XXX (for example YourApp_001 – where ‘YourApp’ is the name of the application you defined in Codeflow and ‘001’ is the Version that was set in the package.json – in this case ‘0.0.1’).This page is auto-created during the CodeFlow deployment process (not this is updated via the apex local template – pls ensure if you have added 3rd Party Libraries that these have been added correctly).
  2. App Cache Page – this is a VisualForce Page which will be called YourAppCache_xxx (for example YourAppCache_001 – where ‘YourAppCache’ is the name of the application you defined in Codeflow and ‘001’ is the Version that was set in the package.json – in this case ‘0.0.1’).This page is auto-created during the CodeFlow deployment process and uses a build process to scan your www directory to ensure all assets are noted in the cache correctly. This page is then referenced as the manifest for the Start Page above (this is all automatic).
  3. App Static Resource – this is a Static Resource which will be called YourApp_xxx (for example YourApp_001 – where ‘YourApp’ is the name of the application you defined in Codeflow and ‘001’ is the Version that was set in the package.json – in this case ‘0.0.1’).
  4. There are also the following MobileCaddy Static ResourcesMockCordova
    Cordova
    MC_Resource (this is to match the version that is specified and used in the CodeFlow build process)