Page tree
Skip to end of metadata
Go to start of metadata

Campaigns provide the ability to perform a set of operations on multiple Things or Connections Some examples for using campaigns are: 

  • Deploying Software Update Packages (SUP)
  • Firmware updates (Through a SUP)
  • Adding and deleting tags on various things or connections
  • TR-50 Method execution 
  • Pinging a group of gateways

Once a campaign is created and things or connections are added to the campaign, the campaign must be started or scheduled for execution. The actions of the campaign will run against the Things or Connections that are added. Once a campaign is started, the campaign actions are executed against each campaign member. 

Both the campaign and the campaign members each have a status value. The campaign states include Ready, Scheduled, Running, and Completed that indicates the current state of a campaign. Once the campaign is started, the campaign will not be finished until each campaign member in its list is completed (success or failure). For a list of the campaign member status see the following: campaign.find or click the View icon to the left of your finished campaign. Any campaign tasks that require parameters are provided as an array of parameters (dependent upon the task being executed).

What's Inside

  • No labels