Skip to content

Using Developer Mode for Safe Changes

When creating a new Inspection, modifying an existing Inspection, or updating Library Scripts, it can be useful to make changes without affecting the currently running version. Developer Mode is only available for Users who belong to a Role with the Developer Mode Data Record permission.

In order to enter Developer Mode:

  1. Click the User Settings button in the top right of the header navigation. An image showing the location of the user settings button
  2. Change the Script Mode dropdown to Developer Mode. An image showing the location of the Script Mode setting

These steps may also be used to disable Developer Mode. Logging out and logging back in will also reset the Script Mode to Production Mode.

Data

Collecting Data

Any data which is collected while in Developer Mode will automatically be deleted after a set period of time, determined by the value of the Cleanup Dev Data (days) Global Setting. This restriction only applies to entered data. Other entities created while in Developer Mode will not be removed after a set amount of time.

Analyzing Data

Data entered while Developer Mode is active will not appear during analysis for users who do not have the Developer Mode permission or for users who are currently in Production Mode.

Updating Library Scripts

Information

This guide assumes that you already have a Library Script which is in use in an Inspection or a Dashboard.

Library Scripts can be updated and tested without affecting production Inspections or Dashboards by using a combination of Developer Mode and Library Script Revisions.

  1. Navigate to the edit page of the Library Script you wish to update.
  2. Edit the Published Revision. An image showing the edit page of a library script with the published revision button highlighted

  3. Update the code as desired.

    Warning

    Be careful not to overwrite the Published Revision while working on the new version. If you have large changes to make, it is recommended to make a small change and immediately save as a new Revision. Subsequent saves to the Library Script will overwrite the new Revision instead of the Published Revision.

  4. Press the Save New Revision button. An image showing an updated library script with the save new revision button highlighted

  5. Enter a Note.

    Information

    Notes are used to keep track of why changes were made. Make sure to enter a descriptive note of the changes being made.

  6. Press the Confirm button. An image showing the note overlay of the library script

  7. Set the newly created Revision as the Development Revision. An image showing the location of the development revision
  8. Save the Library Script.

Any Inspections or Dashboards which use this Library Script will now load the new Revision for any user in Developer Mode. You may safely test your changes to the Library Script by enabling Developer Mode and navigating to the appropriate Dashboard or Inspection.

When you are satisfied with your changes, you may publish the changes for all Users:

  1. Navigate to the edit page of the Library Script.
  2. Set the Live Revision to the newest Revision.
  3. Optional Unset the Development Revision. An image showing the location of the live revision
  4. Save the Library Script.
  5. Use the User Settings overlay to enter Production Mode.
  6. Check that the changes to the Library Script have take effect on the Dashboard or Inspection.

See Also