New In This Release
Improved Dashboard Notifications
We had some requests to make our notifications more visible and more usable, so we have. Please note the screenshot below. Notification have moved from the bottom of the screen to the top right of the screen. There is a notifications bell icon with a badge indicating how many notifications there are. Each notification can be individually dismissed, or they can be dismissed en mass. The SmartPin icon, name, and address are prominently visible in the notification underneath the color- coded and icon-coded banner containing the notification message. Tapping on the ‘View’ button in the notification will display the SmartPin details for that notification.
Deleted By Column in SmartPin by Age Report
When displaying Deleted SmartPins in the SmartPin by Age Report, a Deleted By column is not present.
Customer Partner API
Partners need to be configured for your customer by Nrby administrators. But once a Partner has been configured, you can now control whether the Partner is enabled or disabled in the dashboard UI as well as the API. In the Customer Settings screen for our demo Customer, you can see Nrby administrators have configured two partners, Partner1 and Partner2.
If you return to the dropdown menu in the upper right corner, you will notice a new Partners option that allows you to enable and disable each partner individually.
Below is the API documentation for Customer Partners.
SmartPins that have been marked as Parent SmartPins, and appropriately configured with identifying Attributes can now contain other SmartPins as children SmartPins. Children SmartPins behave the same as regular SmartPins, but they can be organized as tasks for parent SmartPins. The screenshot below depicts the new Tasks tab that shows up only on Parent SmartPins. This is our initial implementation and rollout of this feature. Improvements are already on the way.
First, determine how to uniquely identify each instance of your parent SmartPins through Attributes. Perhaps it is a NodeName attribute (as depicted here), or a combination of a NodeName and Franchise attribute. Configure those Attributes as Parent Identifiers that are both Required and Persistent.
Then, in your Parent SmartPin, add the identifying attribute(s) as Attributes of the SmartPin. Now you can add the potential types of child SmartPins to your parent SmartPin. The identifying attributes will automatically be added to the children. Below, you see our Node Parent SmartPin using the NodeName identifying Attribute and having NodeChild1, NodeChild2, and NodeChild3 SmartPins as types of children.
Now, when you create a parent SmartPin on the map, you provide the uniquely identifying attribute values, and any other attribute values, as depicted below.
And you do the same when you create a child SmartPin.
When you do that, the children SmartPins automatically appear as tasks in the parent SmartPin details.
Now, when you view the Attributes History report for the parent SmartPin, it will automatically include the children SmartPins in the attribute history. Below we are displaying the Attributes History for the Node Parent SmartPin.