deviceWISE Cloud 19.09 Release Notes

New

Added logic to recalculate usage-cache during every CDP sync.
Implemented a REST (POST) solution allowing a user to recover their account and reset their passwords in the Logging into the App Center.
Implemented credential validation before creating/updating of LoRa providers.
Added ability to store the previous payload of a LoRa device on uplink.
Added funtionality to automatically set Confirmable True, when Serialize is set to True. For more information, see Sending downlink to a LoRaWAN device
Now a LoRaWAN Thing will display Motion Indicator and Last uplink upload fields.

Documentation

Updated the Campaigns with a table that shows various states of a Campaign and Campaign members
Added MQTT Interface diagram and note about QoS levels. For more information, see MQTT Interface
Added action to publish messages to Microsoft teams teams.webbook action
Added topics about Using the Actions Menu (Thing) and Using the Actions Menu (Connection)
Added details of the Flush downlink queue in LoRaWAN
Added a topic explaining about MQTT Control Packets
Added samples that uses BBox to thing.aggregate.locations and cdp.connection.aggregate.locations
Added details on newly added Rate plan field to Changing Status
The following events will now be able to filter using the newly added Carrier field

Fixes

Fixed an issue in the Device profile edit screen which will not cancel on clicking Cancel.
Fixed an issue with file column sorting being passed to thing.list error
Fixed an issue that stopped the Campaign clone to work when clicked the clone button on the Campaign dashboard.
Fixed an issue that fails to update the Email notification while editing a Campaign
Fixed an issue that prevented to show the current Things in the Current Thing tab in the Geofences
Fixed an issue that allowed to edit the Connections Carrier Custom fields
Fixed an instance where a badly constructed lwm2m.metadata.register parameter would return a cryptic error message.
Fixed the Things list table where certain custom column types where not showing.
Fixed an issue that stopped updating the Thing definition.

Improvements

Improved the access settings to a user who has been revoked access to the default org or when the default org has been suspended. Those users will be able to login to another organization if they have the right to access it.
Improvised the trigger logic to allow processing of attributes, alarm, and properties that have colons (:) in the key.
campaign.template.create will now validate JSON structure and eventType element of the campaign parameter.
The thing.find action campaign/trigger action will now return LoRa or LwM2M device information (where available) when the Load Values parameter is set to true.
Added new output field(periodUsage) for trigger event connection.usage.change event . It will return the usage for the specified time period that caused the trigger to fire.
Added View JSON under Actions menu while viewing a LoRa Thing
After every login attempt (which also occurs after every user initiated update), the status of the provider object will be updated if it changes. This will indicate if the last authentication of the the provider was successful. This will be displayed on the LoRa provider list page, and on the provider view pages.
When auto generating Things is not enabled for a provider (no Thing definition specified), the Actility sync will gracefully fail, log the information, and bypass the backfill logic (not making the request to Actility for the list of devices).
Additional validation for from/replyTo email address parameter for email.send action..
Added reset password feature to Logging into the App Center