Sorry for the late post, but my team has a question we can't seem to find a solution for in the eValid documentation pages:
In the eValid architecture, can you have two copies of eValid running together (in parallel) and then have the two separate scripts talking to each other?
Any recommendations/suggestions/advice please?
Really good question...many subtleties involved in this one TheoMarc.
There's actually no way you should, or would want to, have two eValid's running from the same playback script.
At playback time, each script is opened exclusively and read into an internal format for execution.
However, there is a trick here in that when you do a CallScript then that really amounts to opening a new script, and the process repeats.
So technically Script A could invoke Script B, and it could invoke Script A and so forth.
We've done this and it gets tricky.
But it works.
The other way to look at this is to think about having one browser sync on the actions that happen in another eValid browser.
That can be done only at the desktop level by doing sync on screen images.
But that is very crude.
A better way is to use eValid's System CallWait command.
This command can call a desktop function which can wait for something to be true before return control to the eValid browser that invoked it.
Two (or more) eValid browsers thus could communicate using something in the local PC as a mediator between the two (or more) instances.
SO, yes, probably you can work this out ... but fair disclosure, this is going to be tricky to get working reliably.
-- eValid Support