Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Description of Issue

Setup for BGA or BGT workflow

What workflow will be triggered when an amendment is released

Context
  • Budget Transfers and Amendments
  • Budget Workflow
  • BGA
  • BGT
Cause

Budget workflow is determined by a user's Budget Amendment Transfer data access.

Resolution

If both BGT and BGA rules exist:

  1. Amendment Type 1 or 4 is used
    1. If user's Budget Amendment Transfer data access is set to FULL, then BGT rule is triggered 
    2. If user's Budget Amendment Transfer data access is set to NONE, then BGA rule is triggered
    3. If user's Budget Amendment Transfer data access is set to LIMITED, then BGA rule is triggered
  2. Amendment Type 2, 3, 5, or 6
    1. BGA rules will always be triggered

If no BGT rules exist, only BGA rules:

  1. Amendment Type 1 or 4 is used
    1. If user's Budget Amendment Transfer data access is set to FULL, workflow is bypassed (auto-approved) 
    2. If user's Budget Amendment Transfer data access is set to NONE, then BGA rule is triggered
    3. If user's Budget Amendment Transfer data access is set to LIMITED, workflow is bypassed (Auto-approved)
  2. Amendment Type 2, 3, 5, or 6
    1. BGA rules will always be triggered

If no BGA rules exist, only BGT rules:

  1. Amendment Type 1 or 4 is used
    1. If user's Budget Amendment Transfer data access is set to FULL, then BGT rule is triggered 
    2. If user's Budget Amendment Transfer data access is set to NONE, workflow is bypassed (Auto-approved)
  2. Amendment Type 2, 3, 5, or 6
    1. Workflow is bypassed (Auto-approved)
Additional Information

General Ledger data access for the selected program, Budget Amendment Entry (bgamdent), will determine what accounts the user can see/enter on an amendment/transfer





  • No labels