Welcome, Guest
Username: Password: Remember me

TOPIC: Hiding project members.

Hiding project members. #1283

  • bingo57
  • bingo57's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 9
  • Karma: 0
I have a request that has a project which has 160 members that are allowed to assume and process it. Is there any way to hide the members in the process box of the request so it dosn't run off the screen?
The administrator has disabled public write access.

Hiding project members. #1284

  • Dkloepfer
  • Dkloepfer's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 92
  • Thank you received: 2
  • Karma: 0
One of our customers had this same problem - too many resources could possibly assume a request. We investigated, but found that we not able to change the listing shown in the request.

Dave Kloepfer
Dave Kloepfer
http://www.synergyexpert.com
dkloepfer@synergyexpert.com
[url=http://www.synergyexpert.com:2v9xq3t1]Tips, Tools & Manuals[/url]
The administrator has disabled public write access.

Hiding project members. #1286

  • bingo57
  • bingo57's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 9
  • Karma: 0
Is there another way to let everyone assume and process the request without doing it this way? The only reason that I used a project is to allow everyone access to it.
The administrator has disabled public write access.

Hiding project members. #1288

  • Dkloepfer
  • Dkloepfer's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 92
  • Thank you received: 2
  • Karma: 0
There is an additional field within the Request Definition that allows "Everyone" to act as a Resource to "Realize" a request. In the top of the Request - instead of each resource being labeled and in your case - showing 160 names - it simply states "Everyone"

I have never seen any documentation on the use of this specific field (value) in the Synergy documentation, but found it while creating some requests.

Depending upon your request and steps, it might not work - but I believe it is worth a review.

This request does not show up as a workflow item, and the use of a custom asp search page for these type of Requests and showing all "Approved" requests of this type for your staff would be recommended. This could be linked to a custom Start Page for all Resources to look over or as a Favorites link or as a button on a common ASP Page for any staff to click.

We can do a gotomeeting.com if you wish to see it in action. Send me a message if you wish further assistance.

Dave Kloepfer
dkloepfer@synergyexpert.com
Dave Kloepfer
http://www.synergyexpert.com
dkloepfer@synergyexpert.com
[url=http://www.synergyexpert.com:2v9xq3t1]Tips, Tools & Manuals[/url]
The administrator has disabled public write access.

Hiding project members. #1291

  • bingo57
  • bingo57's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 9
  • Karma: 0
Yea the "everyone" field is only availible to assume and or assign in the process step, not just process. I have set that to everyone and they can assume it but can't edit the field the end time field in a multi-line request. I may take you up on the goto meeting. I want to try one other thing first.

Thanks for you help,
Jim
The administrator has disabled public write access.

Hiding project members. #1294

  • bingo57
  • bingo57's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 9
  • Karma: 0
I also tried using roles but it also shows all users in the role and won't let the user edit the end date/time field when used in a multi-row form request. I could live with the showing of all the users if I have to but why won't the request allow the resourse that assumes it edit the date/time field when form view is slelected? It's available untill you click form.
The administrator has disabled public write access.

Hiding project members. #1295

  • Dkloepfer
  • Dkloepfer's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 92
  • Thank you received: 2
  • Karma: 0
Without seeing the request, could you use a Free Date field instead of the End Date field, if that is the limitation with the multiple request type. Would that help and if necessary have the EEM change the field in the requests to the proper value in the End Date value?

Dave Kloepfer
dkloepfer@synergyexpert.com
Dave Kloepfer
http://www.synergyexpert.com
dkloepfer@synergyexpert.com
[url=http://www.synergyexpert.com:2v9xq3t1]Tips, Tools & Manuals[/url]
The administrator has disabled public write access.

Hiding project members. #1300

  • bingo57
  • bingo57's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 9
  • Karma: 0
I need the end time. I didn't know it mattered about free date fields and whom and how they process. I'll give you the short version of the request. This is used in a jail to enter daily logs. One of the logs is called inmate temp. out of the cell block.
The request has a creator which is set to current, a start/date and time, reason free text with several drop down picks and multiple account fields for "INMATES". Officer A that works midnight shift picks 6 inmates to leave the cell block for kitchen duty before his shift is over. Officer B Comes in on dayshift and sees the workflow request in appoved and pending status. The inmates come back in the cell block and he opens the request and assumes it and the end time field is there and editable untill he hits the form view because they all came back at the same time and he doesn't want to open each record individully and process each. If officer A stays on duty and opens the pending requests of course he doesn't have to assume it so he can use form view enter one return time and process all six at one time with the same reture time.
The administrator has disabled public write access.
Time to create page: 0.063 seconds
Powered by Kunena Forum  Protected by R Antispam