Support for multiple browser windows
Hello,
I recently came across an issue with OpManager 6 where it doesn't appear to handle multiple broswer sessions properly. Here's what happenend:
I went into the Notification Profiles page and create a new notification profile. To keep our notification profiles in a standard format I like to view an existing notification profile while I work on the new one. So I opened in a new browser tab one of the existing notification profiles. I click backwards and forwards between the tabs as I fill out the new notification profile options.
Once the new notification profile is finished I click Save. This is where the problem occurs. Rather than saving the new notification profile, it actually saves all of the changes into the exsiting profile that I had open in the second tab.
It appears that OpManager doesn't keep track of the sessions properly. We use other web-based applications here that work happily with multiple instances running.
Has this been corrected in OpManager 7? If not, is it something you are aware of and working on for a future release?
Thanks.
I recently came across an issue with OpManager 6 where it doesn't appear to handle multiple broswer sessions properly. Here's what happenend:
I went into the Notification Profiles page and create a new notification profile. To keep our notification profiles in a standard format I like to view an existing notification profile while I work on the new one. So I opened in a new browser tab one of the existing notification profiles. I click backwards and forwards between the tabs as I fill out the new notification profile options.
Once the new notification profile is finished I click Save. This is where the problem occurs. Rather than saving the new notification profile, it actually saves all of the changes into the exsiting profile that I had open in the second tab.
It appears that OpManager doesn't keep track of the sessions properly. We use other web-based applications here that work happily with multiple instances running.
Has this been corrected in OpManager 7? If not, is it something you are aware of and working on for a future release?
Thanks.