i

Please enable JavaScript to view this site.

Every person using Deyel or any of its applications based on this platform are called users. As such, they have a code that uniquely identifies them, a password which allows them to authenticate and initiate the work session and a user profile, that collects their personal information, working information, their preferences, additional data, etc.

 

There exists a type of user that does not represent a person, called "Intelligent Thing". It is about devices, virtual or physical, that have the capacity of communicating with other devices, reacting to events and executing specific functions. Intelligent things can participate of business processes, as initiators of them or as responsible of executing activities, so as to optimize the execution of such processes. For example, the execution of daily tasks or calculation tasks can be delegated to them.

Chatbots

 

Among the users of type "Intelligent Thing" there exists a particular type that is the chatbot.

 

A chatbot can communicate with the other users using Tedis, interpreting specific messages. Each chatbot can define a process to model the way in which it responds to each of the messages received. The answer can be simple, for example responding with a predefined phrase, or it can be more complex and shoot the execution of a business process.

 

Chatbots are defined to interacts with users through the messages, delegating this way the execution of tasks. Human users can use the chatbots as their assistants, so that they automate the actions the user wants and reply to their messages.

Properties

 

For each user a profile is kept with the following information:

 

User Identification

 

Labor Data

 

Delegations and Absences

 

Security

 

Personal Data.

 

For users type "Intelligent Thing", Configuration Data.

 

 

Usuarios_img01        

 

An asterisk “*" on the label indicates that the property is required.

 

User Identification

 
Profile Image

Each user can upload to their profile an image from a file. In case of not informing, an image with the user´s initials is automatically generated.

 

User

Code that uniquely identifies the user.

 

Alias

The value entered in this property works as an alternative code for the user. For example, email address can be used or any other coding that uniquely identifies the user. Deyel checks that there are not two users with the same alias.

When entering the portal, the user can enter either his code or his alias to authenticate.

 

Behavior Indicators

Information about usual tasks, days worked and the last tasks of the user are graphically displayed.

With the indicator “Most usual activities” a ranking of the most executed activities is displayed.

With the indicator “Worked days”, it is seen how his presentism was. When clicking on this indicator, the profile form is displayed so that absences and licenses with their type and period covered are displayed.

With “My tasks” a summary of the assigned tasks is displayed, together with their state regarding their due date. By clicking on these tasks, you can show the grid of the task with its cases.

 

Cover Image

It can be personalized selecting an image to use as background from the icon. fondo.

 

Name - Surname

These properties may not be informed for "Intelligent Things" .

 

Email

The value entered in this field works as an alternative code for the user. Deyel checks that there are not two users with the same email.

Labor Data

 

Organizational Unit

Indicates the organizational unit in which the user works.

 

Authorizing

Determines the one in charge of authorizing or approving the procedures started by the user.

It is an optional property, that makes reference to another user, belonging to the same organizational unit or to a different one.

This property can be recovered from the business processes so as to assign the responsible to those activities that require an authorization, by using an agent. Authorizing.

 

Calendar

Identifies the calendar that establishes the dates and working hours of the user.

This property can be defined for each user individually.

When the user has not a special calendar defined, then the current calendar at the level of the organizational unit to which it belongs is considered. If there is no definition of a calendar in such unit, will be sought at the higher levels of the organizational structure, until detecting the calendar to apply.

The root organizational unit of all the hierarchy has a predetermined calendar defined.

 

Job Position

 

Optionally the job positions which correspond to the users can be indicated.

 

Position

Defines the job position occupied by the user.

 

Wizards

 

Optionally the chatbots can be selected to work as wizards of the user.

 

Wizard

A user can define one or more chatbots as their wizards.

Each time the user receives a message, each of their wizards verify if they recognize that message as a command they can execute. 

Each chatbot exposes the commands they can execute and defines which participants can invoke their execution.

On the other hand, those who communicate with this user can see the commands they can use, by pressing the command icon on the chat window.

Delegations and Absences

 

Delegates

 

The list of delegated users is indicated and the period during which the delegation of tasks is valid.

When the user is inactive or absent then those current delegates can:

oDo the tasks assigned to the user.

oInitiate the processes authorized for the user.

 

Delegate of

 

Informs the user list that have delegated tasks in the user and the corresponding period.

This list is dynamic and is completed at the moment of opening the user profile.

 

Absences

 

Each element of the list indicates the type of absence and the corresponding period.

During these periods of absence the mechanisms of tasks delegation are activated.

 

Absences can be indicated considering a start and end time.

Security

 

State and Expiration

 

User State

Indicates if the user is active or not.

An inactive user cannot enter the system, as their account is deactivated.

 

Expiration Date

The user account is automatically deactivated when the date entered in this property is exceeded. This automatic deactivation does not use the tasks delegation scheme.

This mechanism is not applied when the authentication of users is not made by Deyel but it is delegated to LDAP or Google.

 

Password Expires

It allows to establish a term of validity of 30, 60 or 90 consecutive days, starting to count from the last modification made on the user data.

After that deadline, when the user logs into the portal it is required they renew their password.  It can also be stated that the password does not expire.

This mechanism is not applied when the authentication of users is not made by Deyel but it is delegated to LDAP or Google.

 

Licenses

 

Each environment of Deyel has use licenses that enable the use of licensed applications during a period of time and by a certain number of users.

In this section the list of licensed application the user can use is indicated and which type of user license they have assigned.

 

Product

Indicates the licensed application the user can use.

 

Type of License

Indicates the type of user license that is assigned to the user to use the product.

 

Permission

 

The access permits the user has assigned are listed. Each element from the list indicate the name of the permit and the application they belong to.

 

In the first positions the permits the user inherits for belonging to an organizational unit, playing a role or a job position are displayed. These elements are displayed protected and it is not possible to delete them from the list. Hovering over each of these elements, it is displayed from which object the permit is inherited.

 

Following the inherited permits, the permits assigned directly to the user are shown. When creating or modifying the user you can add or delete elements from the list.

 

First the application is chosen and then the permit of such application that you want to assign to the user.

 

When permits from a licensed application are assigned, this must be able to be used by the user. If the application is not available in the use license of the environment, the permit is seen as protected and it is possible to delete it from the permits list, but not modify the element

 

The permit "Account Manager" can only be assigned to a unique user.

In On-Premise installations of Deyel, this permit can be assigned or removed from a user by the security administrator.

In Cloud installations, you must use the site of Deyel to change the user defined as " Account Manager".

 

In every installation there exists a set of predefined permits, that can be assigned to the users.

 

Roles

 

The roles the user performs are listed. The list is dynamically conformed when accessing the user profile, recovering the roles where the user and their unit are actors. Each element indicates the role name and the application it belongs to.

In the first positions the roles the user inherits for belonging to a unit are displayed and then the roles where the user is an actor.

Personal Data

 

The user profile includes the following properties:

 

Nationality

Birth Date

Identification Type / ID Number

Phone Number / Extension

 

Addresses

 

The user can have multiple addresses, with the following properties for each of them:

 

Country

State

City

Postal Code

Street

Number

Department

 

Media

 

The user profile includes information about the identity of the user in the different social medias (Linkedin, Twitter, Facebook, YouTube y Skype).

 

Additional Data

 

Observations

Allows to load complementary data of the user.

Configuration Data

 

This section is only available for users type "Intelligent Thing".

 

 

config_img1

 

Definition

 

Visible

Determines if the chatbot is visible in the user list of the business social media Tedis.

When a chatbot is not visible, it can work as a wizard, but it is not possible to send it messages directly in a chat.

 

Thing Type

Deyel incorporates the concept of chatbot, as a type of intelligent thing.

In future versions other types of intelligent things will be supported.

 

Message Processor

The chatbot can define the business process that implements the processing of the messages it receives. Each time a chatbot receives a message, starts a case of this process to generate the corresponding answer.

 

Commands

 

This section defines the list of commands the chatbot can interpret and answer.

Executing a command implies executing the business process that implements it.

 

Participants

 

This section defines the participants that can use the chatbot as wizard.

If an organizational unit is chosen, then any user from that unit can use the chatbot.

 

WebHooks

 

Webhooks are interfaces that allow to integrate applications, that is, they allow to connect and exchange data between applications.

A chatbot can use multiple webhooks, each of them defines the URL used to contact other application, sending it data in JSON format.

When a chatbot receives a message, it forwards it to each of its webhooks.

System User

 

To make internal operations, automatically, Deyel uses a predefined user called SYSTEM USER (SYSUSER).

This user is displayed in the user list, it is not possible to modify or deactivate it and it does not require user licenses.

The initial load of the use license or its subsequent update or the execution of programmed tasks, among others, are operations whose execution is made using this user and so it remains registered in the audit trails.

It is not possible for someone to enter the user portal authenticating as the system user. Deyel uses it only for the doing and registration of internal tasks.

Send us your comment
Share on Twitter Share on Linkedin Send by Email Print