 |
The effective date for all products within the scope of this document for this release is 01/15/2016 - 04/08/2016.
| New Element for Doc Viewer text display only |
|---|
|
| 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. |
| Build/Assembly Transaction when Unused Rules Exist |
|---|
|
| 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:
|
| Implementation Notes: This requires a Requirements Editor update. |
| New Element for Doc Viewer text display only |
|---|
|
| 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. |
Support was implemented for supplying a predefined document print order in the PacketType\DocumentRefs element.
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.
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.
<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.
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.
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’).
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.
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.
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>
An issue was identified while opening a compare dictionary:
Error: An error occurred comparing data dictionaries. Index was outside the bounds of the array.
The solution required changes to the Data Dictionary Viewer.
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.
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’.
Modified Outline.cs file to include ID display.
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.
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.
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.
The Renditional Web Services addresses have been updated to the most current addresses, eliminating the need to manually look up and update the them.
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)
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.
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.
The TaglineSeparatorLine attribute has been added to the Document element, providing the ability to suppress printing the Tagline separator line.
Resolved an issue where Raw XML was displaying when editing the contents of an element that included text and a data item (DTA).
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).
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.
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.
Now, When users perform a Save As command with read-only files, the new file is editable.
The file ‘Type’ description for Requirements Editor files when browsing using Windows Explorer was spelled incorrectly as ‘Requiements Document’.
Corrected the spelling to be ‘Requirements Document’.
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.
Modified fields in PTR Editor to allow scrolling and copy/paste when file is Read Only.
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.
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.
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…
A problem occurs if the folder RequirementsEditor does not exist under users\Appdata\Local\Temp directory. A check was added to see if the directory does not exist and creates it if not found.
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.
A setting was modified in the isolated shell to show project name before tool name, which was not set previously.
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.
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.
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.
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.
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.
All Inactive content is omitted in the PDF Outline
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.
Code was modified to remove the ability to add attributes or child elements to content references.
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.
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.
For Internal installations only:
Previously, the E-Form Rendition package was always intalling, even after choosing Make Unavailable in the Advanced install options.
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.
Now, when a Title Font emphasis is added to text, it changes the text from Serif font a Sans Serif font.
Users reported that the ancillary barcode printed over the document tagline on certain documents from the October content release.
There was a change made to the WKFS_StyleGuide. Now the barcodes will no longer render over the top of a footer or tagline.
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.
The Content stylesheet was modified to correct the issue. Now, if emphases are wrapped around the content, the information prints as expected.
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.
I-32 Writer PDF was modified to handle properly rendering fonts with fractions.
The following issues were reported:
|