Is there a way to make the Previous Value/New Value links in a generated DNG Audit History Report actually work?
We have DOORS Next Generation version 6.0.3 and are trying to generate an 'Audit History Report' using the Reports -> Generate a report -> 'Audit History' option. After going through the wizard and selecting all the settings, we generate the report. When looking at the output we see that most of the Primary Text fields have hyperlinks in the 'Value' column with links to see the Previous Value and the New Value. Clicking on these links yields an error instead of allowing us to see the previous or new values. The error we get is:
The artifact, https://...resources/CA_16b... , was not found in the repository.
ID CRRRW7283E The project that contains the artifact might have been deleted or archived, you might not be a member of the project,or the artifact might not be visible in the current configuration. Verify that the artifact exists, that you are using an appropriate configuration, and that you are a member of the project.
The artifact hasn't been deleted and we don't have any streaming going on in RM. Is there any way to get these links to show actual data instead of the error? Is this a bug in the report template on the server and is there a fix for it?
Thanks,
Jamie.
2 answers
Hi,
If you generate your report to Word or Excel, you might face this problem:
https://stackoverflow.com/questions/25070176/hyperlink-changes-from-to-20-20-when-clicked-in-excel
Try to copy the link generated and paste it in your browser to check if it works.
If it works, then generating your report in PDF might be a solution.
If it doesn't, sorry, I'm not sure I can help you more.
Cheers,
Nico
Jamie, I suggest you contact IBM Support to get it investigated further, as it is likely a defect.
It is easy to reproduce, the embedded links are correct in that they return the correct content in RDF/XML format, when used in a REST client. But when accessing such links in a browser, they would get redirected and eventually show the error that you see. It may have something to do with Configuration Management, regardless the project is CM enabled or not.
An example in my environment, the embedded link is
https://clm603.example.com:9443/rm/resources/_8d71b3c40ae84dee87ecf70a992a8070?revision=_eb4wEQjwEeePre_VWPaB3A
It will return the correct content when used in a REST client or the RDNG debug service.
After a couple of redirection, the below link is sent to the server and results in a 400 error.
https://clm603.example.com:9443/rm/resources/_8d71b3c40ae84dee87ecf70a992a8070?revision=_eb4wEQjwEeePre_VWPaB3A&vvc.version=true&&dojo.preventCache=1497415457904