Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Introduction

In many business cases there is a need to interact with a user. The CoreOne User Interactions are an easy way to cover use cases such as get an approval from someone, gather feedback from someone or just inform him about a task ahead. Those user interactions will appear on the users dashboard and depending on the interaction type, will display the information to the user and display the possible actions. Once they are performed, the user interaction simply disappear from the dashboard again.

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.

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.

Data Storage

The user interactions and their data are stored in the CoreOne Suite Meta Directory.

  • No labels