What is a Module

You can think of a module as a project or job. Every module offers a complete and separate capability.  Information and data in one module isn't available to other modules.  Each module can have it's own forms, maps and settings.

What's involved in creating a module?

When we create a module, in addition to our forms, there are a couple of extra settings we need to think about:

  • Name: You will need to give your module a name. This is what people will use to identify modules, so make it short but descriptive.
  • Password: Together with the name, users will use the password to subscribe to your new module.
  • Colour: Because field users may subscribe to multiple modules, the chosen colour will be used across the client to distinguish the module and it's inspections.
  • Archive Age: Because you don't necessarily want to keep closed inspections on your field devices forever, you can specify how many days to wait before they're removed from field devices. They won't be deleted from the server, this only effects field devices. A common setting is about 30 days, but you can choose whatever suits your needs, from 1 to 365 or more.
  • Map Features: Any points, lines and areas to display on your map.
  • Forms:  All forms are part of an inspection class.  For more details see Inspection Classes