You are viewing limited content. For full access, please sign in.

Question

Question

"how do I return an error?"

asked on April 3

If I need to prevent the user from doing something and I cannot prompt the user is there a way to raise an error message when they try to do it?

0 0

Replies

replied on April 3

Can you be more specific to what you are trying to prevent someone from doing?

0 0
replied on April 3

I am hoping to prevent authorized users from moving documents into inappropriate folders based on metadata. I would like to block "bad" moves but raise some type of notice that the process is "not permitted" rather than just failing to occur.

0 0
replied on April 3

You're probably better off writing a workflow to move/file your documents based on metadata if that's your main concern, as it removes any chance of human error.

0 0
replied on April 11

Thank you for the suggestions, but I am not trying to create my set, I am working to prevent folks from accidentally altering the existing structure without tying their hands with security by restricting the rights.

I read about a scheme some years ago to do what I am trying to do. The idea was to prevent authorized users from misfiling for example, a confidential document into a public folder by utilizing a "Security Level" value. So, assuming 1 is public and higher numbers are more secure, the idea was to never allow a document to move into a folder with a lower security value or never allow a folder to move into a folder with an equal or lower value. 

I am trying to prevent click and drag errors that we see frequently causing folders to end up under a neighboring "peer" folder. My question here was aimed at raising an error in lieu of a message box since that is not an option in Workflow. This, so that they would realize that the action was blocked for a reason. If it is actually legitimate, then they need to reset the security level before proceeding.

0 0
replied on April 14
0 0
replied on April 16

Thank you, Brian! That was a big help, and I am very glad to know of that solution. I have now tested it, and I think I might still have problem. I am trying to prevent folks from accidentally doing a "click and drag" that places a folder under its peer or lower. For security, the issue is a little different. Since the peer is at the same level, moving something into a peer folder at the same level, would not trigger the system to block the move. I need to block "equal to or less than" the security only blocks "less than". I don't know if there is a way to alter that behavior.

0 0
replied on April 18

Right, our classification levels system is designed to prevent placing higher classified entries into lower classified folders. There isn't a way to block the action when the entry and folder have the same classification level.

0 0
replied on April 8

If we're talking about users moving entries using the web or Windows client, then the ability is either allowed or disabled. If it is disabled, there isn't any explanatory text. Some actions have an "are you sure" dialog, but there isn't an opportunity for you to provide your own text for that. A workflow could only be involved after the user has successfully moved the entry, and has no way of communicating back to the user.

It seems like the best options are either: 1) if possible, remove users' rights to move the entries in question, and rely entirely on automated filing or 2) have these moves trigger a workflow that could potentially place the entry back in the correct location in the event it was moved to an inappropriate folder.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.