Post

2 followers Follow
0
Avatar

Business rule fails when non-license user updates progress

I have a Task business rule that colours $C_CLZ_TeamTaskColor_CLZ based on $Tasktype.

This is set to run "Every time a record is created or edited" in certain projects. As I want to make sure any updates are caught.

However, if an e-mail user updates press on a task, I get the following error:

"An error occurred while executing action '1 - Update Field' in a configuration named 'Sets Team Board colour based on task type': User not authorized for operation Update on Desktop HTML/CSS by license type."

So I need to sort of criteria like

Not(CurrentUser().Licensed) - so that the rule will not run if a non-licensed user updates anything on the task.

Any hints?

Peter Fjelsten Answered

Please sign in to leave a comment.

7 comments

0
Avatar

It looks like the system is taking this action as a way to circumvent the licensing since email-only users cannot update fields other that percentage completion and a few others. Does this rule need to be real-time or can you use a scheduled workflow rule?

Josh Santos 0 votes
Comment actions Permalink
0
Avatar

Well, I suppose it does not have to happen immediately, but we only have limited scheduled workflow rules.

I guess it's a bug because, the users is not changing anything else than hours/remaining effort/complete/notes in the upodate form.

Peter Fjelsten 0 votes
Comment actions Permalink
0
Avatar

Can you open a support ticket for this?  We'll see what R&D's feedback is.

Josh Santos 0 votes
Comment actions Permalink
0
Avatar

I'm getting the same thing on a workflow rule in our system, too.  Our workflow is called "HelpDesk: Update task resolution, item, assigned, work task type from Issue."  We've gotten four errors today triggered by user emails.  The error says it occured while executing action '2.1 - Update Field' and the reason is "User not authorized for operation Update on [whatever the user put in the subject line of the email] by license type."

Druckenmiller, Chris 0 votes
Comment actions Permalink
0
Avatar

I believe this was confirmed to be a bug and is already scheduled to be addressed in an upcoming patch.

Josh Santos 0 votes
Comment actions Permalink