Welcome, Guest
Username: Password: Remember me

TOPIC: Security in workflow

Security in workflow #1808

  • Jlopez
  • Jlopez's Avatar
  • Fresh Boarder
  • Posts: 1
  • Karma: 0
We have a request to prevent some people to view others worklists. We are using the older 360 version of the software.
On the workflow screen the the "User" field has a dropdown list that the worker can select another worker and see their worklist. They want to disable this for some workers.
I have looked at using function rights and looked at security levels but have not had any luck.
Any ideas on how this could be done?
The administrator has disabled public write access.

Security in workflow #1809

  • ddozer
  • ddozer's Avatar
  • Senior Boarder
  • Posts: 51
  • Karma: 0
Depending on the nature of the requests you could maybe set the security level to private so that only the current actor and the resource in emplyee ID can see the request. This may limit it too much though if there are others that still need to access the request.
The administrator has disabled public write access.

Security in workflow #1814

  • Dkloepfer
  • Dkloepfer's Avatar
  • Expert Boarder
  • Posts: 92
  • Thank you received: 2
  • Karma: 0
You may also set the requests to have a Project Security Level (by hardcoding a project in the request). This would allow only members of that project the ability to see the requests.

If you didn't want to have the Project hardcoded, you may use a checkbox (or drop down list) in the request to have the Event Manager modify the request and turn it to a project specific request.

You might have a project specific request for a request such as "to do with reply", and possibly a separate request / project for "to do" type activities.

This should allow a resource to view in their workflow - requests for themselves and other resources (when they select another resource) that are not project specific.

Another possible solution would be to copy the EPTasks.asp page and with the SDK for Synergy create a copy without the ability to search by Resource. The SDK could do a Page redirect for your resources.

Also take a look at Functions 56, 82 or 132 to see if they can be used for security of functions.

Last, Can you change the the Level/Division in your requests (Corporate, Group, Division, Cost Center Group or Cost Center) to allow the viewing of only those Resouurces with the same Level/Division. I am not too sure if this would work.

Hopefully, this might spark some other ideas by others.
Dave Kloepfer
[url=http://www.synergyexpert.com:2v9xq3t1]Tips, Tools & Manuals[/url]
The administrator has disabled public write access.
Time to create page: 0.042 seconds
Powered by Kunena Forum  Protected by R Antispam