41 lines
1.1 KiB
HTML
41 lines
1.1 KiB
HTML
|
<html>
|
||
|
|
<head>
|
||
|
|
<link rel="stylesheet" type="text/css" href="..\styles.css">
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<img src="..\..\da.png" alt="" align="right">
|
||
|
|
|
||
|
|
<!-------------------------------------------------------------------------->
|
||
|
|
|
||
|
|
<p class="h1">
|
||
|
|
<span>BusinessRulesScripts</span>
|
||
|
|
</p>
|
||
|
|
|
||
|
|
|
||
|
|
<h2>Purpose</h2>
|
||
|
|
<p>
|
||
|
|
This example demonstrates how client side scripts can be <b>modified on the server</b>
|
||
|
|
and then <b>downloaded to the client</b> via a simple call.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
When you compile and launch the server, it displays a memo containing various client
|
||
|
|
side rules executed within event handlers such as BeforePost.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
You can test it by compiling and launching the client. Try deleting an
|
||
|
|
item with a <b>gain > 90</b>, for example.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
Next modify the server memo and click <b>Refresh Scripts from Server</b>
|
||
|
|
to see that your change has been actioned.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
Note how the strong typing allows simple reference to field names, thus
|
||
|
|
making script changes as simple as possible.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
|
||
|
|
<!-------------------------------------------------------------------------->
|
||
|
|
</body>
|
||
|
|
</html>
|