Known Issues in SDL LiveContent S1000D
This is a list of known issues in SDL LiveContent S1000D.
| Issue No. | Description |
|---|---|
| LCS-3791 | Microsoft Edge: Save Position is not working Issue: When viewing a publication in the Microsoft Edge browser, if you move or resize the browser window, click Save Position and close the publication, the browser does not restore the window's size and position when you next open the publication. Instead, the browser opens maximized in the default (upper left corner) position. Resolution: This is a known issue with the Microsoft Edge browser. For more information about this issue, refer to the following page on the Microsoft Support web site: |
| LCS-3395 | 'Or' in Categorical Search doesn't work correctly for multiple words from different categories In Categorical Search, using the Or operator with words from different categories causes some search results to be displayed under the incorrect category. |
| LCS-3388 | Revision Highlights report lists elements with ADD and MODIFY changes in different ways for Issue 3.0 In the Revision Highlights report for S1000D Issue 3.0, elements with a |
| LCS-3057 | Dialog buttons labels do not match labels defined is spec for issue 4.1 The labels for some dialog box buttons are not consistent with the labels defined in S1000D Issue 4.1. |
| LCS-3056 | Support Equipment Applicability Filtering does not consistently filter out support equipment Support Equipment Applicability functionality sometimes fail to correctly filter out support equipment. |
| LCS-2964 | "Target" field is set to "undefined" after editing and saving Bookmark/Note Target field is set to undefined after editing and saving a Bookmark or Note. Also, if you access the DM containing the edited bookmark or note and open the Bookmark/Note window, an undefined target is displayed (even without pressing Edit). |
| LCS-2843 | IPD Column heads and links are not consistent across S1000D Issue Illustrated Parts Catalog elements are not displayed consistently in some cases. |
| LCS-2798 | Procedural Step Number does not align with text when Procedural step has more than one para with applicability If a procedural step has more than one paragraph with applicability, the filtered view with the text of only one of the paragraphs displayed incorrectly shows the text one line below the Procedural Step number. |
| LCS-1876 | Setting applicability with large tables can cause empty table sections Some tables have failed to render properly when applicability is set, resulting in empty table sections. |
| LCS-1496 | PDM Stepping Back within a dmLoop. LiveContent S1000D provides the capability to step back to a previous troubleshooting step within a process data module. Also provided is the support from dmLoop elements, which provide authors the ability to iterate within a process data module. Under certain conditions attempting to move to a previous step within a dmLoop appears to fail. It is possible to create iterations within a dmLoop that processes variable values, but does not require user interactions. In this situation, going back to the previous step would reset the variable values, execute the process, and then move forward to the original (forward) troubleshooting step. |
| LCS-1495 | Undefined or Null PDM Variable Declarations. The S1000D specification provides a mechanism for resolving variable values that are undefined or null. A variable that is declared, but is not assigned a value at the time of declaration, should prompt the user with the dialog that is associated with the variable declaration. If no dialog is defined within the declaration, an error condition occurs. This capability has not yet been implemented in LiveContent S1000D. |
| LCS-1372 | Dialog boxes do not display when a variable is tested for <noValue>. |
| LCS-1279 | Certain entities in a DM cause errors during publishing. |
| LCS-752 | The back button loads the previous DM; however, it loads the first graphic, not the graphic that was displayed when leaving the DM. |
| LCS-671 | Adding applicability to paras contained in procedural steps introduces an "extra" carriage return in the step. Note that the first step does not have applicability on the Para. In the case of the second step, there are several possible paras, each of which has its own applicability. When the para is selected, it has an "extra" carriage return that causes it to be displayed 1 line below the number of the step. This appears to be a style sheet issue. |
| LCS-670 | When using the step mode in the viewer to navigate into a step with multiple figure references, the graphic window is updated to the last figure referenced in the step. This issue has been noted in versions 4 and Version 5 of Live Content. When using the step mode in the viewer to navigate into a step with multiple figure references, the graphic window is updated to the last figure referenced in the step, rather than the logical first figure. |