Release Notes
Redix AnyToAny XML GUI Mapper
Version 6.2.0
Version 6.1.0
Version 6.0.0
Version 5.8.0
Version
5.7.0
Version
5.5.0
Version
5.4.0
Version 5.3.0
Version 5.1.0
Version
5.0
Version 4.9.0
Version
4.8.0
Version
4.7.0
Version
4.6.0
Version
4.4.0
Version
4.3.0
Version 4.2.0
Version 4.1.0
Version 4.0
Redix Format Converter V6.2.0
New
Features:
Fully supports the HIPAA NPI
(National Provider Identifier).
Completely rewrote the Convert
area in the GUI Mapper.
-
Provides utilities to help
users view/modify/debug the IFD/OFD.
-
Allows users to view the
index file when the output contains multiple output
files. For example, if the output contains multiple
claim pages in the PDF format, the index file allows
users to view the summary of the claims and to view each
specific claim page.
Provides a Microsoft Visual
Studio 2005-style editor for collapsing/expanding the OFD
code.
Released RMAP module V4. The new
RMAP module now supports multiple ST and HIPAA NPI
validations.
The
International Components for Unicode (ICU) package was
integrated into the Redix engine, extending Redix's encoding
support to the 100+ encodings that are allowed by ICU. In
particular, all the encodings registered with the Internet
Assigned Numbers Authority (IANA) are now supported by the
Redix engine.
Redix Format Converter V6.1.0
New
Features:
PDF module. Adds 10 new OFD
functions to the PDF module. There are now around 65 OFD
functions that can be used with the PDF module.
Two new OFD functions,
writeEDIsegB and genEDIcompB, to generate EDI segment and
composite data elements.
Three new pre-defined HIPAA
maps:
1) HIPAA 837 Professional to
HCFA1500/CMS1500 PDF
2) HIPAA 837 Institutional
to UB92/UB04 PDF
3) HIPAA 835 to Medicare 835
Consolidated all of the API
calls' conversion flag parameters. The 'c' type can be used
for any type of XML file, including Well-Formed, DTD, and
Schema files. The 'b' type is no longer supported.
Adds several new OFD functions:
min, max, frmtdecimal, fmtzip, fmtphone, and rreplacestr.
Redix Format Converter V6.0.0
New
Features:
PDF module. Adds more
than 50 OFD functions that are used in the PDF module.
Supports WPC Open Source XML
Schemas for HIPAA Transaction standards.
Database Module now supports
the Linux platform.
New API's (xmledi_cfg and xmledi_app) and
a new executable xml2edi improve the performance of XML to
EDI conversions.
New API's (redix_x12_merge) and
a new executable redixx12merge
merge multiple X12
transactions into a single interchange file.
New API's (redix_x12_rerrange) and
a new executable redixx12rearrange rearrange
the contents of one X12 interchange into one or more
interchange files.
Supports long XML tag names,
including those that are specified by the WPC Open Source
XML Schemas.
New executable rmsginfo,
which returns a given message's information.
New pre-defined maps between
the HIPAA standard and the WPC HIPAA XML Schema. For
example, users can now use the pre-defined map to convert a WPC
Open Source Schema Professional Claim to a HIPAA 837 Professional
message and vice versa.
New OFD functions: removealphas
(removes alphabetic characters from a string),
removedigits (removes numeric characters from a string), removechars
(removes given characters from a string).
Consumes approximately 20% less
memory than the previous versions.
Redix Format Converter Version 5.8.0
New
Features:
Database Module now supports
the Solaris platform.
For HL7 messages, ACK
(acknowledgement) messages will be automatically generated.
Both the original mode and enhanced mode of ACK messages are
supported.
Provides more JAVA examples for
the AnyToAny, AnyToXML, and HL7ToAny engines.
Redix Format Converter Version 5.7.0
New
Features:
Adds several new OFD functions:
age (gets the age of an individual from his/her birth date), rdbinsert,
sqlinsert, orainsert (for database insertions), rdbfetchnext, sqlftetchnext,
orafetchnext (for database fetches).
Modifies some OFD functions to
allow non-printable (non-alphanumeric) characters to be
converted and printed. For example, the codeconv()
statement now supports the conversion of vertical bars,
commas, and other non-printable characters. The mstrcat()
statement has been extended to allow up to 8,000 data
strings to be concatenated, including non-printable
characters.
New API (redix_HL7_map) to
convert an HL7 message to any other format.
Supports multiple MSH
transactions in an HL7 message.
Supports custom JAVA packages on
the Solaris and Linux platforms.
The database module now runs on
the Linux platform.
Database module has been
modified to allow up to 999 fields in a table.
The database module's
performance has been improved by ~15%. Also, the
performance with the native driver of a specific database
has been improved. For optimal performance, use the Oracle
Call Interface (oci) for Oracle Databases and OLE-DB for
Microsoft SQL Servers.
Supports up to 999 fields in a
record. Previously, it was 99.
Includes
RMAP
Version 3.
Includes six pre-defined maps
which convert HCFA-1500 text images to the HIPAA 837 format.
Redix
Format Converter Version 5.5.0
New
Features:
Adds text image file support.
The HIPAA package now supports
mapping from an HCFA 1500 text image file to the HIPAA 837
Professional format
Adds two new OFD functions,
splitnames and splitaddsressN4, to split names and
addsresses, respectively
Adds the Cascade Map screen in
the GUI to allow users to run multi-maps by pressing a
single button
Redix
Format Converter Version 5.4.0
--------------------------------------------------------------------------------
New
Features:
Adds two new APIs, redix_isa_consolidate() and redix_license(). redix_isa_consolidate() is
used to consolidate multiple ISA/GS into one ISA and one GS
Adds the new executable redixisacons.exe.
Fixed a bug in "Migration
a database map".
New on-line help for the GUI
Mapper.
Modified the year validation so
that a valid year will be 1700-2100 when the data type is defined as DT type.
Fixed the "~' bug in the
before_event and after_event in the GUI Mapper
Redix
Format Converter Version 5.3.0
--------------------------------------------------------------------------------
New
Features:
The
new version now supports two more standards, HL7 (Version 2.3 and 2.4) and NCPDP
(Version 5.1).
Adds a new parameter "encoding
scheme" in AnyToXML engine. This new field was also addsed in the AnyToXML
configuration screen,
Adds
new APIs, redix_xml_map_extB(), redix_getHL7info(), and redix_getNCPDPinfo().
Adds
the scope checking feature. In the GUI Mapper, the user can choose if he/she
wants to turn on the scope check.
When
importing a map file, if the included IFD file also exists in the user's system,
the new GUI Mapper will prompt the user.
Redix
Format Converter Version 5.1.0
--------------------------------------------------------------------------------
New
Features:
A
new module "HIPAA RMAPs module" is created. The new module
includes the RMAPs for the following HIPAA messages:
837_Professional
837_Professional A1
837_Institutional
837_Institutional A1
837_Dental
837_Dental A1
835
835 A1
834
834 A1
270
270 A1
271
271 A1
278_Request
278_Request A1
278_Response
278_Response A1
The
Redix Format Converter Engine now includes the communication and data security
module. New OFD functions, such as encryptfile, decryptfile,
smimesendmail, ftprecv, ftpsend, zipfile, and unzipfile, are supported.
The
Redix Format Converter Engine now can be used as a scripting language to
handle the work-flows requirements.
The
Redix HIPAA Package now includes a new HIPAA compliance GUI. The user
can select any HIPAA file, whether it is a previous version of the new version
based on the Addsenda, and the tool will determine the file type and the
version number to pass to the right IFD and OFD for the compliance
checking. The 997 will be generated automatically. The view error
message can help the user to walk through the errors in case errors are
discovered. If the HIPAA messages are 837, 835 or 820 related, then a
corresponding balance reports will also be presented.
New
OFD functions are addsed, e.g., getX12info, getfiletype, and chkX12mult.
New
screen is provided to support the D type code checks. The new screen
allows users to modify and save the dbm files.
New
screen is addsed to generate map reports for used and not used elements.
New
screen is provided to view the X12/HIPAA/CSV files in grid. This feature
is very useful for the RMAPs.
to
top
Redix
Format Converter Version 5.0
--------------------------------------------------------------------------------
New
Features:
The
Redix Mapper Version 5.0 supports a new XML schema standard PIDX (Petroleum
Industry Data Exchange) Version 1.0
The
Redix HIPAA Package 5.0 supports the new HIPAA Addendum which was published in
Oct. 2002. All of the predefined HIPAA maps supported in the previous
version have been upgraded to support the new standard.
The
Redix HIPAA package now ships with three more predefined maps (RMAPS) that
converts proprietary Redix Comma Separated Values (CSV) files to HIPAA
837. These three maps include RMAP_1P to 837 Professional, RMAP_1I to 837
Institutional, and RMAP_1D to 837 Dental. Full documentation of each map is
included with the HIPAA package. More than 30 predefined maps are included in
this new version.
The
Redix HIPAA Package has been enhanced to support complete HIPAA compliance
checking to support WEDI/SNIP 1-7 level checks.
Adds
a new flexible grid view to allow users view or modify the input file.
The
Enhanced Configuration tab allows users to enter the TA1 filename and warning
level during the conversion.
Adds the ability to allow a translated XML file to be
indented.
Increases
the OFD edits in the GUI Mapper from 80 to 200. This allows users to adds
more OFD statements and checks.
When
importing an XML Schema, the GUI Mapper will list all of the possible root
elements to help users locate the root node.
The
View Error Information screen has been enhanced to allow users view the cross
reference map from the source tree.
The
GUI Mapper has been enhanced to include a "Save As..." button that
allow users to save the testing file after modification and uses the modified
file as the new testing file.
Adopts
a new naming convention for HIPAA standards, addenda, and balance reports.
Additional
OFD functions, including atocur, atodecimal, etc., have been addsed.
to
top
Redix
Format Converter Version 4.9.0
--------------------------------------------------------------------------------
New
Features:
The
Redix Mapper Version 4.9.0 includes a new backup utility, which allows users to
backup map files.
In
previous versions, the intra-segment compliance checking was done in the
OFD. In this version, it will be done in the IFD using the new G, H, or I
types in the "Syntax Rules".
Addsitional
OFD functions, including getlineno, preparelist, isuniquelist, deletelist,
isvaliddate, isvalidtime, etc, have been addsed.
To
improve performance when accessing the Oracle database, the new version will
bypass the ODBC driver and directly interface with the Oracle native
driver. The following OFD functions have been addsed in the new version for
this purpose: oraconnect, orardbsqlcmd, oradisconnect, and oragetnextavailint.
Four
types of code checks are supported in the new version, including Redix
proprietary index files.
The
new version addss a new GUI to help users view every translation error. The
errors can be compared to the input file, the standard message, and the map.
The
performance of the HIPAA compliance process has been improved by moving the
HIPAA intra-segment checking into the IFD.
to
top
Redix
Format Converter Version 4.8.0
--------------------------------------------------------------------------------
New
Features:
The
Redix Mapper Version 4.8.0 now includes a HIPAA/EDI debugging screen. The
screen displays detailed error information for each element if errors were found
during the translation. A red box will also be displayed in front of each row to
highlight the error segment. These new features will allow users to perform a
detailed HIPAA GAP analysis.
The
Edit Message screen in the Message Definition area now allows users to import
segments and their related element information from other message
definitions.
The
Edit Message screen now also supports a new tree view for non-XML messages.
The
new export feature in the Export a Map screen exports all of the information
about each map that will be exported and its source/target message definitions,
including code definitions and import OFDs.
In
the Redix Editor screen, new utilities have been addsed, including sorting and
conversion functions.
When
cloning a map, the Redix Mapper Version 4.8.0 will also allow users to clone the
message definitions.
The
Redix Mapper Version 4.8.0 allows users to convert external table lookups to the
"A" type of code check.
The
Redix Automation Processor 4.8.0 includes a new server process RAPserver.
Users can use VC++, VB, or Java to interface the server. Several RAP
client examples are provided in the examples folder under the Redix directory.
A
new default userdata screen allows users to edit ISA and GS segments, as well as
separators, for each X12 and HIPAA map.
The
Redix AnyToAny Engine with database module now includes two addsitional keywords,
rdbgetnextint and rdbgetcurint.
The
Redix Mapper Version 4.8.0 addss one more button to allow users quickly locate
the row that has an OFD error.
The
Redix Automation Processor has been modified to handle EDI/HIPAA to database
translations more efficiently.
to
top
Redix
Format Converter Version 4.7.0
--------------------------------------------------------------------------------
New
Features:
The
Redix Mapper Version 4.7.0 with the database module now supports mapping a
database in both directions, i.e., database to XML, EDI, or CSV, etc., and vice
versa. The database can be any ODBC compliant database system.
The
Redix AnyToAny Engine is enhanced to support more functions, including sendmail(),
atocur(), etc.
The
Redix HIPAA package provides more pre-defined maps, including the NSF 2.0/3.01
<-> HIPAA 837, UB92 5.0/6.0 <-> HIPPA 837, and HCFA ERA
<-> HIPAA 835. The proprietary UB92 format, such as the state
specific Medicare/Medicaid UB92, can also now be mapped to a HIPAA 837
transaction set in a pre-defined map.
The
Redix HIPAA package with database module provides a pre-defined map, which
converts the HIPAA 837 transaction set to a Microsoft SQL Server database; then
in a separate pre-defined map, the data is extracted from the SQL Server and
re-formulated into a HIPAA 837 message.
The
Redix HIPAA package provides balance check information. With one
key-stroke or an API function call, a HIPAA 837 or 835 transaction sets can be
balanced. A balance report is automatically generated. The report
can also be customized.
to
top
Redix
Format Converter Version 4.6.0
--------------------------------------------------------------------------------
New
Features:
Supports
W3C XML Schema. In addsition to the DTD, an XML Schema (xsd) file can be
imported to the Redix Mapper. Once the XML is message is imported, the
message is ready to be mapped.
In
the previous version, the X12 syntax rules and EDI code definitions are defined
in the OFD (Output File Descriptor). In this new release, they are defined
in the IFD (Input File Descriptor) instead. The Redix XML GUI Mapper's GUI
is deigned to help users construct the X12 syntax rules and EDI code
definitions. When the user extracts the EDI message from the EDI standard,
the X12 syntax rules and EDI code definitions are automatically generated. To
support the X12 syntax rules, a new section area "#SEGCOND" is created
in the IFD.
Supports
RosettaNet version 2.0.
Updates
the HIPAA transaction sets, including the syntax rules and code definitions.
Automatically
define the appropriate separators when a new map is created.
In
the previous version, when an XML message was mapped, a user would have to
create a dummy trailer node to hold the OFD statements, such as "endloop"
or "endsegment". In the new release, the user does not have to
do this any more since the Redix Mapper will automatically generate the "endloop"
or "endsegment" statements without using a dummy trailer.
Supports
database mapping. The new release provides a GUI to allow a user to map
any message, including EDI, XML, CSV, flat file, to an ODBC database.
to top
Redix
Format Converter Version 4.4.0
--------------------------------------------------------------------------------
New
Features:
With
this new version, users can now identify a variety of segment and element
details through the use of the Mapper Area's Input and Output Message
Definition's icons.
-
An input message definition's icon can now be differentiated between
segments that contain or do not contain loops.
-
An output message definition's icon can also now be differentiated
between segments that contain or do not contain defined elements, loops, segment
loops, conditional statements, before events, and after events. In
addsition, different icons are now used to distinguish between different types of
element definitions, as well as whether or not an element contains loops,
segment loops, conditional statements, before events, and/or after events.
The
Redix Mapper Area has also been expanded to allow a user to open a dialog box,
which will allow the user to display and/or print a listing of addsitional
information, e.g., element conditions, before/after events, etc., associated
with a Map Definition's elements.
to
top
Redix
Format Converter Version 4.3.0
--------------------------------------------------------------------------------
New
Features:
The
long-awaited Integration Guide is finally available.
-
This guide details the API, COM, ActiveX, and Redix Automation Processor
(RAP).
-
It also provides examples to interface the Redix AnyToAny engine,
AnyToXML engine, user exits functions, database module, and userdata() functions
with the user's existing application. These examples are in various programming
languages, including VC++, VB, and JAVA (TM).
It
is now possible to pass the EDI Interchange Information with an automatically
generated XML to EDI Map Definition, using the userdata() function in an OFD
file.
-
The ability to
pass data during translation by using the userdata() function has existed for
quite some time, but now this feature has been taken one step further. Users now
have the option to use a hybrid OFD form during the exportation of an XML to EDI
Map Definition in the Export to DTD Dialog Box.
-
In addsition,
precedence has been given to existing data from the incoming XML input file. The
following rules apply to the ISA and GS segment fields:
| -
|
| If input data is passed to the map, use
this data |
| -
|
| Otherwise, if there is no data being
passed, use the userdata() function |
| -
|
| If there is no input data nor userdata()
function being passed, use a default value |
-
For more
details about this new feature and its specifications, please refer to the
"Extracting Using userdata() from XML to EDI" section of the "N2K
(Need To Know)" chapter from the GUI Mapper Online Help Manual.
The
integer error
return code may now be referenced to display the cause of error.
-
Upon completion of
a translation process, whether it was successful or not, an integer is always
returned, corresponding to the success of the translation. The integer zero
represents a successful translation, while a negative integer is returned to
reference a failed translation. Now, it is possible for the user to send the
returned error code to an API or command-line function to return the error
message. For example:
| - |
A translation that returns the
integer -104, may be passed through an API such as redix_get_err_msg(-104)
to return the error message: |
| |
|
Error in Opening the IFD. |
| - |
or, a translation that returns
a -101 may be passed through the command-line command errcode -101
to return the message: |
| |
|
Error in Opening the Input File. |
-
The API function redix_get_err_msg
(integer) has now been addsed to the file rfcerr.lib (for Windows) and
libredixerr.a (for UNIX) located in the /lib directory of the Redix folder.
-
The command-line
executable errcode integer has now been addsed to the Redix folder.
-
For more
information concerning the error return code processes, please refer to the
"N2K (Need To Know)" chapter under the subject "Error Code
Messages" of the GUI Mapper Online Help Manual.
Two
new functions, redix_mem_process and redix_app_process, have been
addsed to allow users to interact with the Redix Automation Processor using
input/output files or data streams.
-
The
function redix_mem_process allows the user to use data streams as the
input and output data. The following is a description of the parameters, which
may be used:
| redix_mem_process( |
input_string |
, |
A variable of type String Data
containing the input information. |
| output_string |
, |
A variable of type String Data
to contain the output information. |
| error_string |
, |
A variable of type String Data
to contain any error information, if one exists. |
| ack_string |
, |
A variable of type String Data
to contain any acknowledgement information, if one is to be created. |
| configuration_file |
, |
A variable of type String Data
containing the name of the configuration file of the RAP process. |
| log_file |
, |
A variable of type String Data
containing the name of the log file, of the RAP process, to be appended. |
| userdata |
, |
A variable of type String
Data containing the userdata to the AnyToAny engine. |
| ); |
-
The function redix_app_process
allows a user to use data files as the input and output data. Below is a
description of the parameters, which may be used:
| redix_app_process( |
input_file |
, |
A variable of type String Data
containing the name of the input file of the RAP process. |
| output_file |
, |
A variable of type String Data
containing the name of the output file, to be created during the RAP
process. |
| error_file |
, |
A variable of type String Data
containing the name of the error file, to be created (if any), during
the RAP process. |
| ack_file |
, |
A variable of type String Data
containing the name of the acknowledgement file, to be created (if any),
during the RAP process. |
| configuration_file |
, |
A variable of type String Data
containing the name of the configuration file of the RAP process. |
| log_file |
, |
A variable of type String Data
containing the name of the log file, of the RAP process, to be appended. |
| userdata |
, |
A variable of type String
Data containing the userdata to the AnyToAny engine. |
| ); |
-
The difference
between the functions redix_app_process and the redix_mem_process is that the
redix_mem_process function writes the output to a string, while the
redix_app_process writes the output to a file.
-
When these
functions are used, the directories and filenames defined in the configuration
file are NOT used; instead, the directories and filenames that are specified by
the parameters. In addsition, the need to include the parameter log_file is
optional. If no value is passed for the log_file parameter, the name XMLProcess.log
will be used by default.
-
Addsitional
information concerning the new RAP functions may be found in the Redix
Automation Processor Manual and Integration Guide.
to top
Redix Format Converter Version 4.2.0
--------------------------------------------------------------------------------
New
Features:
To
accommodate the user’s rapidly changing needs, as well as to enhance the
GUI’s ease of use, the RFC Conversion Area now has a new design.
-
To better integrate the RFC Conversion Area into the RFC, the Conversion
Area’s structure is now similar to the Mapper and Message Definition Areas.
-
The tabs are now designed to give the user a sense of before and after
the conversion process.
- In addsition to the new design, users can now create a Conversion Area
Project from the Generate IFD / OFD Dialog Box.
Furthermore,
the RFC AnyToXML Area also has a new and innovative design.
-
As with the RFC Conversion Area, the RFC AnyToXML Area’s structure is
also similar to Mapper and Message Definition Areas.
-
Similar to the RFC Conversion Area, the tabs are now designed to show the
user before and after the conversion process.
-
Like the RFC Conversion Area, users can now create an AnyToXML Area
Project from the Export to DTD or Export to Schema dialog boxes.
To speed
up the conversion process, the Generate IFD / OFD dialog box has also been
updated.
-
Through the use of the Generate IFD / OFD dialog box, the user can now
create a Conversion Area project in the Mapper.
-
The addsitions in the Generate IFD / OFD dialog box will allow the user to
select a map definition to be used and specify any pertinent separators for the
new project.
-
Once the project is created, all the user needs to do is to adds some
personal preferences, an input file, and then, the user can view his/her own
work.
-
Addsitional details can now be found in the rfc.hlp manual under the
topic, The XML Cycle of the “Need 2 Know” chapter.
In
addsition, the Export to DTD dialog box has also been updated.
-
The Export to DTD dialog box now allows the user to create an AnyToXML
Area project from any non-XML definition.
-
The addsitions in the Export to DTD dialog box will allow the user to
select a non-XML message definition to be used. Then the user can generate the
new project along with a new DTD and Mapper Area Definition.
-
Once the project is created, all the user needs to do is to adds some
personal preferences, an input file, and then, the user can view his/her own
work.
-
In addsition, while using the Element style structure, the user can now
construct his/her own DTD and Map Definition using the Description Naming
Convention.
-
Addsitional details can now be found in the rfc.hlp manual under the
topic, The XML Cycle of the "Need 2 Know" chapter.
Lastly,
the Export to Schema dialog box has also been updated.
-
The Export to Schema dialog box now has the ability to create an AnyToXML
Area project from any non-XML definition.
-
This addsition in the Export to Schema dialog box will allow the user to
select any non-XML message definition and generate this into a new project along
with the Schema.
-
Once the project is created, all the user needs to do is adds to some
personal preferences, an input file, and then, the user can view his/her own
work.
-
Addsitional details can be found in the rfc.hlp manual.
Addsitional
Corrections and Updates:
Bugs in the CSV
Multiple Header / Record Type have been solved.
-
The program will now not only assume endsegment statements, but
will also assume the endloop statement as well, allowing for proper loop
cycling.
to top
Redix Format Converter Version 4.1.0
--------------------------------------------------------------------------------
New Features:
The
RFC supports the ability to automatically map a
message definition to its own matching, well-structured, newly created, XML
definition.
The RFC now supports Message Definition Extraction to
W3C Schema
The RFC
Now Supports Message Definition Extraction to
BizTalk Schema
Massive Mapper Tutorial Expansion
Redix Command-line Procedures Explained
New
Database Module for Code Check Validation
New Module: Redix Automation Processor
New smart CSV data type
Corrections and Updates:
Java
[TM] JDK 1.3 and above Version Fix
writeXMLAttribute()
Bug Correction
EDI
Standards Additions and Correction
Import Process of Redix XML Definition Database
Bug
to top
Redix Format Converter Version 4.0
--------------------------------------------------------------------------------
New Features:
Full support of CSV Files
- Full support of CSV files as both Input and Output file
types.
|
- That is correct, files of only one record type, and a
set number of items of variable length may now be used as input or
output message definitions.
|
i.e.
"A","BB","CCCC","DDD"
or
123/435/643/756/345
or
'1'-'432'-'65456'-'865'
You may set your separators.
|
- Additional details can be found in the rfc.hlp manual.
|
Redix Engine Alternate DTD location support
- Added the ability for the Redix Engine to search the
PATH of the local system, if a required XML DTD is not present in the
Redix Program's directory.
|
- If the user uses the following statement:
<!DOCTYPE Transaction SYSTEM "MyDTD.dtd">
the Redix Engine will search for the "MyDTD.dtd" file within
the Redix program's directory, and if not present there, will search
within the paths defined within the SYSTEM PATH.
|
- This feature is available for the Redix Engine, not the
Redix GUI mapper.
|
- Additional details can be found in the rfc.hlp manual.
|
The Redix Command-line now accepts the OUTFILE name
- Now the user can specify the variable "OUTFILE"
within their command-line configurations files, which allows them to
specify the name of the output file to be created.
|
- Additional details can be found in the rfcxml.hlp manual.
|
Find and Replace Utility added to the Message
and XML Definition Edit Screen Tabs
- Now by clicking on the 
button, the following screen will be shown:
|
|
|
- The user may then replace all occurrences of a text item
within a tabular column, with a new text item.
|
- Details found in the rfcxml.hlp manual.
|
Corrections and Updates:
Sequence Characters
- The format of converted Sequence Characters has been
corrected.
|
- & will now convert to & when applicable (and
vise versa).
|
- > will now convert to > when applicable (and
vise versa).
|
- As well as all other acceptable sequence characters.
|
- Additional details can be found in the rfc.hlp manual.
|
Split() and AllocArray() Pointer Problem
- A pointer problem in the split() and allocarray()
functions has been corrected to assure stability.
|
Since no one template package can meet the needs of everyone, the chances are good that you will need to
adds extra pages to your web site. Rather than create a new page template, we've
added a New Page template.
(It's a quick, easy shortcut we've used for years!) Use this page to create extra pages for your web. Within the folders view:
|
Make a copy of the newpage.htm page by highlighting it and then using these shortcuts - Control + C to copy and Control + V to paste. |
|
Rename your newly copied page to whatever name you need. |
|
Then drag the page into the navigation view and drop it into place. |
|
Front Page will then apply the proper names to the buttons and page banner. |
|
Make as many pages as you need, when you need them. |
|
