Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Text File rules - Completing the Create, Save As, or Specialization form

Updated on February 7, 2022

Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.

Create a Text File rule by selecting Text File from the Technical category.

Key parts

A Text File rule has three key parts:

App Name (Directory)Enter the name of the Web server directory to place this file when it is extracts from the database. Subdirectories specific to the RuleSet and version are created to hold the extracted text file.
IdentifierEnter the name you choose for this file. Choose a name that is valid for both UNIX and Windows files. Use only lowercase letters.
File Type (extension) Enter an extension for this type of file, with no period. For example enter css for Cascading Style Sheets, js for JavaScript, or htm for (static, pure) HTML. Enter htc for Dynamic HTML (DHTML) files.

The list of Windows file types that you can enter here is defined through a standard map value named Rule-File-Text.RuleFileTextTypes. You can add to this list by overriding that rule.

Rule resolution

When searching for text file rules, the system filters candidate rules based on a requestor's RuleSet list of RuleSets and versions.

Time-qualified and circumstance-qualified rule resolution features are not available for text file rules. The class hierarchy is not relevant to rule resolution of text file rules.

About Text File rules

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us