User management forum

+4
Planned

Import groups process

Juan Francisco Babío Casal 6 months ago updated by Saray Renilla Lamas 4 months ago 4

In terms of improving the group import process in NetexCloud, I wish to flag on what happened in the pre-production environment after launching an import of 64 groups:

The summary perceived by the end user is as follows:

slow process: total time in accomplishment of all the work 55 minutes, for 64 registers... What will happen with 100?

Unreliability in what the screen says: the import was done in the cloud instantly and 62 groups were created in the LMS Pack in the first minute. The remaining 2 groups took 54 minutes to propagate.

After reviewing the process with the parties, I summarize the operation that currently follows:

- For each cloud group create the group in database and create a message in the queue to send the info to central

- A processor of the queue takes the message and generates request to central (I don't know if it makes checks before launching the creation operation)

- Central collects the request and generates the group in database.

Problem that arose in this import:

In central deadlocks are produced due to possible multiple requests for several threads from the cloud.

Proposal for improvement:

- Instead of generating X messages in a queue, it would be more logical to send all the information collected in a single message. If this fails, it will be reattempted later.

- Each platform manages the information at its own convenience, which is why it requires it to implement a web service so that it can receive the information it needs.

Comments

- Communications between platforms the fewer requests there are between them the faster the communication between them.
    Answer
    Saray Renilla Lamas 4 months ago

    ES

    Desafortunadamente este es un caso que afecta tanto a nuestro componente (Gestion de Usuarios) como a la plataforma que recibe la operación masiva.

    El caso del borrado se ha puesto en conocomiento de dicha aplicación. Conjuntamente se ha llegado a la conclusión de que se inroducirá una mejora en la funcionalidad para permitir el borrado de grupos que tengan hijos o elementos secundarios y así agilizar la operación de borrado. Esta mejora se encuentra en fase de desarrollo.

    La creación de grupos de manera masiva donde la esctructura donde el orden no sea algo imprescindible todavía no ha pasado a desarrollo ya que todavía no ha sido analizada por ambos componentes.

    En cualquier caso os mantendremos informados del progreso de ambas mejoras.

    Saludos,

    Saray

    EN

    Unfortunately, this case affects both our components (User Management) and the platform that receives the massive operation.

    The case of deletion has been brought to the attention of this application. It has been concluded that an improvement in the functionality will be introduced to allow groups deletion that have children or secondary elements and thus speed up the deletion operation. This improvement is in the development phase.

    Creation of groups in a massive way where the order/structure is not something essential has not yet passed to development since it has not yet been analyzed by both components.

    In any case we will keep you informed of the progress of both improvements.

    Regards,

    Saray

    +2
    Planned

    Deleting users

    Juan Francisco Babío Casal 5 months ago updated by Saray Renilla Lamas 4 months ago 5

    In users administration, we found the following:

    Cannot delete users inactivated in bulk process... We believe that an additional delete button that would be activated if it is detected that all of them are disabled and dissapear if there are active users in the list.

    Answer
    Saray Renilla Lamas 4 months ago

    ES

    Hola Juan,

    Tal y como comenta Paco, el planteamiento inicial fue el de limitar el número de acciones permanentes que se pueden realizar sobre una selección de varios usuarios. La intención era limitar la exposición de acciones propensas a error que realiza una administrador desde el menú de usuarios, y forzar estos procesos masivos (o grupal) por otros mecanismos.

    Sin embargo, concido con Patricia que la lógica puede ser mejorada y así minimizar acciones no deseadas simplemente habilitando la opción de borrado única y exclusivamente si se cumplen ciertas condiciones.

    Muchas gracias por esta propuesta de mejora!

    Os iremos manteniendo al tanto de su desarrollo e implementación.

    Saludos,

    Saray

    EN

    Hello Juan,

    As Paco says, the initial approach was to limit the number of permanent actions that can be carried out on a selection of several users. The intention was to limit the exposure of error-prone actions performed by an administrator from the user menu, and to force these massive (or group) processes by other mechanisms.

    However, I agree with Patricia that logic can be improved and thus minimize unwanted actions by simply enabling the delete option only and exclusively if certain conditions are met.

    Thank you very much for this improvement proposal!

    We will keep you updated on its development and implementation.

    Regards,

    Saray

    +2
    Started

    Modificación de la estructura jerárquica de grupos

    Juan Francisco Babío Casal 5 months ago updated by Francisco López (Team Leader) 4 months ago 1

    Debido a que los clientes reflejan la estructura de grupos con su estructura organizativa, se está viendo una problemática que conviene solventar lo antes posible, que se trata de poder modificar esa estructura sin tener que hacer borrados masivos de grupos.

    En la actualidad por el front, el usuario una vez creado un grupo, no puede modificar el "padre", elaborando y creando progresivamente la estructura que necesite. Esto se ve claramente con un ejemplo:

    Teniendo como estructura original:

    • Producto play
    • Producto cloud
    • Producto central
    • Producto maker

    La estructura que se quiere obtener es la siguiente sin mover a ningún usuario de ningún grupo:

    • Producto Netex
      • Producto play
      • Producto cloud
      • Producto central
      • Producto maker

    En la actualidad esto no se puede realizar ni por front, ni por servicios web, sin borrar el grupo con todas las asignaciones de los usuarios y volviendo a crearlos, pudiendo afectar en las demás patas del producto debido a vinculaciones con cursos, sprints o lo que haya vinculado por detrás.

    +1
    Excluded

    Change the sender of email notifications

    Dori Martinez Ramirez (aecc SE 2 months ago updated by Saray Renilla Lamas 2 weeks ago 3

    Hello;

    We would like to propose as an idea of improvement the ability to change the sender of the mail when sending notifications to users because by default appears "From: LearningCloud We suggest that the sender can be modified or that corresponds to the key name of the instance.

    Greetings.

    +1
    Started

    Automatically unassign users from groups

    Videoarts 4 months ago updated by Logicearth Support 3 weeks ago 4

    In NetexCloud, currently you can enrol users to groups by using assignment rules, but if someone's parameters change and the rules no longer apply to them then they are not automatically taken out of the group.

    For example, if you have a Manager group based on Job Title = Manager rule and a user is changed from a Manager to another job role then they should not be in the Manager group any more.

    0
    Started

    groupadmin misses search function

    The Courseware Company (NL) 3 weeks ago updated by Francisco López (Team Leader) 3 days ago 1

    Hi there,

    the groupadmins on the netexCloud side do not have a search bar in the users tab. Also they can not see the users per group.

    Could you please adjust this?

    0
    Excluded

    Increase expiration time for "welcome mail" in netexCloud

    Ricardo Emanuel Devai 2 months ago updated 1 month ago 5

    Hi, there

    Currently, the standard expiration time for welcome emails is 24 hours. Is it possible to extend it for 5 days? It would be of a great help and would avoid users contacting the HR Department asking for help. I think 24 hours is such a short period in case a user is travelling, out of the office, too busy. Also, I understand that the welcome email is not really sensitive information, thus a longer period would not represent a risk, in my opinion. Thank you! 

    As a tip for administrators, you can re-send the welcome email from the user page or you can tell the user to click on "Can´t access my account" and the system will send a new email to the user. 

    Answer
    Saray Renilla Lamas 2 months ago

    EN

    Hello Ricardo,

    The changing this configuration is possible. However, customizing its value for a specific client is only possible if the client has a dedicated installation of NetexCloud. If not, this parameter will be unique for all tenants under the same instance.

    Nevertheless, as you mentioned, the welcome process can be easily retrigger from the administration panel or by the user itself at anytime.

    Regards,

    Saray

    ES

    Hola Ricardo,

    El cambio de esta configuración es posible. Sin embargo, la personalización de su valor para un cliente específico sólo es posible si el cliente tiene una instalación dedicada de NetexCloud. Si no, este parámetro será único para todos los inquilinos bajo la misma instancia.

    Sin embargo, como has mencionado, el proceso de bienvenida puede ser fácilmente relanzado desde el panel de administración o por el propio usuario en cualquier momento.

    Saludos,

    Saray


    0
    Answered

    Types of fields in Extensible Field Creation

    Ricardo Devai 2 months ago updated by Ricardo Emanuel Devai 2 months ago 2

    Hello,

    When I access netexCloud > Configuration > Advanced Settings > Extended Fields > + Create field

    In the Type menu, I find the following options:

    Text - how many characters can I use in a text field?

    Integer - are they integers here? Are they separated by commas?

    List of values - What values can I insert here? Are they separated by commas or is it a value per field?

    And if I want an alphanumeric field with no character limit, which option should I use?


    Answer
    Saray Renilla Lamas 2 months ago

    ES

    Hola Ricardo,


    Respondiendo a tus dudas sobre los tipos de campos extensibles:

    • Text - ¿cuántos caracteres me permite en un campo de texto? <El límite serían 255 caracteres>
    • Integer - ¿aquí son números enteros? ¿Se separan por comas? <Sí, sólo se pueden introducir números enteros>
    • List of values - ¿Qué valores puedo insertar aquí? ¿Se separan por comas o es un valor por campo? <Puedes introducir cualquier tipo de "string" e incluso caracteres especiales. Al crear este tipo de campos verás que para añadir un nuevo valor simplemente escribes el valor deseado y le das al botón añadir (+), acto seguido te aparecerá la opción de añadir otro nuevo posible valor, y así hasta que la lista esté completa y quieras guardar>

    Los valores admitidos tienen un límite de 255 caracteres (alfanuméricos) por lo que no hay posibilidad de crear un campo alfanumérico sin límite de caracteres. Si dicho límite es admisible, sería recomendable usar el tipo text.

    Saludos,

    /Saray

    EN

    Hello, Ricardo,


    Answering your questions about the types of extensible fields:

    • Text - how many characters can I use in a text field? The limit would be 255 characters
    • Integer - Are they integers here? Are they separated by commas? Yes, only integers can be entered
    • List of values - What values can I insert here? Are they separated by commas or is it a value per field?  You can enter any type of string and even special characters. When you create this type of fields you will see that to add a new value you simply type the desired value and click on the add button (+), then you will have the option to add another possible new value, and so on until the list is complete and you want to save.


    Supported values have a limit of 255 characters (alphanumeric) so there is no way to create an alphanumeric field without a character limit. If this limit is admissible, it would be advisable to use the text type.

    Regards

    0
    Excluded

    Creating new users (username must be a single data that is not repeated)

    sparral 3 months ago updated by Saray Renilla Lamas 2 months ago 2

    Good morning.

    I'm going to raise this query with an example, see if anyone can give me an idea/solution.

    I have María Pérez Fernández (username mperezf)who has been a user of the platform for two years.

    It joins the company Martina Pérez Flores, along with 49 other people, and, therefore, I prepare a csv with the data of the 50 new users. The username for Martina is mperezf.

    Result: after uploading the csv with the data of the new users, the user of Martina Pérez Flores will NOT have been created and the user of María Pérez Fernández will have become the data (name, surname and all others) of Martina Pérez Florez.

    The problem is the matching username. Logically the username has to be a unique data, which is not repeated. But, you shouldn't skip a warning message like "The mperezf user already exists, your data will be modified, are you sure you want to continue?"

    Is there a quick way to verify that in the csv there is no username that is identical to that of another user already existing on the platform? I can only automate it, in a way, as follows: export all users already created on the platform to an Excel, add the new ones and search for duplicates. But I still find it a task that consumes an exaggerated time.

    Are there any rules that 100% guarantee that a username has not been created before?

    We see that the functionality of creating users using csv is very limited, because it only works when the username does not co-indice with any other. If it matches, the information is always overwritten. Also, this happens without you being aware of what's going to happen, because at no point do you get a warning message about what's going to happen (it can take quite a while before you realize the error):

    If you checked the S option in the csv, all the data you've put in the csv, including empty data, is overwritten. That is, all the data in the username row will be assigned to the previously existing user and if there is any empty field in the csv, it will also be flushed to the previously existing user.

    If in the csv you have checked the option M, do not force the data, so if there is an empty field in Excel, the one that already existed will be respected, but all those listed in the Excel will be assigned to the existing user previously.

    Couldn't there be, for example, a "create" C operation, in which data is never overwritten and warned in the event that you try to create a new user with an existing username?

    My idea of improvement is that some procedure is enabled to generate new users (not to modify existing ones) by uploading a csv, ensuring that the data of an existing user will not be overwritten.

    Answer
    Saray Renilla Lamas 2 months ago

    ES

    Buenas tardes,


    Actualmente el tipo de operaciones masivas soportadas por el producto no incluye un "crear" (C) como tal por lo que en este caso concreto la plataforma siempre considera que la información indicada en el CSV es la correcta a sobreescribir y/o mantener y/o borrar. Bien es cierto nada limita que se puedan introducir nuevos usuarios dentro de la plataforma con las operaciones existentes.

    La solución sería, como bien se indica en el ticket, sería una nueva funcionalidad dentro las operaciones masivas soportadas, y que se soporte la opción de "crear usuarios" (C) o similar. En este tipo de operaciones ante el caso mencionado se debería lanzar un error de que el usuario ya existe, tal y como ya se está realizando cuando se crea un usuario mediante los mecanismos de creación de usuarios (por ejemplo, a través de pantalla). 

    Gracias por la sugerencia!

    Saludos,

    /Saray

    EN

    Good afternoon,


    Currently the type of massive operations supported by the product does not include a "create" (C) as such so in this particular case the platform always considers that the information indicated in the CSV is correct to overwrite and / or maintain and / or delete. It is true that nothing limits that new users can be introduced into the platform with the existing operations.

    The solution would be, as it is well indicated in the ticket, it would be a new functionality within the supported massive operations, and that the option to "create users" (C) or similar is supported. In this type of operations before the mentioned case an error should be launched that the user already exists, as it is already being done when creating a user by means of user creation mechanisms (for example, through the screen).

    Thanks for the suggestion!

    Regards,


    0
    Started

    Multiple filters do not work

    Videoarts 5 months ago updated by Saray Renilla Lamas 1 month ago 5

    Afternoon,

    In the users area I have just tried to use a filter which would select individual users whom are members of two specific groups. However the results gave me all users in both groups including those who are a member of only one of the groups I filtered for which isn't the result I want. The filter is essentially using 'OR' instead of 'And' as I would expect.

    Also it doesn't seem that you can export the filtered results.

    Can these two pieces of functionality be improved as described?

    Best Regards

    Will