nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Checked-out documents (originals) not visible in share

ph73nt

Dear list

I have a repository with two main folders (active and drafts), for document control. The philosophy being that new revisions of the active documents are "checked-out" into the drafts area and when they are approved, the new version can be checked-in.

My problem is that when I do this, the active document becomes invisible in Share and can only be accessed by navigating to the draft and downloading the older version. This is not the case in Explorer, where I can see the active version in its rightful place - which is what I'd like to do in Share.

Is there a fix for this wihthin Share?

Many thanks in advance, Neil

Find more posts tagged with

Comments

mikeh

It was a conscious design decision because our user testing discovered people were confused by the "Working Copy" label.

You can still get to the original document via the action: More / View Original Document.

Thanks,
Mike

ph73nt

Thanks Mike. Can I override this?

Neil

mikeh

You can remove the READ_LOCK filter from filter.lib.js in the Document Library repository webscripts. You might also want to override item.lib.ftl in the same place to not remove the Working Copy label.

Thanks,
Mike

ph73nt

Thanks, but…

Only a partial success. I was able to edit "item.lib.ftl", to which I replace the instance of "" with " (draft revision)" (which visually suits my needs).

I was, however, unable to find any files featuring the (case-insensitive) phrase "READ_LOCK." filters.lib.js (under slingshot/documentlibrary) contained a READ_ONLY_LOCK, but that sounds like something I want to keep. filter.lib.js (under components/documentlibrary) contained nothing of the sort.

I searched for all files containing "READ_" ending with .js (on Windows/NTFS (not my choice), hence case insensitive). Any other hints?

Thanks again, Neil

mikeh

It's the READ_ONLY_LOCK you want to remove (I was recalling it from memory).

Thanks,
Mike

ph73nt

I'm very impressed by your memory.

I have replaced

      var filterQueryDefaults =
         " -TYPE:\"thumbnail\"" +
         " -TYPE:\"systemfolder\"" +
         " -TYPE:\"fm:forums\"" +
         " -TYPE:\"fm:forum\"" +
         " -TYPE:\"fm:topic\"" +
         " -TYPE:\"fm:post\""; +
         " -@cm\\:lockType:READ_ONLY_LOCK";
‍‍‍‍‍‍‍‍‍‍

with

      var filterQueryDefaults =
         " -TYPE:\"thumbnail\"" +
         " -TYPE:\"systemfolder\"" +
         " -TYPE:\"fm:forums\"" +
         " -TYPE:\"fm:forum\"" +
         " -TYPE:\"fm:topic\"" +
         " -TYPE:\"fm:post\""; // +
         //" -@cm\\:lockType:READ_ONLY_LOCK";
‍‍‍‍‍‍‍‍‍‍

in the file …./tomcat/webapps/alfresco/WEB-INF/classes/alfresco/templates/webscripts/org/alfresco/slingshot/documentlibrary/filters.lib.js

This has solved the issue…. hope I don't lose some other functionality 😉

Neil