Welcome, Guest
Username: Password: Remember me

TOPIC: Workflow Creator / Realizer (Not the Same)

Workflow Creator / Realizer (Not the Same) #1108

  • Dkloepfer
  • Dkloepfer's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 92
  • Thank you received: 2
  • Karma: 0
One of our customers has asked us to help them create a new request for their staff to use. This request will be created by anyone in the organization, but they do not want the "Creator" to be the same person as the "Realizer"

We can't use Groups, because the same person would have to be in all of the groups. Without using Event Manager, are there are other ways we could handle this 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.

Workflow Creator / Realizer (Not the Same) #1110

Lots of ways - put an item on the request, you could even hide that field, and have the realizer be the manager of that item. Easy enough. Default the item field to that particular item.
How about that?
Ann
Ann Roos Hayner
Omaha NE
The administrator has disabled public write access.

Workflow Creator / Realizer (Not the Same) #1129

  • mmccarty
  • mmccarty's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 17
  • Karma: 0
If you add Resource to the workflow fields, and specify which resource, you can direct the Realize stage to be completed by that Resource. The request is submitted by anyone, but goes to the named resource.

Or, you can create a workflow role for that task and assign the Realize stage to the role. That's actually better because as people come and go the role doesn't change - just those assigned to it. We start our workflow roles with WF- (e.g. WF-Programs, WF-UPS Clerk) and our document roles with DM- (e.g., DM-Credit Application, DM-Corporate Policies).
The administrator has disabled public write access.

Workflow Creator / Realizer (Not the Same) #1311

  • ultrav375
  • ultrav375's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 35
  • Thank you received: 1
  • Karma: 0
We use roles in most of our workflows - we usually include one person who is to do that step the majority of the time and one backup. This has turned out to be the best for us. I usually name the role "realizer of the return authorization request" so it is obvious what it is for.

Celeste
The administrator has disabled public write access.

Workflow Creator / Realizer (Not the Same) #1568

  • SLeete
  • SLeete's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 54
  • Karma: 0
Several years ago, I wrote Document: 14.622.846 - Routing a Request Based on a Workflow Condition. This may also be of help to you. It can be viewed through our customer or partner portal.
Scott Leete
Presales, Principal


Exact Software North America LLC

T +1 407 602 6088
F +1 866 544 5456
scott.leete@exact.com
http://www.exact.com
The administrator has disabled public write access.

Workflow Creator / Realizer (Not the Same) #1581

  • be05x5
  • be05x5's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 123
  • Thank you received: 2
  • Karma: 0
I guess you could send the workflow to anyone (or a temp user) and set Assume to "Everyone". This would allow anyone to find this workflow and grab it.
The administrator has disabled public write access.
Time to create page: 0.049 seconds
Powered by Kunena Forum  Protected by R Antispam