Create and Print Word Document saves as UID not Artefact name
We've just upgraded to RRC 4.0.1 from RRC 3.0.1.3 and have noticed a behaviour change.
When we use the Create and Print to Word option the resulting file name seems to be the underlying UID rather than the artefact number and name as it was before.
ie
3.0.1.3: Filename was 1234-_Artefact name.doc
now in 4.0.1 we get: _WpIPsItf....doc
This is causing confusion as you might expect as some are not renaming the resulting file to a sensible name at the time.
Is this now expected behaviour, can we change?
Thanks
Stephen Toop
When we use the Create and Print to Word option the resulting file name seems to be the underlying UID rather than the artefact number and name as it was before.
ie
3.0.1.3: Filename was 1234-_Artefact name.doc
now in 4.0.1 we get: _WpIPsItf....doc
This is causing confusion as you might expect as some are not renaming the resulting file to a sensible name at the time.
Is this now expected behaviour, can we change?
Thanks
Stephen Toop
One answer
Hi Stephen,
I have seen this issue occur once before. In that case, restarting RM resolved the issue. But before doing so, you might want to try to reinitialize the the publish service on the server.
To do this, open a browser window and navigate to https://server:port/rm/publish/initialize. If this is completed successfully, the following message is displayed: "Initialization Complete Successfully". They try to print again.
The rrdg.log which is used for the create and print reports might also have some information logged that might help identify the problem. The server logs (rm.log, jts.log) would also be a good place to check for messages as well.
I hope this helps.
I have seen this issue occur once before. In that case, restarting RM resolved the issue. But before doing so, you might want to try to reinitialize the the publish service on the server.
To do this, open a browser window and navigate to https://server:port/rm/publish/initialize. If this is completed successfully, the following message is displayed: "Initialization Complete Successfully". They try to print again.
The rrdg.log which is used for the create and print reports might also have some information logged that might help identify the problem. The server logs (rm.log, jts.log) would also be a good place to check for messages as well.
I hope this helps.