Expere Authoring Tools Change Log

Administration Enhancements

Modified SCHEMA.PKG Generation
Type: Enhancement Reference: PBI 318597 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: Expere Administration Tool User Guide
Summary: Support was implemented for supplying a predefined document print order in the PacketType\DocumentRefs element.
Technical Notes: With this change the content builder will generate a document data requirement SCHEMA file when a predefined PKG file is present in the source repository. The SCHEMA file contains all the data points referenced by all the document package selection rules for each document referencing a given package. Packages correspond to phases defined in the phase group PHAS file.
Implementation Notes: This feature requires an Administration Tool update.

Expere Administration Tool Time Out Configurable
Type: Enhancement Reference: PBI 360260 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: Administration Tool User Guide
Summary: The Requirements Administration application has been enhanced to be able to configure load timeout to avoid failure loading huge repositories. The default timeout changed from the current hard coded value of 5 minutes, to 10 minutes.
Technical Notes: Modified ReqAdmin.exe.config and RequirementsAdmin.exe.config to include new key in appSettings group: <add key="LoadTimeout" value="10"/> Value 10 corresponds to 10 minutes. If key "LoadTimeout" does not exist in config file, internal load timeout will be set to 10 by default.
Implementation Notes: This feature requires Requirements Administration Tool (Server Tools) update.

ReqAdmin – Content References Not Updating in Single Pass using ‘Update’ command
Reference: PBI 360269 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: No documentation impact.
Summary: The ReqAdmin update command was not fully updating content references in one pass. After running the update command and updating the authoring web service with the updated repository, when opening an REQ file in the RE3 tool, messaging indicated that content references still needed to be updated.
Technical Notes: For Nested ContentReferences, the existing logic automatically ran the update process twice. If more than two nested levels existed, the update command had to be ran again which then update two additional levels. The command would need to be executed multiple times depending upon the number of nested content references. The logic was modified to update 'all' nested references in one single pass. Each time the update command was executed, the REQ filesize would grow as a result of updating contentreference elements with new IDs but leaving behind the old as unused rules. The logic was modified to update the parent content reference and any nested content references and update at the same time. This prevents new unused rules from being created but does remove any from existing repositories (development of a function to remove unused rules will be addressed in separate PBI). To improve performance, caching has been added at org structure level so that a child org that needs to update from a parent/root, won't re-update the parent/root if that was already done. Previously the caching was happening at the org level instead of org Structure level.
Implementation Notes: This feature requires a Requirements Administration Tool (Server Tools) update.

CPU/Memory Improvements
Type: Enhancement Reference: PBI 357091 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: No Documentation Impact
Summary: Modified the ‘build’ functionality to improve inefficiencies with CPU and Memory. The build functionality is used both by the Administration Tool and as a ReqAdmin command (‘build’).
Technical Notes: Improved memory leaks in all areas except PTRParsing section. Very large repositories may still experience high usage of CPU/Memory due to the PTRParsing re-write not completed.
Implementation Notes: This feature requires a Requirements Administration Tool (Server Tools) update.

Remove Unused/Orphaned Rules Command
Reference: PBI 364198 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: Expere Administration Tool User Guide
Summary: You can run this command against a Repository to remove all unused/orphaned rules from all documents in the Repository. This will help alleviate space issues and may help improve build times.
Technical Notes: We have added a new command to the ReqAdmin command line that will allow users to modify a Repository in order to remove all unused rules. The command line for this is: removeorphanedrules <Repository Path>
Implementation Notes: This feature requires a Requirements Administration Tool (Server Tools) update.

Content Stylesheet Enhancements

TagTree Structure Minimization
Type: Defect Reference: 358050 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Summary: Modified creation of the TagTree structure to simplify the tags and meet proper tagging requirements as follows: consolidated separate paragraph tags to eliminate the extra ‘pause’ by screen readers, removed tags with empty values, replaced incorrectly used paragraph and span tags with either sections or divisions.
Technical Notes: Modified FOPRender.java to add support for FillableCheckbox to FoFIlter. Added ID attribute to Signer object created by FOAcroFormFieldFilter. Added ADA roles to various components in layout tables; remove tags for non-breaking spaces. Rewrite logic that cleans up the tag tree before final PDF production. Modified Content Stylesheets to add role attribute for Sections; fix missing fo:table-row in Signature markup; add role attribute to Para and FragmentedPara.
Implementation Notes: This feature requires an Expere Engine Update and Content Stylesheets update (Stylesheets Modified: WKFS_StyleGuide.xsl, Signature.xsl, Sections.xsl).

Content References Previous/Next Navigation Toolbar
Type: Enhancement Reference: PBI 336794 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: No documentation impact
Summary: A new Content References Navigation toolbar has been added to Requirements Editor (RE3). The toolbar has two new buttons for previous and next for navigating content reference blocks within an REQ file
Technical Notes: By default, the new toolbar is not visible. To display the toolbar, go to View>Toolbars and select Content References Navigation. This functionality originated as a navigation requirement for the Merge Tool.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.

Tagline Separator Line

Type: Enhancement
Reference: PBI 346328
Compliance Impacts: This enhancement is not a compliance or regulatory issue.
Documentation: Requirements Editor User Guide

Summary: The TaglineSeparatorLine attribute has been added to the Document element, providing the ability to suppress printing the Tagline separator line.

Technical Notes:

Attribute Name	TaglineSeparatorLine
Values	Yes, No - Default is Yes
Logic	If attribute is not present -or- TaglineSeparatorLine=Yes, then continue to honor printing the tagline seperator line as it does today. If TaglineSeparatorLine=No, suppress printing the tagline seperator line.
Additional Information	By default, if the Tagline and MetaData elements are not authored, the default behavior is to print a tagline separator line at bottom of each page. Also, presence of Tagline and/or MetaData elements will print a tagline separator line. In either scenario, adding TaglineSeparatorLine=No element will be honored and suppress printing of the tagline separator line.

Implementation Notes: This feature requires a Content Stylesheet and a Requirements Editor Tool update.

Content Stylesheet Defects

Spaces no longer trimmed when authored in phrase
Type: Defect Reference: PBI 349232 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: No documentation impact
Issue: Resolved an issue identified with FragmentedPara’s where the Phrase element had spaces authored which were getting removed when the PDF was rendered.
Solution: Modified WKFS_StyleGuide.xls to remove the fo:Inline wrapper added to otherwise clause.
Implementation Notes: This feature requires a Content Style Sheet update.

eInitials printing incorrect line widths
Type: Defect Reference: PBI 320447 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation: Requirements Editor User Guide
Issue: When generating documents that include eInitials, the line width is printing 2.5 inch, which is the length for the eSignature field. Previously, when the Esignature type 'initials' was chosen, the line coming from the signature element still printed full width.
Solution: Now, when Esignature elements are present and the type 'initials' is chosen and the Length attribute is not authored, the signature line is the same width as the Esignature initial box by default, not standard full width. If Length attribute is authored, that attribute is honored.
Implementation Notes: This feature requires a Requirements Editor Tool update.

Ancillary Barcode printing over tagline resolved
Type: Defect Reference: PBI 355602 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation: No document impact.
Issue: Users reported that the ancillary barcode printed over the document tagline on certain documents from the October content release. Note: No issues existed with TRID or static documents.
Solution: There was a change made to the WKFS_StyleGuide. Now the barcodes will no longer render over the top of a footer or tagline.
Implementation Notes: This feature requires a content stylesheet update which will be available in the November content.

Alignment 'Justify' not working correctly for Notice Element
Type: Defect Reference: 308772 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: An issue was identified with the alignment attributes (Justify, Left, Right, Center) of the Notice/NoticeContent element in that when there is a bold, italic, all caps, small caps, small font, large font, or title font emphases wrapped around the content, the information would not print as selected.
Solution: The Content stylesheet was modified to correct the issue. Now, if emphases are wrapped around the content, the information prints as expected.
Implementation Notes: This feature requires a style sheet (WKFS_StyleGuide.xsl) update.

Data Dictionary Viewer Defects

Resolved error when comparing data dictionaries
Type: Defect Reference: PBI 363523 Compliance Impacts: This defect is a compliance issue. Documentation: No documentation impact.
Issue: An issue was identified while opening a compare dictionary: Error: `An error occurred comparing data dictionaries. Index was outside the bounds of the array.`
Solution: The solution required changes to the Data Dictionary Viewer.
Implementation Notes: This feature requires a Data Dictionary Builder update.

Requirements Editor Enhancements

New Element for Doc Viewer text display only
Type: Enhancement Reference: PBI 370475 Compliance Impacts: This enhancement is a compliance issue. Documentation: Requirements Editor 3 User Guide
Summary: A new element ‘DocViewerOnly’ can be authored in a REQ file and when set to true, the corresponding text is displayed/visable in Doc Viewer only and suppressed from the rendered PDF. The new element can be authored as a child of a Condition/Otherwise element with a child para element to define the text. The use case for this new element derived from the new rounding method implemented for the TILA-RESPA Integrated Disclosures to provide the capability to explain rounding rule details.
Technical Notes: Modified the Instance.xsd to add new element and modified RulesToErl.xsl stylesheet to strip out the element information so it does not render on the PDF.
Implementation Notes: This requires a Requirements Editor upgrade.

REQ File Name Added to PTR Editor Window
Type: Enhancement Reference: PBI 338046 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: Requirements Editor 3 User Guide
Summary: The “PTR Editor” window now displays the name of the document. In the upper left-hand corner of the window the document name appears after “PTR Editor”. When working with multiple REQs and PTR windows this will help differentiate the PTR Editor windows.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.

Outline Editor Displays IDs for Conditions and Iterators
Type: Enhancement Reference: PBI 335031 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: No Documentation Impact
Summary: The Outline Editor tab has been enhanced to display the ID for Conditions and Iterators formatted as COND.ID##### or ITR.ID#####. Previously, Conditions and Iterators displayed the text ‘AutoID’.
Technical Notes: Modified Outline.cs file to include ID display.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.

Content References Previous/Next Navigation Toolbar
Type: Enhancement Reference: PBI 336794 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: No documentation impact
Summary: A new Content References Navigation toolbar has been added to Requirements Editor (RE3). The toolbar has two new buttons for previous and next for navigating content reference blocks within an REQ file
Technical Notes: By default, the new toolbar is not visible. To display the toolbar, go to View>Toolbars and select Content References Navigation. This functionality originated as a navigation requirement for the Merge Tool.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.

Resizable Content Reference Window
Type: Enhancement Reference: PBI 336153 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: No documentation impact.
Summary: The Content Reference window is now resizable. This allows for resizing the window to see longer reference names without having to use the horizontal scroll bar.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3) update.

Rendition Web Services Update
Type: Enhancement Reference: PBI 355241 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: No documentation impact.
Summary: The Renditional Web Services addresses have been updated to the most current addresses, eliminating the need to manually look up and update the them.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3) update.

Create HTML outlines instead of PDF for large outlines
Type: Enhancement Reference: 365905 Compliance Impacts: None Documentation Impacts: None
Summary: Changes were made to the PDF Outline functionality to allow for HTML outlines instead of PDF. If a PDF outline is determine too large to produce within the PDF Outline tab, it will instead be presented as HTML.
Technical Notes: If a HTML outline is preferred for all outlines instead of PDF, the following setting in Windows Registry can be added to allow for this preference: HKEY_CURRENT_USER\Software\Wolters Kluwer\RequirementsEditor\3.0\Expere\OutputOutlineFormat with the value HTML.
Implementation Notes: This enhancement requires a Requirements Editor update.

Projects Migrated to Core Shared Libraries
Type: Enhancement Reference: PBI 367801 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: No documentation impact
Summary: ExpereNetRuntime and BuildOutlinePDF have been migrated to the Requirements.Service shared core library. resourcesLib has been migrated to the Requirements.Commonshared core library. This helps in getting core logic into the core libraries and also allows for better documentation and testing.
Implementation Notes: This feature requires a Requirements Editor Tool update.

New Command for Build, Repository, Preview and Outline artifacts
Type: Enhancement Reference: 372080 Compliance Impacts: None Documentation Impacts: None
Summary: A new command has been created that allows for the merging of Build, Repository, Preview and Outline artifacts.
Technical Notes: This new command allows for a user to pass a repository, its build output and optionally preview and outlines outputs to create a manifest. The command will then output all the combined artifacts on either a singular line of business basis or on a combined line of business basis depending on how the user wishes to receive the output.
Implementation Notes: The enhancement ONLY requires an Expere Server Tools update, but it is advised to only be used internally as it will help with our content build process.

RE3 Framework – 2015 Visual Studio Upgrade
Type: Enhancement Reference: PBI 371925 Compliance Impacts: None Documentation Impacts: None
Summary: The RE3 Framework solution has been upgraded from Visual Studio 2013 to Visual Studio 2015.
Technical Notes: The entire RE3 framework solution has been upgraded to Visual Studio 2015 with the exception of the Isolated Shell which remains in Visual Studio 2013. Upgrading keeps us current with latest technology stack and provides additional features for debugging.
Implementation Notes: This feature requires a Requirements Editor 3 Tool Update. Note: Pre-Requisite Component Required: Prior to installing the 16.1.0 release of RE3, installation of the Microsoft C++ 2015 Redistributable (x86) executable is required. The pre-requisite executable can be found in Install folder: VC_redist.x86.exe. This is one-time install; once it is installed, it does not need to be installed again with future updates.

Tagline Separator Line

Type: Enhancement
Reference: PBI 346328
Compliance Impacts: This enhancement is not a compliance or regulatory issue.
Documentation: Requirements Editor User Guide

Summary: The TaglineSeparatorLine attribute has been added to the Document element, providing the ability to suppress printing the Tagline separator line.

Technical Notes:

Attribute Name	TaglineSeparatorLine
Values	Yes, No - Default is Yes
Logic	If attribute is not present -or- TaglineSeparatorLine=Yes, then continue to honor printing the tagline seperator line as it does today. If TaglineSeparatorLine=No, suppress printing the tagline seperator line.
Additional Information	By default, if the Tagline and MetaData elements are not authored, the default behavior is to print a tagline separator line at bottom of each page. Also, presence of Tagline and/or MetaData elements will print a tagline separator line. In either scenario, adding TaglineSeparatorLine=No element will be honored and suppress printing of the tagline separator line.

Implementation Notes: This feature requires a Content Stylesheet and a Requirements Editor Tool update.

Requirements Editor Defects

Build/Assembly Transaction when Unused Rules Exist
Type: Defect Reference: PBI 367213 Compliance Impacts: This enhancement is not a compliance issue. Documentation: No documentation impact
Summary: Previously, the RE3 Build and Execute Document functions caused an error if there were unused rules.
Techinical Notes: This modification provides the ability to build and assemble a transaction without errors, even if there are unused rules in the REQ (applies to dynamic docs only). Impacts both Readonly and Writeable REQ files. Note: This modification: applies to dynamic documents only impacts both ReadOnly and Writeable REQ files
Implementation Notes: This requires a Requirements Editor update.

Loan Estimate – New Sum/Round Method for Fees Not Disclosed
Type: Enhancement Reference: PBI 351029 Compliance Impacts: This enhancement is a compliance issue. Documentation: Requirements Editor 3 User Guide, Expere Developer’s Guide
Summary: Per TILA-RESPA Integrated Disclosure rules, fees that are not disclosed separately, must be aggregated first with actual values, totaled and then rounded. The Expere Tools have been modified to support this scenario. Prior to this enhancement, fees that are not disclosed separately would round each fee first and then be summed together to obtain the total which results in a compliance error where the totals can be off by $1 or more depending on the number of fees and amount of the fees. On the Loan Estimate, for Loan Costs and Other Costs Sections that have fees that exceed the maximum number to be disclosed are aggregated together and disclosed as "Additional Charges" in Subsections A, B, F, G and H, and C (if addendum is not used). For these fees that are aggregated together and disclosed as "Additional Charges", the rounding method has now changed to use the "Total First, then Round" method since these fees are not separately itemized and disclosed (previously, the "Round First, then Total" method was used). As a result of this change to the "Additional Charges" rounding method, the section totals and subtotal sections have been updated to reflect this change. This applies to both TXN and MISMO Expere Knowledge Base Content versions. Code of Federal Regulations Information: 12 CFR 1026.37(f)(6). 12 CFR 1026.37(o)(4)(i)
Technical Notes: The Requirements Editor 3 Tool has been enhanced to add new elements and attributes to support the new rounding method. The Expere Engine Stylesheet has been modified to add logic to utilize new elements/attributes and implement new rounding method to for calculating totals for fees that are not disclosed separately.
Implementation Notes: This feature requires an Expere Engine Update and Requirements Editor 3 Tool Update. Important: Installing the released version of the Expere Knowledge Base Content with TILA/RESPA Rounding Updates requires upgrading the Expere Engine and Requirements Editor 3 Tool to Version 16.1.0; the updated content is not backwards compatible with prior versions of the Expere Engine/Tools.

Changes to Title Font Emphasis and DefinedTerm
Type: Defect Reference: 345913 Compliance Impacts: This is a compliance issue. Documentation Impacts: None
Summary: Previously, when Title Font emphasis or DefinedTerm tags were added anywhere in text elements (such as para elements) and the element after the emphasis contained DTAs, the PTR Editor did not display the correct DTA information when editing the element.
Technical Notes: Now, when placing Title Font emphasis or DefinedTerm tags at the beginning or in the middle of text elements that contain DTAs, the PTR Editor window displays the correct DTA information when editing the field.
Implementation Notes: This requires a Requirements Editor upgrade.

eInitials printing incorrect line widths
Type: Defect Reference: PBI 320447 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation: Requirements Editor User Guide
Issue: When generating documents that include eInitials, the line width is printing 2.5 inch, which is the length for the eSignature field. Previously, when the Esignature type 'initials' was chosen, the line coming from the signature element still printed full width.
Solution: Now, when Esignature elements are present and the type 'initials' is chosen and the Length attribute is not authored, the signature line is the same width as the Esignature initial box by default, not standard full width. If Length attribute is authored, that attribute is honored.
Implementation Notes: This feature requires a Requirements Editor Tool update.

Editing Element Text displays as Raw XML
Type: Defect Reference: PBI 353368 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation: No documentation impact
Issue: Resolved an issue where Raw XML was displaying when editing the contents of an element that included text and a data item (DTA).
Technical Notes: Reverted a prior change and implemented a new solution that changed the SchemaLocation attribute on the InstanceReqDiff.xsd (schema file for the merge tool) to correctly reference the Instance.xsd (RE Tool main schema file).
Implementation Notes: This feature requires a Requirements Editor Tool (RE2 & RE3) update.

"Save As" Lock Up Resolved
Type: Defect Reference: 350176 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: When performing a Save As function, if users clicked the Cancel button on the Document Properties window during the save, any future Save As functionality was disabled. Now users are able to cancel on the Document Properties screen and then save.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.

Editable REQ After Save As
Type: Defect Reference: 237525 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: Previously, when you performed a Save As command on a read-only REQ, you could not edit the new file. The application behaved as if it was still a read-only document.
Solution: Now, When users perform a Save As command with read-only files, the new file is editable.
Implementation Notes: This feature requires a Requirements Editor Tool update.

Spelling Correction for Requirements Document File ‘Type’ Description
Type: Defect Reference: 346756 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: The file ‘Type’ description for Requirements Editor files when browsing using Windows Explorer was spelled incorrectly as ‘Requiements Document’.
Solution: Corrected the spelling to be ‘Requirements Document’.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.

PTR Editor Window – Able to Scroll and Copy/Paste ReadOnly REQ Files
Type: Defect Reference: 354911 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: Resolved issue where the scroll bar was disabled and unable to copy/paste text for ‘Business Logic’ and ‘PTR’ fields when the REQ (RE3) file properties were set as Read Only.
Solution: Modified fields in PTR Editor to allow scrolling and copy/paste when file is Read Only.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.

Missing Web Service Error Message
Type: Defect Reference: 350556 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: Previously, an error message was displayed after a user cleared the authoring web service value within Tools > Options and attempted to open an REQ file.
Solution: A change was made to alert the user while opening an REQ file if there is a missing Web Service in the Expere Configuration options.
Implementation Notes: This feature requires a Requirements Editor Tool update.

Preview and PDF Outline tabs result in path incorrect error
Type: Defect Reference: 355631 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: An error was resolved when navigating to the Preview or PDF Outlines tab in RE3. The Preview tab generated the following error: `Preview unavailable: Could not find a part of the path ‘C:\Users \firstname.lastname\Appdata\Local\Temp\RequirementsEditor\`. The PDF Outline tab generated the following error: `Cannot find …:/Users/firstname.lastname/AppData/Local/Temp/Req…`
Solution: A problem occurs if the folder RequirementsEditor does not exist under the users\Appdata\Local\Temp directory. A check was added to see if the directory does not exist and creates it if not found.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3) update.

REQ Filename included in application bar
Type: Enhancement Reference: 313095 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation Impacts: No Documentation Impact
Summary: The Requirements Editor 3 application was modified to include the REQ Filename name in the application title. When the application is minimized or when using alt-tab to navigate applications, the Filename is included so the user can easily identify the session to select. If there are multiple REQ files open in a single session, the filename of the REQ that has focus is used for the name in the application title.
Technical Notes: Modified setting in the isolated shell to show project name before tool name which was not set previously.
Implementation Notes: This feature requires a Requirements Editor 3 Tool update.

PTREditor Does Not Display Rule Info after Content References Update
Type: Defect Reference: 364386 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: When opening an REQ file that has out of date content references, the rules in those content references are not displaying in the PTR Editor Window after the content references update. The PTR editor remains blank when selecting a rule (any DTA/COND/ITR). This also happens on updating a content reference manually, adding a new content reference and the automatic content reference update.
Solution: RE Tool was modified to reload the entire tree whenever a content reference update takes place and to expand all sections to their previous state before the update. The PTR Editor was not displaying the rule info after the content references update because the content references were not updating the content from the web service, but the field grid was getting updated. This resulted in rules showing up in the outline editor that were not in the field grid.
Implementation Notes: This feature requires a Requirements Editor Tool (RE 3) update.

Messaging for Duplicate Element IDs Instead of Auto Renumbering
Type: Defect Reference: 362370 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: When opening an REQ file, and user selects ‘No’ to the message asking to ‘Update Inherited Components’, duplicate Element IDs (ie. Section, Notice, TransactionGraphic, etc.) were automatically renumbered to make it unique. Research concluded that the renumbering of IDs occurred at time of opening the REQ file, not as a result of the ‘Update Inherited Components’ messaging. System logic is in place that automatically trapped for duplicate element IDs and renumbered to make them unique which in some cases resulted in other ID duplication which in turn were renumbered as the logic for the new ID assigned does not check if the ID is already in use.
Solution: Modified the existing logic to identify the duplicate element IDs and display a message to the user instead of automatically renumbering. The user can research the duplicity to research root cause and determine remedy actions.
Implementation Notes: This feature requires a Requirements Editor Tool (RE 3) update.

Inactive Content Omitted on PDF Outline
Type: Defect Reference: 349246 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: Previously with PDF outlines, if content was Inactive in the Outline view it was being displayed in the PDF outline view. This is confusing for the customer because in the PDF outline view they cannot tell where Inactive content begins and ends.
Solution: All Inactive content is omitted in the PDF Outline.
Implementation Notes: This feature requires a Requirements Editor Tool update.

Adding Attributes to Content References
Type: Defect Reference: 349335 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: An issue was identified in which a user could add attributes to content refrences when they should not have that ability. This was done by right-clicking on the root of a content reference and adding a profile attribute to the content reference.
Solution: Code was modified to remove the ability to add attributes or child elements to content references.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3) update.

Resolved error adding valid Schema to Transaction XML
Type: Defect Reference: 364452 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: Previously, adding a TXN>Borrowers element in Transaction XML resulted in the following error message: `An error occurred adding the element to the prototype: The reference node is not a child of this node.`
Solution: Now for Transaction XML, you can add a Borrowers element at the TXN level without receiving an error, even if it exists in the Notes>Note element.
Implementation Notes: This feature requires a Requirements Editor Tool update.

Rendition plugin for internal Requirements Editor Installer
Type: Defect Reference: 357497 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: For Internal installations only: Previously, the E-Form Rendition package was always intalling, even after choosing Make Unavailable in the Advanced install options.
Solution: The installer was updated to ensure the following: E-Form Rendition package is installed when the install package is selected. E-Form Rendition package is not installed when the Unavailable option is choosen for the E-Form Rendition package in Advanced Install options. Update installationss (without uninstalling first) honor the previous install decision to exclude it or include it. When installed, the E-Form Rendition menu option should be available in RE3. When not installed, the Rendition menu options and customizations to the PTR editor window should not appear. FOP and XEP do not have this option available. Important: Note that the previous three CAB files have now been embedded within the .MSI file.
Implementation Notes: This feature requires a Requirements Editor Tool update.

Title Font Emphasis Has No Effect
Type: Defect Reference: 338459 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: Previously, when using the Title Font emphasis on text, it had no effect. The expected font change from Serif to Sans Serif was not occurring.
Solution: Now, when a Title Font emphasis is added to text, it changes the text from Serif font a Sans Serif font.
Implementation Notes: This feature requires a Requirements Editor Tool update.

OutputFormat printing issue addressed
Type: Defect Reference: 322811 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: The following issues were reported: Mapping "USA" to the "/Txn/OrgEstablishedState" enumeration printed USA on documents when selecting the "Texas" output format; the expected value should have been United States of America. Mapping "NT" to the "Txn/OrgEstablishedState" enumeration printed NW Territories on documents when selecting the "Texas" output format; the expected value should have been Northwest Territories.
Solution: The issues above have been resolved. The following now print correctly on all forms: United Stateds of America Northwest Territories
Implementation Notes: This feature requires a Requirements Editor Tool and Expere Engine update.

I-32 Defects

I-32 PDF Writer: Fractioned Font Sizes Issue
Type: Defect Reference: 362314 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: An issue was identified when using fractioned font sizes (9.5, 10.5, etc) where the text was not properly rendered in the output PDF file. Non-fractioned sizes (9, 10, etc) were rendering correctly.
Solution: I-32 Writer PDF was modified to handle properly rendering fonts with fractions.
Implementation Notes: I-32 Writer PDF update is required.

The effective date for all products within the scope of this document for this release is 11/25/2015 - 1/14/2016.

Requirements Editor Defects

OutputFormat printing issue addressed
Type: Defect Reference: 322811 Compliance Impacts: This defect is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Issue: The following issues were reported: Mapping "USA" to the "/Txn/OrgEstablishedState" enumeration printed USA on documents when selecting the "Texas" output format; the expected value should have been United States of America. Mapping "NT" to the "Txn/OrgEstablishedState" enumeration printed NW Territories on documents when selecting the "Texas" output format; the expected value should have been Northwest Territories.
Solution: The issues above have been resolved. The following now print correctly on all forms: United Stateds of America Northwest Territories
Implementation Notes: This feature requires a Requirements Editor Tool and Expere Engine update.