To jump from a WLD page to the first page of an EWD application, create a link in the WLD page to the special WLD/EWD bridge page (ewd.asp). For example:
<a href="ewd.asp&ewdApp=myNewStuff&ewdPage=begin&ewdTechnology=wl&xxx=123&yyy=hello"> New EWD Stuff </a>
A number of name/value pairs must be added to the ewd.asp:
Note: The name/value pairs are separated from the page name (ewd.asp) by a & character rather than a ? character. This is a standard WLD convention.
Also note that the additional name/value pairs are automatically copied to the EWD Session where they are added to the wld session object. In the example above they would be instantiated as:
wld.xxx = "123" wld.yyy = "hello"
The ewd.asp page is included in the EWD download Zip file and should be copied to the same path as the source pages of the WLD application. It must be compiled using ^%wldcomp in the standard WLD way.
Sometimes it is more desirable to jump to the EWD application via a server-side redirection. This can be achieved within the pre-page script of the old WLD page to which you would have previously been using. Any additional name/value pairs can be passed from the WLD application to the EWD application via a special reserved local array named %wldewdnvp. Here's an example of a jump to an EWD application:
<script language=Cache> //type=pre-page s %wldewdnvp("name1")="hello" s %wldewdnvp("name2")="there!" s ewdApp="myNewStuff" s ewdPage="begin" s ewdTechnology="wl" s JUMP="ewd" QUIT </script>
In this example, the pre-page script will force a redirection to the ewd.asp page, which, in turn, will jump the user to the page begin.ewd in the EWD application named myNewStuff. Two additional name/value pairs (name1 and name2) are also passed to the EWD application. These latter name/value pairs are automatically copied by EWD directly to the EWD Session. In this mode they are not added to the wld EWD Session Object. In the example above they would be instantiated into the EWD session as:
name1 = "hello" name2 = "there"