ucdavis / ucdavis/Purchasing

Auto Approvals for Other Requesters

Open
#327 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feedback
Dominant language
C#
Stars
7
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Reviewing how auto approvals work...

http://computing.caes.ucdavis.edu/faq/prepurchasing/how-do-auto-approvals-work

It took some effort to figure out how to get type 2 working (i.e., auto approval that an approver set up).

Here's my recipe:

  1. Within the "Workgroup Accounts" screen I set myself as an approver on a designated account. Of course I added myself to the "Approvers" group within the workgroup prior to this.

  2. Within my "Auto Approvals" screen, I set an auto approval for the designated account, which I set myself as the approver for above.

Now, when a requester other than myself creates an order request specifying the designated account (where I want the "Select an Account" option used instead of the "Approver & Account Manager" option within the "Order Details" of a reqest), my profile automatically approves it.

+> What I'm curious about: why does the auto approval not work for other requesters if I specify myself as the "Target User" on the "Auto Approval" edit screen instead of specifying an "Account"? (FYI: If I set both I get "An error has occurred" screen after I click the "Save" button.)

Originally I was thinking that I would set an auto approval for a "target user" once, and then I could set that target user as an approver on one or more accounts. When the workgroup accounts change, the user's auto approval rules wouldn't need to change.

As it appears to me, I need to add the designated user as an approver on each account, and that user needs to have an auto approval rule for… more

Bradford LutenBradford Luten on March 7, 2014 5:56 PM (0 comments) Public permalink


Votes: 2
Author: jsylvest
Voters: jsylvest,ajnichol

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or code entry points are named. Start by tracing the Auto Approvals and Workgroup Accounts flows described in the issue, reproduce the target-user behavior for another requester, and clarify whether the intended result is support for target-user rules or an error-message fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
authorization, backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.