More about Text
File rules
|
|
Text file rules are one form of static content — rules that do not depend on clipboard values. When you save or check in a text form rule, Process Commander deletes any previous file on the Web server based on that name, directory, RuleSet, and version. The directory path and file names are based on a hash code derived from RuleSet version lists.
You can override some standard text file rules to change the appearance of your application user interface. If this is necessary, you can determine which text file rules you need to override by reviewing the output HTML of your application's harness forms.
Use the Rules Inspector tool to study the structure of harness forms, sections, and the HTML rules they reference.
If you copy a Skin rule using the Save As toolbar operation, three text file rules (identified on the Styles tab for Desktop, Work and Report) are also copied.
When you use the Save As toolbar operation to copy a text file rule that contains CSS styles into a different RuleSet, a warning appears if the CSS text references images (that is, binary file rules) that are not available to you. Note the names of these images and copy or create them into your application RuleSet.
When a requestor first references a text file rule, Process Commander extracts the image file (or other binary file) as static content into an appropriate Web server directory on the server. It determines the destination directory from the rule key and a hash code derived from the requestor's RuleSet list.
Your Internet Explorer
browser has a workstation cache of recently received files.
When testing updated or overridden text files for JavaScripts
and CSS files, clear your Internet Explorer browser cache
(Tools > Internet Options > Temporary Internet Files
> Delete Files) to see the effect of some newly
exported text files.
Select Delete all Offline Content to ensure that older versions of JavaScript files are also purged from the Internet Explorer cache.
If the change is to affect many users, asking them to each
clear their local cache may not be practical. By default, HTTP
headers mark static elements to be cached for 24 hours, so
users will receive the newer files a day later. If this is not
satisfactory, you can set the
defaultcachingtimeout element in the
prconfig.xml file to a value lower than the
default of 86,400 seconds (24 hours). For example:
<env name="http/defaultcachingtimeout" value="6000" />
A lower value causes more HTTP traffic and so can adversely affect response time.
If authorized, you can use the System Management application to delete all extracted static files from the HTTP server directory structure (on a specified node), forcing them to be extracted again on demand.
