...
The following target types are supported
Target Type | Description |
|---|---|
CoreIdentity | Directed directly at a user |
Email Address | Directed at a user with this email address without knowing the user. This might be used when we are not sure if the user already has an account yet for example. |
Mobile Number | Directed at a user with this mobile number without knowing the user. This might be used when we are not sure if the user already has an account yet for example. |
Users with confirm changes rights | Directed at all users who have the confirm changes rights on the targeted entity. |
SessionLink | Allows to access the interaction for any user that knows the SessionLink. SessionLink is generated in the activity and can be accessed by |
Target identifier
The identifier of the target based on the target type. So either an id or text value.
...
By setting one ore more tag, you can decide on which detail page a given user interaction should appear. So if you create a user interaction in relation with a communication data, you can set the tag to communication-data to show it on the detail page of the communication data.
Available tags:
Tag | Description | Example |
|---|---|---|
| A user interaction in relation to a users communication data |
|
| A user interaction in relation with a organization unit / company. You can add the id of the given organization unit to further specify which object it is affecting. Just us the |
|
| A user interaction in relation to a representation |
|
Combining multiple tags
You can also combine multiple tags together. Simply separate them by using the ; separator. Here is an example of a user interaction that effects two organization units:
...