Trying to find out if anyone has successfully set up and uses multiple requester id's linked/attached to one single log on for RSS.
We've got several users who order for different departments, etc, and they have multiple requester id's in RQ04. But, we want them to have one single log on ID when logging in to use Portal RSS. I know now they would need separate log on id's, one for each requester id.
This is in LSF 9.0 environment with 8.1 apps, on AIX.
My thought was it's possible to set up multiple RSS services, add a identity to each of those services, but then to create copies of the RSS bookmarks which each would point to one of the multiple requester id's.
Any ideas?thought?
TIA,
Roger
+1 for that idea!
Have not been able to successfully do it, multiple RSS links-each to a different requester identity has been unachievable as of yet for us. We seem to always get sidetracked on other issues whenever we get started good though...
Different Approval Trees. We currently are not using Process Flow for approvals so they have to have a different Requester ID for each Approval Tree that their departments tie to.
I know re-inventing the wheel it seems when there is a tool to achieve the same results...but that's where we are at.
We use a single RSS approval code for our requesters. The requesters need to submit a signed form from their budget authority for each cost center they wish to order from. We have some users with 7 or 8 different areas they can order for, although most only have 1 or 2.
Roger,
In the past I've developed a work around for this type of situation by presenting the user with a custom screen prior to launching RSS, allow them to provide whatever information is necessary to determine the appropriate approval path and then execute an AGS (Transaction) call to update the approval code on the requester record before they launch RSS. I never felt it was an "elegant" solution, but it works. It may also be possible to add a user exit to RQ10 that follows some business logic to essentially perform the same task, but I haven't actually done it that way.
thanks,
Jason Beard
617-548-5568
jabeard3@gmail.com
We limit one RQ04 record per requester, even if they request for multiple account units.. we use initials and "multi" in the requester id, we leave the account unit blank on the main rq04 screen, and list all the account units on the account unit screen. This works well for us.