Skysens Docs
  • Getting Started
  • Agile Predictive Monitoring
    • Concept
    • Hardware
    • Wireless Networks
    • Platform
    • AI
  • Main Menu and Overview
    • Overview Usecases
    • Widget Types
      • Value
      • Gauge
      • Image
      • Notification
      • Map
      • Text
      • Intensity Chart (Heatmap)
      • Table
      • Line Chart
      • Bar Chart (Histogram)
      • Line - Bar Chart
      • Pie Chart
      • Sankey Diagram
    • Best Practices
  • Notifications
    • Notification Menu
    • Notification Types
  • Asset
    • Asset Types
    • Asset Listing
    • Asset Details
    • Application
  • Rules Menu
    • Rules Edit and Frequency
      • Condition
      • Action
  • Sources
    • Connection Types
      • Modbus TCP
      • MQTT
      • HTTP
    • Device Catalog (LoRaWAN)
    • Network Management (LoRaWAN)
      • Gateway
      • Device
    • Virtual Sensor
      • Value
      • Form
      • Simulation
  • Settings
    • Account Settings
    • Location Management (Settings)
    • User/Role Management (Settings)
  • Reports
    • Advanced Reporting
  • Logs
Powered by GitBook
On this page
  1. Rules Menu
  2. Rules Edit and Frequency

Action

Fortune favors the bold

PreviousConditionNextSources

Last updated 2 months ago

Action side of the rule editing menu has multiple capabilities to output data according to user need.

It also has built in data manipulation and custom calculation capabilities to design more complex data streams based on assets and fields manipulated at condition cards in condition side.

Similar to "Condition" side of the rule edit menu it works in card logic which are microservice structure.

Action cards can send notifications as Text, Email, Voice Message, or manipulate and write new data in to new fields in selected virtual sensors or trigger web-hooks for Slack, Microsoft Teams and other custom services.

Send Notifications

Users can send notifications of output of condition side of the rule as Email, Text or Voice Message.

Process Data

After selecting "Process Data" in "Actions" list user can process and manipulate data which are outputted from "Condition" with single or multiple condition cards.

If condition card is only one, only process method is "Custom" process method which enables user to write its own formulation with arithmetic operators.

After creating the process method user can use this output to be sent as notification, webhook or it can be used to be set as a new data field in virtual sensor.

To write new data in to data container user needs to select a virtual sensor, than name of the new field and unit of the value needs to be input.

Sending Webhooks

Users can directly send webhooks wheter data is manipulated or not.

For this, webhook URL is needed for Slack, Microsoft Teams or custom end points.

For multiple Condition cards scenario, other operators act same as in cards.

Please see page for more details.

Condition
integrations
General Action Card Structure (With Notifications)
Processing Data With Arithmetic Operators and Numbers
Setting a Virtual Asset Field
Webhook Details