Connection filters
Connection filters are preferences set by the user to help determine who can interact with them, whether via chat or create a task, assign a task etc.
Last updated
Connection filters are preferences set by the user to help determine who can interact with them, whether via chat or create a task, assign a task etc.
Last updated
The following services are available for the Connection filter.
To create the connection filter, the user's id is needed, this can be gotten from the login response.
The IConnectionFilter is the payload required to create a connection filter.
event
The type of activity the connection filter preference is being setup for
see IConnectionEvents
key
The property for which the connection filter is to take effect
see IConnectionKeys
value
The resultant preference for the said property
string | number | string []
decider
The determinant which would help enforce the filter preference
see IConnectionFilterDecider
IConnectionKeys
IConnectionKeys refers to the properties which connection filter preferences can be effected upon. The following can be found as properties in .
tags
The labels for the user
string []
tagCount
The total count of labels for a user
number
afroScore
The score of the user in the chainsite
number
The resolvers for the connection filter.
greater_than
This decider checks against the current value for that property, if its more than the expected value
less_than
This decider checks against the current value for that property, if its below the expected value
equal_to
This decider checks against the current value for that property, if its exactly the expected value
contains
This decider checks against the current value for that property, if the current value is made up, in part or whole of the expected value
between
This decider provides an option for a range, between a minimum expected value and maximum expected value
IConnectionEvents refers to the activities for which connection filters can be set up and managed.
CREATE_CONVERSATION
Simply means, to initiate a chat, the sender must make sure they meet the preferences of the recipient
The authorization jwt token is required for this service.
The PAKT SDK allows the user to fetch their preferences.
The authorization jwt token is required for this service.
See sample implementation
Users can change their preferences at any point.
The authorization jwt token is required for this service.
See sample implementation below