All devices and workflows belong to a single application. Users can have multiple applications as needed. Dashboards do not belong to an application since a single dashboard can contain graphs and blocks for several different applications.
There are a few places within the platform from which an application can be created; or, applications can be created at any time using the main
When creating an application, you will be asked for three pieces of information:
- Application Name: You are required to name your new application. The name can be changed at any time.
- Description: Optionally, you may also provide a more detailed description of the application.
- Owner: The application must be scoped to your personal Sandbox or to an organization for which you have the Editor role. The owner can be changed at a later date only if you have Administrator permissions for the parent organization (or Sandbox).
Applications can be deleted on the settings page. Deleting an application cannot be undone. All devices, device data, workflows, and device recipes owned by this application will be permanently removed.
The Application Log is a real-time log that displays helpful information about various aspects of your Losant application. It’s most useful for debugging purposes.
As a real-time tool, the Application Log will always begin in an empty state. Logs will appear as actions on your application take place. Logs will show for the following cases:
- MQTT Authentication - A log will appear when an MQTT client successfully connects or fails to connect to the Losant MQTT broker.
- Raw MQTT Messages - MQTT Messages sent or received by the Losant MQTT broker will appear in the log.
- Device State - When devices report state, a log will appear.
- Device Commands - When Losant sends a device command, a log will appear.
- Device Connection Status - When devices successfully connect or disconnect from Losant via the MQTT broker or the REST API, a log will appear.
- Webhooks - When a Webhook is triggered, a log will appear.
- Webhook Replies - When Losant replies to a Webhook, a log will appear.
- Endpoint - When a request is made to a Losant Experience Endpoint, a log will appear.
- Endpoint Reply - When Losant replies to an Experience Endpoint, a log will appear.
- Integration Messages - When Losant receives a message from an Integration, a log will appear.
Resources can be looked up and accessed from any page within an application by searching for it using the search bar within the subnavigation. The search panel can be opened by clicking on the search box or by hitting Option (⌥) + L on Mac or Alt + L on Windows.
The search panel displays a list of recently accessed workflows and devices and links to common routes when it is first opened.
As a term is input, the options will filter and return resources that match. Resources can be looked up by name or partial name and results are restricted to the current application.
Application globals are a set of key/value pairs that are accessible inside of any workflow in the current application. This is a great place to store application-wide configuration that is used across multiple workflows, like phone numbers or API keys.
Any values configured here are accessible under the
globals object on the payload in a workflow run. The globals will always be accessible on the application workflows; however, each global will only be exposed to edge workflows if
Do not send to edge workflows is left unchecked.
Application globals can be overridden within a workflow by defining a different value at the same key in the globals for that specific workflow. You can read more about workflow globals here.