AS4.12 to AS6.5 Migration - Issue with MpUserX

Ask Questions HMI & Visualization
, , , , ,
1

Dear all,

I am facing an issue during migration of project backup from AS4.12 to AS6.5 with MpUserX.
With AS4.12 - I can observe the names of all the configured user from the user list with the help of MpUserXMgrUI.
Similarly, I have converted same project backup in AS6.5 without any logical changes. but I am not able to see the names of configured users in userlist untill I manually login with Admin rights user.

Versions:
Mappview - 6.5.0
MappServices - 6.5.1
AR Version - 6.3.4

I want to know if we need to configure this thing from the configurations which was not the case earlier or something else?
Thanks in advance

Regards

2

If you are using the built in “UserList” widget of mappView the user needs to have the “BR_Engineer” role for the widget to work.

A user with BR system role “BR_Engineer” must be logged in so the widget can be used at runtime. Role “BR_SecurityAdmin” is required in order to add a new user.

Automation Help: mapp UserX Binding to mapp View

3

Thanks for the update!

I am using MpUserXManagerUI Function Block and UIConnect for the task. Now In current case I am not able to see the list of configured user in this function block when admin is not logged in. If I log in with the user having admin rights manually, I get the list of configured user in this case.

When logged in with user not having admin rights

image
image550×595 8.32 KB

when logged in with user having admin rights

image
image552×445 6.59 KB

4

to the best of my knowledge this has changed in AS6, so your findings is correct.

5

Thanks for the clarity!
Actually, I want to ask that most of our customers are using this UI list for logging in at an initial level. Since the list won’t be visible without admin rights in AS6, what shall be the workaround for the same to get this functionality into running?

6

you have to provide user with admin rights, log in, export, log out. how you do that is up to you and your application. Or as alternative solution I think can be used libary ArUser.

In mappFramework 6 we solved it in way, that there will be dedicated user with admin rights created only for this, hardcoded in task logic and we will document this. It is not nice solution, but functional.