Is there any further guidance available on features/limitations of the embedded browser in DeltaV Live?
We'd like to embed the Aspen DMC3 PCWS client in a DeltaV Live graphic but can't make it work. After a few attempts we seem to have the $UrlWhiteList sorted, but now the browser content is blank in runtime with no error message.
BOL states that "The web browser element cannot be used to browse to most DeltaV web-based complementary products, such as DeltaV Logbooks, Syncade MES, DeltaV Batch Analytics, or DeltaV Mobile Portal" but doesn't explain why. Could it be that redirections and/or parameters aren't supported?
Running DeltaV v14.FP2,DeltaV_14FP2_WS_03_CSS (Build 7944).
Andre Dicaire
Thanks for the responses Andre Dicaire and Matt Stoner .
For anyone else attempting this in future, it looks like the old Aspen interface (http://webserver/atcontrol) is not compatible with the embedded browser object in DV Live v14, but the newer Aspen interface (http://webserver/aspenapc) is compatible.
Our system is ~8,000 modules and 20+ years old, recently upgraded to v14, so we'd like to avoid another DV version upgrade for a few years :) Initial impression is that the required functionality is available in the new Aspen interface so we should be OK to migrate users as part of the DeltaV Live migration.
We have an Emerson project team working on the graphics migration in a simulation environment (including new L1/L2 displays expertly designed by Christi Mezzic ) but I've been investigating the Aspen interface on the online system where I can access the web server.