...
The interactions can be triggered from multiple places. They can be triggered from within a workflow, from within preexisting application logic or even from third party application using the CoreOne Application Program Interface V2 (API-V2).
Target
You can target a user interaction to different types. You can target it directly at a user or at a email address or even at a whole organization.
Target types
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 To send the session linke to someone, you have to build the full url:
|
Target identifier
The identifier of the target based on the target type. So either an id or text value.
Titles and description
Both the title and the description of the user interaction that will be displayed to the user can be set on the user interaction. This allows you to customize the appearance for your use case.
Tags
| Info |
|---|
Tags are available from version 8.0 |
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:
| Code Block |
|---|
organization-unit:3343;organization-unit:3353 |
Data Storage
The user interactions and their data are stored in the CoreOne Suite Meta Directory.
...