Release Notes
Released Versions
- SDK 1.3 (viaworks 2.7)
- SDK 1.4 (viaworks 2.8)
Limitations
Messages in the Yammer framework do not have a modified date set. Furthermore, Deleted messages do not have the 'deleted' flag set, as they are simply removed.
API calls are subject to rate limiting. Exceeding any rate limits will result in all endpoints returning a status code of 429 (Too Many Requests). Rate limits are per user per app. There are four rate limits:
Autocomplete: 10 requests in 10 seconds.
Messages: 10 requests in 30 seconds.
Notifications: 10 requests in 30 seconds.
All Other Resources: 10 requests in 10 seconds.
Prerequisites
- A license for the Yammer Connector.
- A User account in the Yammer network is required. A service user access token is needed for indexing.
Authentication
Users are authenticated via Active Directory with the use of their User Prinicipal Names (UPN). The UPNs are matched against the User's email address, which is defined in the User object.
Authorization
Items are marked with a list of Yammer-related Group and / or User SIDs during fetching time.
At search time, User SIDs are matched against the SIDs marked on the items, and only items available to the User are returned as search hits.
Crawl Methods
Full Crawl: The Yammer Connector supports scheduling periodic full scans of the source system.
Incremental Crawl: The Yammer Connector supports ChangeSet functionality for Messages. All messages newer than the latest saved message, are retained.
DocumentHandler
The ViaWorks Document Handler is NOT required on the clients in order to be able to open search hits.
Custom Templates
No custom templates are required for this connector.
Hover: Default
Item: Default
Other information
Multiple connections can be configured, with similar or different content targets and Security options.