User management forum

+4
Excluded

Welcome email links

Fátima García 6 months ago updated by Francisco López (Team Leader) 3 months ago 7

Hello, 

netexCloud welcome emails are a bit confusing at the moment for customers using learningCloud. The links to download the mobile app takes you to learningCloud mobile, but not learningCloud New Generation. 

I suggest adding an additional link to the second app. If it isn't possible, it will be better to have only the learningCloud New Generation link. If we are moving away from the LMS, I think it makes more sense.

Please, can you review?

Regards.

Fátima

Answer

EN

Hello Fátima and Richard, 

Support had a meeting today with netexCloud Product Owner and told us this improvement it's been taken in consideration long time ago (almost a year ago it was suggested by Video Arts). Unfortunately it's been part of our roadmap  backlog since them and won't be implemented during next year. 

We are sorry but we have to prioritize our limited resources depending on the impact.

The improvement is excluded.

Regards

ES

Hola Fátima y Richard, 

Soporte tuvo una reunión hoy con la encargada del producto netexCloud y nos dijo que esta mejora ha sido tomada en consideración hace mucho tiempo (hace casi un año fue sugerida por Video Arts). Por desgracia, ha sido parte de nuestra hoja de ruta desde entonces y no se implementará durante el próximo año.

Lo sentimos pero tenemos que priorizar nuestros limitados recursos dependiendo del impacto .
La mejora está excluida.
Saludos 

+4
Excluded

Import groups process

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

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

    Hola JuanFran,

    Nuestro PO dijo:

    Independientemente de si es una incidencia o no, esta funcionalidad se habilitó de manera unilateral en un producto y no en el resto a petición expresa de un cliente. Este tema tiene que compartirse con el resto de productos: NetexCloud, LearningCLoud  etc etc. Dado que como cloud Propaga! información de grupos al resto de plataformas cualquier cambio en el producto NetexCloud ha de ser validado por ellos.
    Desde producto se recomienda o se pide encarecidamente que la gestión de usuarios se realice desde el módulo pensado para ello: NetexCloud y se usen las cartera de funcionalidades ofrecida por ese mismo producto y no otros que operan en standalone mode.
    NetexCloud ha linkeado la tarea para analizar y ofrecer una solución a esta problemática con central, sin embargo, NetexCloud no puede habilitar esta opción a la ligera sin que el resto de plataformas afectadas haga los cambios pertinentes o evalúen su incorporación a roadmap.

    Saludos,
    /Saray

    Gracias por compartir tus inquietudes.

    Saludos

    +3
    Excluded

    Prevent users who are generated by default on instances from being disabled and deleted

    Samantha Vázquez Fustes (Escalation specialist) 7 months ago updated by Saray Renilla Lamas 3 months ago 2

    Hello

    We request that it be considered as an improvement proposal to prevent users who are generated by default on instances from being disabled and deleted, even if they are included in CSV imports. We refer to the testadmin and testuser users of the instances.

    Thank you very much, a greeting.

    Samantha Vazquez

    Netex Support

    Answer

    ES

    Hola Samantha

    Esta propuesta de cambio o mejora es muy interesante. Si bien, desde producto se considera que sería al menos sólo necesario para el caso de la cuenta de soporte (que sería desde la cual se haría login-as). El resto de usuarios generados por defecto para permitir el alta y pruebas iniciales de la plataforma antes de pasársela al cliente no tendría porqué estar restringido o correspondería al cliente decidirlo.

    Sin embargo, esta propuesta no puede ser ejecutada en el medio plazo. Nuestras prioridades están ya alineadas con otras mejoras solicitadas para el corto/medio plazo así cambios sustanciales de la aplicación y su arquitectura.

    Gracias por esta propuesta! Esperamos poder retomarla o bien que sea sustituida por una funcionalidad de login-as.

    Saludos,

    /Saray

    EN


    Hi, Samantha.

    This proposal for change or improvement is very interesting. Although, from product it is considered that it would be at least only necessary for the case of the support account (that would be from which would be made login-as). The rest of the users generated by default to allow the registration and initial testing of the platform before passing it to the customer would not have to be restricted or it would be up to the customer to decide.

    However, this proposal cannot be executed in the medium term. Our priorities are already aligned with other improvements requested for the short/medium term so substantial changes to the application and its architecture.

    Thank you for this proposal! We hope to take it up again or to replace it with a login-as feature.

    Regards,

    /Saray

    +3
    Excluded

    [admin] login-as option

    The Courseware Company (NL) 9 months ago updated by Francisco López (Team Leader) 8 months ago 2

    Hi there,

    We miss the option as admins to login as a different user, mostly the user that has troubles in the system.

    Thanks,

    Irma

    Answer

    EN

    Hi Irma,

    Our Product Owner was checking this requirement, and she explained to us this depends on our CAS to be compatible with login as. This compatibility is in our roadmap for Q4 2020 (it could be rescheduled) so will be rejected until this compatibility exists.

    Sorry for any inconvenience.

    Regards. 

    ES

    Hola Irma,
    Nuestra Responsable de Producto estaba comprobando este requisito, y nos explicó que esto depende de que nuestro CAS sea compatible con el inicio de sesión. Esta compatibilidad está en nuestra hoja de ruta para el cuarto trimestre de 2020 (podría ser reprogramada), por lo que será rechazada hasta que exista esta compatibilidad.

    Disculpe las molestias.

    Saludos.

    +2
    Accepted

    Real-time synchronization

    The Courseware Company (NL) 9 months ago updated 3 months ago 15

    I would like to add this improvement proposal: 

    For excisting users placing them in a new group it works realtime, the trouble is with newly made user. This is really a big issue, because lots of users are in a face to face training when they are added in the environment, so they need the access right away.

    Thanks!

    Answer

    EN

    Dear customers and partners,


    Today we have concluded a meeting with our products and everyone has accepted this improvement as an objective to achieve for next year's roadmap.

    This is why it is accepted, they are already doing actions that will be notified in our newsletters and in the info of the releases of our products.

    We sincerely regret the inconvenience caused, but we are working already on this goal.

    As always, we appreciate all your cooperation in the process.

    Kindly

    Netex Support

    ES

    Estimados clientes y colaboradores,

    Hoy hemos concluido una reunión con nuestros productos y todos han aceptado esta mejora como objetivo a conseguir para el roadmap del próximo año.

    Es por esto que queda aceptada, en estos momentos ya se están realizando acciones que serán notificadas en nuestros boletines de noticias y en la info de la releases de nuestros productos.

    Lamentamos sinceramente las molestias causadas, pero ya estamos "manos a la obra" para lograr este objetivo.

    Como siempre, agradecemos toda su colaboración en el proceso.

    Amablemente

    Soporte de Netex

    +2
    Excluded

    Deleting users

    Juan Francisco Babío Casal 1 year ago updated by Francisco López (Team Leader) 8 months ago 6

    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

    ES

    Hola, 

    Nuestra Responsable de producto nos ha comunicado respecto a esta mejora:

    "Por el momento desde producto nuestra estrategia seguirá siendo fomentar las operaciones masivas o bien por CSV o por nuestro servicios web. Así que realizar operaciones masivas por pantalla queda descartado dentro de nuestro roadmap."

    Por eso, esta mejor queda excluida del roadmap.

    Saludos

    EN

    Hello,
    Our Product Manager has informed us of this improvement:



    "For the time being, from the product point of view, our strategy will continue to be to encourage massive operations either by CSV or by our web services. So mass operations on the screen is discarded within our roadmap."

    Therefore, this better is excluded from the roadmap.
    Regards

    +2
    Excluded

    Modificación de la estructura jerárquica de grupos

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

    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.

    Answer

    ES

    Hola JuanFran,

    Tras las respuestas de nuestros responsables de producto (Josman y Saray, ya que Negreira no se ve afectado por esta situación) hemos de informarte que se ha decidido que no se podrá implementar nada a corto y medio plazo.

    Esperamos mas suerte para el año que viene.

    Saludos.

    Soporte Netex

    EN

    Hi, Juan Fran,
    After the answers from our product owners (Josman and Saray, since Negreira is not affected by this situation) we have to inform you that it has been decided that nothing can be implemented in the short and medium term.
    We hope for better luck next year.
    Greetings.

    Netex Support

    +1
    Excluded

    Hide apps of the homepage.

    Alain Artola Yllescas 5 months ago updated by Francisco López (Team Leader) 4 months ago 2

    Hi,

    We would like to be able to hide apps of the home screen, for example, library and record so they are not visible to a user.


    Regards

    Answer

    ES

    Hola Alain, 

    Ya recibimos respuesta de nuestro departamento de producto, nuestros compañeros informaron que la visibilidad de las aplicaciones que componen nuestras plataformas se realiza a nivel de cada módulo. Central dispone de todas estas y se configuran a nivel instancia, es decir, para todos los clientes:

    A corto y medio plazo no está previsto que se pueda cambiar la visibilidad de estas aplicaciones de la plataforma, ni tampoco que central se pueda gestionar con mayor granularidad y por cliente o tenant.

    Lamentamos que esto perjudique a tu desempeño con nuestros productos, pero por ahora (en el próximo año mínimo) no podemos afrontar este desarrollo, por eso ha sido rechazado. 

    Agradecemos que nos compartas tus inquietudes y seguro que habrá más suerte la próxima vez.

    Un Saludo

    Soporte Netex.

    EN

    Hi, Alain,
    We already received a response from our product department, our colleagues reported that the visibility of the applications that make up our platforms is done at the level of each module. Central has all of these and they are configured at the instance level, that is, for all customers:



    In the short and medium term, it is not foreseen that the visibility of these platform applications can be changed, nor that central can be managed with greater granularity and by customer or tenant.

    We regret that this will affect your performance with our products, but for now (in the next year at least) we cannot afford this development, so it has been rejected. 

    We appreciate your feedback and I'm sure we'll have better luck next time.

    Regards
    Netex support.

    +1
    Excluded

    Change the sender of email notifications

    Dori Martinez Ramirez (aecc SE 11 months ago updated by Saray Renilla Lamas 9 months 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
    Excluded

    Automatically unassign users from groups

    Videoarts 1 year ago updated by Francisco López (Team Leader) 7 months ago 5

    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.

    Answer

    EN

    Hello, 

    Our Product Owner answerer regarding this improvement:

    Although we find them very interesting. Due to the performance problems generated by the current logic of the allocation rules we are not going to undertake any new type of development in this area.

    In the future, we will work on the concept of "self-managed groups" where assignment rules will add or remove users who comply or fail to comply with such rules. However, this development is not in our nearest roadmap for the reasons stated above.

    Regards,
    /Saray

    The improvement remains excluded from our roadmap, sorry for any inconvenience.

    ES

    Hola

    Nuestra responsable de producto respondió acerca de esta mejora:

    Pese a que nos parece muy interesante. Debido a los problemas de rendimiento generado por la actual lógica de las reglas de asignación no vamos a acometer ningún nuevo tipo de desarrollo en este área.
    En el futuro, trabajaremos en el concepto de "grupos autogestionados" donde las reglas de asignación añadirán o quitaran usuarios que cumplan o dejen de cumplir tales reglas. Sin embargo, este desarrollo no está en nuestro roadmap más próximo por los motivos expuestos anteriormente.

    Saludos,
    /Saray

    El improvement permanecerá excluido del roadmap, sentimos las molestias.