Alarm list based on user login

Find and share HowTos to various installations / configurations!
Search

Post Reply
4 posts • Page 1 of 1
AMRPatricio
Posts: 53
Joined: Mon Dec 12, 2016 3:43 pm

Alarm list based on user login

Post by AMRPatricio » Wed Feb 05, 2020 4:29 pm

Hi all,
I need some advice/suggestions on the following: I want the content displayed in the alarm list to be user dependent (areas of responsibility). The idea is to have a dpGroup per “user profile”, which contains the “DPs”/alarms that the logged user can see and address. Of course, there is few different ways to achieve this, as example:

1. Create a dp of AEScreen and AESProperties (configured with the proper dpGroup) for each user profile. When the user login the correct AEScreen shall be open.
2. Have a generic config for AEScreen and AESProperties. After the user login, the correct dpGroup is applied “on fly” via the temporary AESProperties dp.
3. ….??

Which one is the best approach?
Thanks in advance :D ,
Antonio Patricio

User avatar
leoknipp
Posts: 2205
Joined: Tue Aug 24, 2010 5:28 pm

Re: Alarm list based on user login

Post by leoknipp » Fri Feb 07, 2020 7:41 am

The easiest solution you have mentioned in point 1 - creating a pre defined configuration with the correct filter settings for every dpGroup.
If you are modifying the runtime datapoints you have to know the exact order of steps to get the correct result.

Best Regards
Leopold Knipp
Senior Support Specialist

AMRPatricio
Posts: 53
Joined: Mon Dec 12, 2016 3:43 pm

Re: Alarm list based on user login

Post by AMRPatricio » Wed Feb 12, 2020 9:40 am

Hi Leopold,
Thanks for your response.

I do understand what you said. The problem of the approach no. 1 is the fact that it requires (in my case) 3x configs of each type for each user(profile): AEScreen (Alerts, events, alertRow), AESProperties (Alerts, events, alertRow). Any small change, e.g , adding a new alarm attribute/column will need to be done to all the (AESProperties) configs.

Regarding the option no. 2. I am assuming I can perform the following steps: openAES(in AES_ACTION_INTERACT” mode ),aes_doStop(dp), apply group, aes_doStart(dp). As the temporary dp is overwritten with the “global”/generic properties at the moment the aescreen is open, I guess I need to wait until the initialization is completed and then only after that I can apply my “code”/group.

It there anything wrong on my thoughts?

BR,
Antonio Patricio

User avatar
leoknipp
Posts: 2205
Joined: Tue Aug 24, 2010 5:28 pm

Re: Alarm list based on user login

Post by leoknipp » Wed Feb 19, 2020 5:16 pm

When using openAES() with AES_ACTION_INTERACT the AEScreen is in stopped mode as far as I know.
Therefore it will not be necessary to stop the AEScreen.

If you want to switch the configuration during runtime you have a look at the scripts for the combo box and the "play" button in the panel vision/aes/AEScreenRegBoth.pnl.

I'm not sure if you really need such a high number of configurations.
When you are using the same filter configuration for all users and change the pre defined filter configuration before starting the screen it will possibly work. If a filter configuration is already loaded and the information is written to the runtime datapoint a change of the filter configuration does not affect the runtime configuration.

Best Regards
Leopold Knipp
Senior Support Specialist

Post Reply
4 posts • Page 1 of 1