09-01-2016 06:48 AM
Hi,
I just ran across an issue with one of our custom Unity API applications that does keyword modifications. I found the cause of this issue explained in the blog post "Modifying Keywords through the Unity API in OnBase 16" and saw the change that was being made to address this issue from within workflow with Unity Scripts but I'm trying to see what work around (if any) can be used for external API applications. The quick fix would be to grant the modify keyword permission but in doing so would also allow users to modify the keywords (any keywords on the doc type) from within any client as well since they also have access and needs to retrieve these documents from within the OnBase client(s). This custom application allows keyword modification in a controlled setting so they are only able to modify specific keywords. Just trying to get some other ideas/thoughs if someone else has ran into similiar issues.
Thanks
Anthony
09-01-2016 07:24 AM
We're not on OnBase 16 yet, but I've been following that thread with interest. I understand the security implications of the old behavior, but it seems like a significant breaking change.
For the current behavior, I can think of two solutions that I don't like:
I think a reasonable solution would be for Hyland to make two changes:
09-01-2016 07:13 AM
09-01-2016 07:24 AM
We're not on OnBase 16 yet, but I've been following that thread with interest. I understand the security implications of the old behavior, but it seems like a significant breaking change.
For the current behavior, I can think of two solutions that I don't like:
I think a reasonable solution would be for Hyland to make two changes:
09-01-2016 08:04 AM
09-01-2016 08:40 AM
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.