I’m currently working with the mappview and utilizing the mpuserx function block for user login. While it offers many great features and is quite mature, I’ve encountered an issue with the built-in login control.
The Problem
The login control provided by mpuserx has a major limitation:
Lack of customization options for the size, positioning of buttons, text, and input fields.
This makes it challenging to make the login screen look coherent and aligned with the rest of my application’s UI. The inability to adjust these elements means I can’t tailor the control to fit the design aesthetics or functionality that I need.
My Question
Is there any way to customize the login control or to have more flexibility with the sizes, positions, and layout of the buttons, text, and input fields within mappview?
Alternatively, are there any suggestions or workarounds where I can replace or extend the functionality of the mpuserx login control with something more customizable?
Any Help is Appreciated!
Thank you in advance for your time!
I’m not a mappView expert, so I hope that my reply doesn’t point into the wrong direction as I haven’t used the following information on my own by now.
But in my understanding the’re 2 different possibilities:
using the suitable client action together with standard widgets like text input and button to login a user
using the Widget Development Toolchain (WDTC) to build your own widget for login widget
I personally recommend option 1., as for option 2. you need access to WDTC, additional licenses, deep skills in Javascript development and so on. WDTC is not delivered with Automation Studio → you have to contact you local B&R subsidiary. For details, please see following post and the linked infos there: 1. WDTC - Introduction/Guidelines/Support
For option 1., you have to decide if you want to have a system-wide login (user is logged in at all clients) or a session login (user is logged in at one specific client).
Please see the following documentation:
I assume you refer to the Login-Widget?
The Login-Widget is only a combination of other widgets to provide a quick and easy login interface … if this “out of the box” solution does not meet your requirements, you can check out LoginButton-Widget, Password-Widget and LoginInfo-Widget. (Please notice, there is not “username widget”, as this is just a standard TextInput Widget!).
With these widget you can create your own login experience as needed.
I wanted to share my experience regarding the UserList widget dialog sizing issue, as I encountered a similar challenge recently.
In my case, the MappView HMI was designed with a large resolution (high width and height in pixels). The dialogs for adding/editing/deleting users in the UserList widget were generated dynamically (not sure if this is still the case in newer versions). Unfortunately, the default dialog size was too small for my HMI layout, making it unusable as-is.
To resolve this, I had to use WDTC to manually adjust the hardcoded size and position values of the widgets within these dialogs in a cusotm widget. While this worked as a workaround, it wasn’t ideal.
Since the root cause was my initial HMI dimension choices, I didn’t escalate the issue to support. However, it would be a great improvement to have more customization options for such cases—perhaps allowing users to pass a custom dialog template to the UserList widget (with predefined widget names/types, of course).
Just sharing in case others run into similar constraints!
I’m not 100% sure that I understand your problem - you seem to mix up things.
First I understand, you are using mapp View / Services 5.x … in these versions mapp View’s Authentication Mode only decides, weather mapp View uses RBAC (default) or MpUserX as Authentication Instance. But this is completely transparent to the login functions (Login, LoginButton, Password, …) - they are intended to behave the same (if not, it would be a bug!).
Second, you are referring to the UserList widget - this widget is completely independent of the Authentication Mode. The UserList widget is only the front end component for MpUserX (similar to AuditList - which is the front end for MpAudit). The UserList does not influence the authentication, it only gives you an interface to maintain users.
I understand now. It seems that after I changed the Authentication Mode to UserX in the config, the LoginButton and Password Widget are not working. Could this be a bug?
I’m not sure what’s causing this, and I’m wondering if anyone else has encountered this issue.
Additionally, when I set the Authentication Mode, the widgets work, but the UserList Widget doesn’t display the user list.
I’m not sure if this is also a bug.
Could you help me test the related functionality on mappservice and mappview 5.24?
I’m almost 100% sure that this is not a bug of MapView/Map Services, it is more related to misconfiguration or something similar. As @hobi suggested, local B&R office support can help you, because you can provide them a project. Here in Community we can not do that. Topic is closed for now, please update us with your findings
The Problem
My Question
Any Help is Appreciated!
