Send To-> Create New Document (OnBase 15) not available unless you have permission to create the document you are right clicking on (Unity Client)

[Chris_Farrell]

In the OnBase 15 Sys Admin MRG the following is stated on page 294 in the section on override permissions:

Note: If a user has both Create and Copy To Clipboard / Save As privileges for one
Document Type, the user can access the Send To | Create New Document right-click
option from documents in any Document Type. When the user creates a new document
using this option, only Document Types for which the user has Create privileges are
available to assign to the new document.

However, it appears that you have to have both create and save/as privileges on the document type you're right clicking on. (Unity Client)

Example: If you have Document A, B, and C. And a user group has the create permission overridden on document A (to disable it for Archive purposes) you can't use document type A to create document of type B via Send to-> Create New Document because the option is disabled.

Anyone know a way to work around this?

[Bryan_Hurless]

Hello Chris and thank you for using the OnBase Community,

There is a potential work around for this and it would require a Workflow System Task and Task List.

The User in question would also need the "Workflow" Client Based Product Privilege.

You would create a System Task with a Task list followed by the "Copy Document" and "Set Document Type" actions.

Any Document Types you add to the System Task will be eligible for this Task to be executed against.

As you can see in the example below, the currently logged in user does not have the "Create" privilege for the "Doc A" Document Type.

However this user can select one of the existing Document Types and run the System Task an create a new "Doc A" Document Type" based on the selected Document Type.

As you can see below a new "Doc A" Document Type was created with the Keywords from the selected "Doc C" Document Type.

You can also run this System task for the "Doc B" and "Doc A" Document Types.

I hope this helps!

Thanks again for using the OnBase Community!

[Chris_Farrell]

Hi Bryan, thanks for taking the time to respond but unfortunately this won't meet the needs of our users, and doesn't address the issue. We've got a generic document type that is an archive from our imaging system prior to OnBase. This document type is read-only. If there is a need to work on one of these documents, they need to be copied to a new document type in our taxonomy that the user does have access to create. The send-to functionality as worded in the Sys Admin MRG indicates this should work - it sounds like there's a defect here. If there isn't a way to work around the defect we'll look to create something in-house that allows us to accomplish this. We were hoping to not require workflow access for these users, but it sounds like we'll need to go that route until this is resolved.

Thanks.