Known issues

Workarounds

The following issues in this release have workarounds.

Paste special dialog is not raised on dragging and dropping artifacts between modules (with Ctrl key held down)

First occurrence: 7.0.3

Internal ID: 139756

Problem: Paste special dialog is not raised on dragging and dropping artifacts between modules (with Ctrl key held down)

Workaround: Use the keyboard shortcut or mouse.

REST API request fails for artifacts that are upgraded from 6.0.6.1 to 7.0.2SR1

First occurrence: 7.0.2

Internal ID: 146514

Problem: REST API request fails for artifacts that are upgraded from 6.0.6.1 to 7.0.2SR1

Workaround: Add MD_ in front of Module URI for the REST request to work. For example, https://<hostname>/rm/publish/views?moduleURI=MD_nN51sdfEei2ou_dx66hBQ& viewURI=VW_yTsiR5EeqDQ613sCxIyA&projectURI=_AOnAOGen2aY6YDhQ&oslc_config. context=https%3A%2F%2F<hostname>%2Fgc%2Fconfiguration%2F54

Exporting specific module, exported ReqIF SPEC-HIERARCHY contains a "ghost" SPEC-OBJECT-REF that has no corresponding SPEC-OBJECT in ReqIF and no corresponding Artifact in DOORS Next

First occurrence: 7.0.2

Internal ID: 146619

Problem: We have a problem where a module is being exported as a reqIF and in the reqIF file there is a “ghost” SPEC-OBJECT-REF, meaning that the SPEC-OBJECT-REF has no corresponding SPEC-OBJECT in the ReqIF and also no corresponding Artifact in DOORS Next. The exported ReqIF also fails the DOORS Next ReqIF schema validation that takes place after export due to these issues.

Workaround: Remove ghost entry and export again

Print Req Specification w/ 'Include Attributes' does not print attribute ID if Portuguese language package is installed

First occurrence: 7.0.3

Internal ID: 147217

Problem: When printing a requirement by using Req Specification OOTB template with 'Include Attributes' option selected, in order to have the artifact attributes visible in the report document, the attribute ID is not printed in the report if ELM contains the Portuguese language package installed

Workaround: Not to have the Portuguese language package, which does not work much for Brazilian customers

Filter on enum 'attribute exists' shows artifacts with empty value in the result, for artifacts that still have a deleted value that is assigned

First occurrence: 7.0.2

Internal ID: 147304

Problem: Artifacts, which still have a deleted enum value that is assigned, will show up in the result, when adding a filter on 'attribute exists' for the relevant enum attribute. The artifacts show in the result with an empty value, so the users may think the results are incorrect.

Workaround: Change filter: 'AttributeX exists' to 'AttributeX is Any of' and select all values. Alternatively, saving an artifact will check and remove any invalid enum references. When you modify any attribute or content or description of the artifact and save it, it removes the invalid attribute reference from the artifact.

Users cannot import a ReqIF that creates new types if their role does not grant permission to create all artifact types

First occurrence: 7.0.2

Internal ID: 147367

Problem: A user imports a ReqIF that creates new types. The new types are created, but the import fails with a permission error because the user's role did not have full permission to create pre-existing artifact types. If the user was assigned a role that has full permission to create all artifact types, then the import succeeds, even though we're dealing with all new types.

Workaround: Temporarily grant all create artifact permissions before the import. After a failed import, fix the permissions and then try again

The ReqIF import wizard displays the attribute name as Identifier instead of REQIF.ForeignID

First occurrence: 7.0.2

Internal ID: 147379

Problem: The ReqIF import wizard displays the attribute name as 'Identifier' instead of 'REQIF.ForeignID', causing the attribute value to become null.

Workaround: Import in a new component works fine and shows the value attribute

PermissionsForbiddenException while trying to modify an artifact type in project using a master process and modified local permissions

First occurrence: 7.0.2

Internal ID: 147468

Problem: PermissionsForbiddenException while modifying an artifact type in project using a master process and modified local permissions

Workaround: If the user clicks the Requirement's Edit icon and selects "Edit Attribute" then modify the type from Requirement to Information, then it works.

Using copy/paste in a table inside an artifact creates a new table row, when using Chrome and Edge browsers.

First occurrence: 7.0.2

Internal ID: 147542

Problem: When using copy/paste of the whole content in a table within an artifact, instead of the content being pasted into the selected table cell, a new table row is created with the content pasted in the first column. If the content is pasted into the first column of the table, the new row is added above the selected row. If the content is pasted into the second column of the table, the new row is added below the selected row.

Workaround: If only a subset of the cell content is selected, for example all characters except the last character, then the copy/paste works as expected for those characters and then the user only needs to type in the last character again.

Second ReqIF Import Fails When Module Is Deleted and ReqIF File Contains Same Specification/Module ID and Spec Object ID but Modified Spec-Hierarchy

First occurrence: 7.0.2

Internal ID: 147780

Problem: When users import the ReqIF file, the import report does not show any obvious errors, but the module does not come through.- The module was already imported some time ago via a different ReqIF and then was deleted. Now, when we import the later ReqIF, it is supposed to "resurrect" the module, but nothing happens and no error in the report. Both ReqIF has same specification identifier and spec object identifier but different Spec Hierarchy. Hence, when trying to re-create module structure binding it is giving an internal error which can be found in logs .

Workaround: As specification was existed in configuration and being recreated on reqif import possible workaround might be to move into new configuration.

DB2: Link exists/Not exists filters are slow (or timeout) in modules

First occurrence: 7.0.2

Internal ID: 147745

Problem: Slow view execution, sometime resulting in timeouts.

Workaround: Simplify the view and/or increase client timeout to allow view to complete.

Deleting multiple artifacts in a module with a filter applied fails with BulkedOperationException

First occurrence: 7.0.2

Internal ID: 147016

Problem: In a module with deep hierarchy (module structure is in the stack trace below), there is a need to remove certain artifacts from the module which match a specific String-based attribute value. When a filter is applied to display these artifacts (e.g. attribute 'Role' contains "Classified") and each artifact in the resulting page is selected, the removal operation fails with no obvious error message presented on the screen. The rm.log produces the below stack trace referencing a BulkedOperationException, along with a 400 (Bad Request) response returned to the web UI. The artifacts are not removed from the module.

Workaround: Delete the objects in some other way, like doing it manually.

Wrapper resource are not updated in ReqIf re-import.

First occurrence: 7.0.2

Internal ID: 147765

Problem: The wrapper is not updated during the re-import of a ReqIF file if the package only contains a CSO mapping.

Workaround: There are timeouts in the GC and baseline cases.

Applying a project template should not recreate incoming links from project areas that are not associated with the current project

First occurrence: 7.0.2

Internal ID: 147924

Problem: Applying a project template should not re-create incoming links from project areas that are not associated with the current project. The lack of an association can cause problems, such as improper backlink removal when the outgoing link end is deleted.

Workaround: Simply creating an association between the two projects at any time before link deletion prevents the broken-backlink problem, as the backlinks would get deleted automatically.

ReqIF export skips resources with malformed URLs

First occurrence: 7.0.2

Internal ID: 147874

Problem: When an artifact contains malformed URL, ReqIF export skips such resources from the ReqIF file. This is not clearly indicated in the Export dialog. Also, while the generated ReqIF file skips representing the resource under SPEC-OBJECT, it retains reference to the skipped SPEC-OBJECT under SPEC-HIERARCHY.

Workaround: Correct the URL and export.

DOORS Next modules display wrong images after ReqIF import

First occurrence: 7.0.2

Internal ID: 146111

Problem: When DOORS Next exports ReqIF with images, the image have distinct filename.

Workaround: Change the name of file in ReqIF as well in directory and giving unique names to file will work.

Limitations

The following issues in this release do not have workarounds.

Oracle: Link Exists view filters with extra filters on linked artifacts are slow or timeout on Oracle

First occurrence: 7.0.2

Internal ID: 146476

Problem: When a view contains a Link Exists filter with additional filters for linked artifacts, processing such a view may take a lot of time and may result in timeout.

Filter on a string attribute that has an rdf uri assigned causes the module to load empty in a changeset or when navigating back to the module

First occurrence: 7.0.2

Internal ID: 147989

Problem: When filtering on a string attribute with 'attribute contains' some text or a word, the initial result is OK. But when then creating a changeset or navigating to another page in the same tab, and then back to the module again, the module shows up empty and the display for this module seems completely confused, especially if you also show the attribute in the grid view.

ReqiF Import fails with the Error importing artifact. Propagated exception - duplicate key value

First occurrence: 7.0.2

Internal ID: 147996

Problem: ReqIF Import fails with the Error importing artifact. Propagated exception - duplicate key value

RTF file fail to display in module view when uploaded

First occurrence: 7.0.3

Internal ID: 148014

Problem: ReqIF package includes several OLE objects, but some do not display correctly when imported into DOORS Next. Additionally, the same .rtf files in the package fail to open in Word, although they can be accessed in Word pad by selecting the Unblock and Show All Content options. The same issue occurred when .rtf files are uploaded through the Upload Artifact option and viewed in module view. While the ReqIF package appears to be valid, it seems the problem is related to how the content is previewed in module view. Issue seems to be happening with only some of the objects being imported.

Need to document: in link columns, showing custom attribute values of artifacts at the other end of cross-server links is not supported

First occurrence: 7.0.2

Internal ID: 148017

Problem: Documentation page Filtering artifacts for links to other applications (https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/doors-next/7.0.2?topic=artifacts-filtering-links-other-applications) says this about the Format feature:Use the Format option to customize the column display. You can select attributes of the artifacts and wrap or trim the link text display.However, the is not fully supported for cross-server links. We don't show custom attributes in that section for cross-server links. We should add a sentence after the preceding Format feature that says as much. Even something like "Custom attribute values are not shown for cross-server links" should be good.

Artifact in the preceding documentation module is deleted during reqif import if there is a change in the Module hierarchy.

First occurrence: 7.0.2

Internal ID: 148027

Problem: Artifact in the module is removed during ReqIF import in the update operation, if there is a change in the Module hierarchy.

ClassCastException thrown on delivering link whose type is changed in both source and target

First occurrence: 7.0.2

Internal ID: 148014

Problem: ClassCastException is thrown on delivering link whose type is changed in both source and targetjava.lang.ClassCastException: com.ibm.rdm.service.links.model.impl.Link is incompatible with com.ibm.rdm.service.artifacts.model.IArtifact

ReqIF reimport without TOOL-EXTENSIONS displays image link instead of image

First occurrence: 7.0.2

Internal ID: 148033

Problem: DOORS Next ReqIF Import incorrectly imports image when TOOL-EXTENSIONS are removed

Activity reporting REST API is not correctly returning all of the modified artifacts for a user

First occurrence: 7.0.2

Internal ID: 148047

Problem: When getting the artifacts modified for a specific user, the artifacts are not being returned IF the artifact was modified by another user within the same date and time range.

Satisfied By Architecture Element links are not exported from a baseline in a non IBM Content Manager project

First occurrence: 7.0.2

Internal ID: 148053

Problem: Satisfied By Architecture Element links are not exported from an artifact from a baseline. DOORS Next project is non-configuration management enabled. This behavior seems to be only for Rhapsody® Model Manager links, while the same behavior for links to Engineering Test Management, Engineering Workflow Management and within DOORS Next itself works.

Artifacts shown in Links Explorer that are cross-server cannot be expanded to show their links, and links can't be created from them

First occurrence: 7.0.2

Internal ID: 148057

Problem: This defect asks that we document a limitation for the Links Explorer. See the below documentation on how it works:https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/doors-next/7.0.3?topic=artifacts-links-explorerA note of some kind should be added to that documentation stating that artifacts that belong to another DOORS Next server can neither be expanded to show its links, nor can you create links from them. Both abilities are described in that documentation, so we simply need to mention that neither of those two features can be done for artifacts that exist on another server.

Setting link validity from the grid view on base linked artifact results in the selection being ignored or not set

First occurrence: 7.0.2

Internal ID: 147987

Problem: Attempting to set the link validity from the DOORS Next grid view using the configure page option to set the validity for one or more artifact doesn't not update the validity status. The link that cannot change validity for has a blue arrow in the icon. That means it is a link on the base artifact. This scenario is reproducible once you have a base link like that set up. Doesn't matter if you select a single row or multiple rows. It works, however, if you change the validity from the Links section on the right. It also works if you click on the suspect icon directly on the link it self in the grid view. This issue doesn't appear to be related to artifact links that are link to non-base artifacts.

Changeset might not be delivered because of a "Module Not Found" error

First occurrence: 7.0.2

Internal ID: 147982

Problem: Changeset Unable to be Delivered that use custom delivery and with "preview" option selected due to Module Not Found Error.

Incoming Link Index Provider links not present in RRDG doc report

First occurrence: 7.0.2

Internal ID: 147979

Problem: If a report is generated against a view that shows incoming links which Link Index Provider provides, those links are not present in the generated report.

Need to document that GCM is required in order to clone artifacts

First occurrence: 7.0.2

Internal ID: 147978

Problem: The below documentation section should mention that a running Global Configuration Management server is required in order to clone artifacts:https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/doors-next/7.0.2?topic=components-cloning-artifacts-betweenOne good location might be in the "Before you begin" area, where we list prerequisites. Basically, cloning requires that a Global Configuration Management server is running and reachable. In case it helps, this is the wording we use in our error message when a clone is attempted and the GCM server is not available for whatever reason:"The artifacts cannot be cloned because the Global Configuration Management application is not installed correctly."Only a single sentence is required for this. We need it documented somewhere that this is a requirement.

Conflict on modified binding artifacts is not reported when checking the Compare of a module

First occurrence: 7.0.2

Internal ID: 147971

Problem: In project created in 702ifix030, conflict on modified binding artifacts not reported when checking the Compare of a module.

Unable to upload a new image when generating a report for a review

First occurrence: 7.0.2

Internal ID: 147969

Problem: When generating a report for a review, if you choose to add a logo image, you are only able to select images that were already uploaded.This is because the "Upload a new image..." link is unresponsive.

CSV Export - links can show incorrect module ID when their cell contains links to/from bindings from different modules

First occurrence: 7.0.2

Internal ID: 147948

Problem: When exporting a view to CSV/XLS, if an artifact has links to bindings from different modules, an incorrect module ID can be used for some of the links.This was recently fixed for the case where there was only a single link, or multiple links to bindings from the same module (see 146908).But this appears to be an edge case.

When duplicating an artifact with a Validated By link, if the user isn't a member of that Engineering Test Management project, the link won't be duplicated on Engineering Test Management side, but DOORS Next will still create a backlink (opt-out only)

First occurrence: 7.0.2

Internal ID: 147917

Problem: When duplicating an artifact with a Validated By link, if the user isn't a member of the related Engineering Test Management project, the link won't be duplicated on Engineering Test Management side, but DOORS Next will still create a backlink. The problem only exists in an opt-out context (i.e., not Engineering Test Management-Enabled)

Full DCC ETL is slow

First occurrence: 7.0.2

Internal ID: 147910

Problem: A full load for the DOORS Next DCC job takes over 48 hours to run at the client site. This is longer than their maintenance window, so the customer has ended up in a state where the data warehouse isn't usable and they can't (or won't) dedicate the downtime that is required to bring it back.

ReqIF reimport without TOOL-EXTENSIONS displays image link instead of image

First occurrence: 7.0.2

Internal ID: 148033

Problem: DOORS Next ReqIF Import incorrectly imports image when TOOL-EXTENSIONS are removed.

Lack of robustness when applying project templates - artifact templates can end up having undefined/incorrect types and formats, if the originals have pre-7.x URLs

First occurrence: 7.0.2

Internal ID: 148003

Problem: If a project template contains an artifact template whose type URL or format URL is from pre7.x, then the resulting artifact type or format will be undefined. Specifically, a customer's project template had artifact templates with type URLs that had missing prefixes. And the formats had unique URLs, as opposed to generic URLs. The apply-template code is not able to find matches for these URLs, so they are left as-is, making them essentially undefined.

Failed to create the asset folder due to a parent folder is gone exception and ReqIF import failure.

First occurrence: 7.0.2

Internal ID: 147896

Problem: ReqIF import failed as the system mightn't create the asset folder due to a 'parent folder' gone exception.

Reusing attributes not updated when importing a reqif file

First occurrence: 7.0.2

Internal ID: 146582

Problem: When importing a ReqIF, the attribute values from the reqif be should be updated when artifacts are being reused.

DB2: View timeouts with "Link does not exist" filters

First occurrence: 7.0.2

Internal ID: 146477

Problem: Customers may experience DN Web client timeouts when filtering on tags in module and artifact grids.

Identifier [xxxx]' not valid during export of ReqIF file

First occurrence: 7.0.2

Internal ID: 145379

Problem: Error message is displayed on exporting or downloading the ReqIF file.

[Design defect] Module structure wrong after changeset delivery if there are newer structural changes available in the source stream

First occurrence: 6.0.6

Internal ID: 142909

Problem: If you select a subset of change sets to deliver rather than delivering all changes, the system may put artifacts into a different location in the module than the user expects.

[Design Defect] audit history performance - on large modules with lots of audit history, the initial load and each subsequent page change take a long time (2.3 minutes per page) and no information appears to be cached

First occurrence: 6.0.6

Internal ID: 124766

Problem: On large modules with lots of audit history, the initial load and each subsequent page change take a long time (2.3 minutes per page) and no information appears to be cached

Limitation - artifacts shown in Links Explorer that are cross-server cannot be expanded to show their links, and links can't be created from them

First occurrence: 7.0.2

Internal ID: 148057

Problem: This defect asks that we document a limitation for the Links Explorer. Please see the below documentation on how it works:https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/doors-next/7.0.3?topic=artifacts-links-explorerA note of some kind should be added to that documentation stating that artifacts that belong to another DOORS Next server can neither be expanded to show its links, nor can you create links from them. Both abilities are described in that documentation, so we simply need to mention that neither of those two features can be done for artifacts that exist on another server.

Validated By links do not appear after drag and drop from Engineering Test Management

First occurrence: 7.0.3

Internal ID: 147838

Problem: When dragging test cases from Engineering Test Management to link to an artifact in DOORS Next, the links don't always appear. The link is created though and a manual refresh will show it.

Audit History report only displays 25 entries.

First occurrence: 7.0.2

Internal ID: 147801

Problem: Audit history report only contains 25 entries, when changes are more that 25 then only it shows 25 entries.

Missing artifacts and vertical scroll bar when filtering binding artifacts with link column set with workflow attribute

First occurrence: 7.0.2

Internal ID: 147754

Problem: Missing artifacts and vertical scroll bar when filtering binding artifacts with link column set with Format = workflow attribute

Accessibility - keyboard shortcuts to access the CKEditor toolbar were removed

First occurrence: 7.0.2

Internal ID: 147719

Problem: When editing the contents of an artifact in a module grid, users can no longer access the CKEditor toolbar via keyboard shortcuts.

ReqIF import fails with warning and module does not exist after the import

First occurrence: 7.0.2

Internal ID: 147708

Problem: ReqIF import with warning and module does not exist after the import

Value of enum attribute in artifacts are reset incorrectly during import

First occurrence: 7.0.2

Internal ID: 147687

Problem: If an enumerated attribute data type is edited in target project area, to remove and re-add a value, subsequent imports might be affected. Artifacts have the value that was removed and re-inserted might be reset.

Repotool command rmPurge fails with RuntimeException: TRS services are not available. Repair is not possible.

First occurrence: 7.0.3

Internal ID: 147673

Problem: The below Repotool command fails, apparently due to DMT/TRS Services not initializing properly ../repotools-rm.sh -rmPurge fromFile=/tmp/fromfile.txt

Using OSLC API to create an artifact, POST to the creation factory results in two identical error messages in the rm.log, although the artifact is created

First occurrence: 7.0.3

Internal ID: 147634

Problem: For an opt-in project, when creating an artifact through OSLC API two identical error messages are added to the rm.log:ERROR oh6todo - vvc.mapping.changeset should not be replaced. Current: _tJEJ0Ej7Ee-5DY4Knxy5kw. Replacement: _tL1J8Ej7Ee-5DY4Knxy5kw.The artifact is created, so it's not obvious if there was an actual error.

Event mode: baseline selections might receive shapes from the parent stream

First occurrence: 7.0.2

Internal ID: 147548

Problem: When the baselines are created, it is possible for the stream shapes to be included in the baseline selection. This is incorrect and results in the TRS validation flagging these shapes as extras.

The file name for the preview image of a DOORS Next diagram does not match between the zip container and the ReqIF file.

First occurrence: 7.0.2

Internal ID: 147499

Problem: The file name for the preview image of a DOORS Next diagram does not match between the zip container and the ReqIF file.example: in ReqIF file: object data="xxx.png_alternative_image.png"in zip container: xxx_alternative_image.png

View filter using server's hostname in RDF URI is lost after server rename

First occurrence: 7.0.2

Internal ID: 147428

Problem: If server URL is used in RDF URI for an attribute definition, and a condition on this attribute is defined for a view, then, after a server rename, the view will no longer have the filter condition on that attribute

The Change Sets tab of a stream can be empty if some change sets are linked to work items from a third-party Engineering Workflow Management server

First occurrence: 7.0.2

Internal ID: 147164

Problem: When looking at the Change Sets tab of a stream, if there are work items linked to the change sets, and some of the work items' titles that are returned by the Engineering Workflow Management server don't start with a work item ID followed by a colon, then none of the change sets will get shown.

Linked artifact enumeration conditions lost when saving a view

First occurrence: 7.0.2

Internal ID: 147148

Problem: When saving a filter with a Linked Artifact section and enumeration filters in it, the enumeration conditions are lost when saving as a view.

Quick Search can show bindings that are not referenced by an existing module

First occurrence: 7.0.2

Internal ID: 147108

Problem: In the case where a binding exists that is not referenced by an existing module, that binding will still get shown in Quick Search's results. The result's Module attribute is shown as being blank, and clicking the binding link opens the “We’re Sorry… cannot be found…” page.

Custom Review reports appear in "Generate Module Report For View" + "Generate Report For View"

First occurrence: 7.0.2

Internal ID: 147082

Problem: Custom Review reports appear in "Generate Module Report For View" + "Generate Report For View"

When printing a module, a wrong link is generated for an embedded artifact that resides in a different project area

First occurrence: 7.0.2

Internal ID: 146855

Problem: When printing a module, a wrong link is generated for an embedded artifact that resides in a different project area.The link for the embedded artifact references the stream if of the parent artifact, instead of referencing the stream id of the embedded artifact itself.

Oracle: View timeouts that use tag filters in an all artifacts view for large components

First occurrence: 7.0.2

Internal ID: 146847

Problem: Create a view in the All Artifacts tab. Add a filter for "Tag is any of". The performance of this view degrades as the total number of versions in the component increases. See attached SQL/explain plan. The query uses a component_id predicate instead of a config_id predicate. In the customer case, the number of versions in the component was more than 4 million.

No warning about Link Constraints preventing creation of DOORS Next links between two DOORS Next servers

First occurrence: 7.0.2

Internal ID: 146796

Problem: When trying to create a Link when a Link Constraint is defined between two servers that use the add link option, there is no error message stating this operation is not supported as the Link Constraint is enforced. Drag and drop however produces a warning.

ReqIF import does not update Enum values on the artifacts that are imported in the second ReqIF

First occurrence: 7.0.2

Internal ID: 146790

Problem: ReqIF import does not update Enum values on the artifacts that are imported in the second ReqIF, when using a mapping context

If we changed Attribute when exchanging a ReqIF file, strange values are entered.

First occurrence: 7.0.2

Internal ID: 146205

Problem: When the attribute is changed on exchanging the ReqIF file, the changes are not reflected in the Attribute of the second project and some strange data value is entered.

DOORS Next Audit history page is showing incorrect translation for "Past week" and "Past month"

First occurrence: 7.0.2

Internal ID: 145767

Problem: In DOORS Next's Audit History page, there are options to display "Today", "Yesterday", "Past week", Past month".

Error when sharing a folder view with process role name that contains special character (&)

First occurrence: 7.0.2

Internal ID: 143961

Problem: Error when sharing a folder view with process role name that contains special character (&)

Navigating to DOORS Next from JRS by clicking a module artifact does not focus on the right artifact

First occurrence: 7.0.1

Internal ID: 143237

Problem: We have a problem where when we click on a module artifact from the JRS report, though the module is opened and the right artifact is selected, the focus is not on the selected artifact. So it is confusing for the user to know if the right artifact is selected or not.

"Target with changes" for module Compare does not always show the proper delivered data

First occurrence: 6.0.6

Internal ID: 142913

Problem: "Target with changes" for module Compare does not always show the proper delivered data

rm log contains ERROR m.ibm.rdm.fronting.server.services.RMBridgeService - Service Error: Unable to resolve expected configuration

First occurrence: 7.0.2

Internal ID: 141823

Problem: The rm.log has several instances of this error2

021-07-08T18:32:50,307 [TID: 750DB9A9][rene.morrow] [WebContainer : 2 @@ 18:32 
<unauthenticated> <Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
 Chrome/91.0.4472.124 Safari/537.36 Edg/91.0.864.64@9.42.75.198> /rm/operations] 
ERROR m.ibm.rdm.fronting.server.services.RMBridgeService - Service Error: Unable to resolve expected configuration

.

Blank gaps in module due to improper handle of page requests

First occurrence: 6.0.6

Internal ID: 137942

Problem: Under certain scenarios, the module displays blank gaps

System-defined attributes and types that are translated to browser's language/locale of first login after server restart

First occurrence: 7.0.3

Internal ID: 147856

Problem: When a project is created, the system-defined attributes and types are defined in the same language as browser's, and if browser's language/locale is changed, the attributes should remain in the language that is used upon creation. The issue is that if server is restarted, the attributes will translated to the browser's language of the first user to log in, and will remain in that language until next restart.

UI defect reported by users on 'Boolean' attribute type's check boxes

First occurrence: 7.0.2

Internal ID: 147742

Problem: Users are confused by the check boxes when editing Boolean attributes. The check boxes are a representation of the attribute's value (empty box for "no value" or "false"; checked box for "true"), but users may think that the boxes are used to set the value that is the users may think that clicking the empty box for "false" would mark the value as "false", when it changes the value to "true".

Ampersands (&) are allowed in RDF URIs, but you cannot create link constraints with artifact types that have them

First occurrence: 7.0.3

Internal ID: 147664

Problem: We currently allow type RDF URIs to have ampersands. However, if you try to create a link constraint with an artifact whose RDF URI has an ampersand, the link constraint fails to save, due to a SAXParseException.

Translation error on the dash board widget comment in German, "an" expected instead of "bis"

First occurrence: 7.0.2

Internal ID: 147223

Problem: Translation error on the dash board widget comment in German

ReqIF import should be able to import U+0093 and possibly other Unicode control characters

First occurrence: 7.0.2

Internal ID: 145597

Problem: Importing a ReqIF (delivered by customer) leads to an incorrect encoding in DOORS Next for characters within the character code area ca. 145 – 155.