How You Bypass Approvals for Specific Development Goal Subprocesses

As administrators, you can enable selective bypassing of approvals for development goals in Transaction Console. You can do this without modifying either the existing autoapproval or manual approval rules of the development goals rule set.

Your organization may want some development goal transactions to be committed immediately, but may want other transactions to go through the approval flow. For example, your organization may want to allow employees to add a development goal that their manager shared without any approval, but may want managers to approve other transactions. You enable bypass approvals for the subprocesses that don't need manager's approval.

Development Goal Subprocesses for Bypass

When you expand the Approve Development Goal rule in the Approval Rules tab of Transaction Console, you can see these subprocesses that you can enable for bypassing approvals:

  • Add Shared Colleague Goal: Employee adds a goal that's shared by a colleague to their development plan.

  • Add Shared Manager Goal: Employee adds a goal that's shared by their manager with them to their development plan.

  • Goal Share Action: Employee shares their development goal.

  • Manage Private Goals: Employee does any action such as add, update, copy, delete, complete, or make inactive or active on their private development goal.

Note: You can also see the Remaining Goal Actions subprocess. This is for the goal actions other than that listed earlier. But You can't enable or disable Bypass Approvals for this subprocess. This only reflects the Bypass Approvals setting of the parent Approve Development Goal rule.

Configure Selective Bypass of Approvals for Development Goal Subprocesses

Here's how you can selectively bypass approvals for some development goal transactions:

  1. Go to Tools > Transaction Console.

  2. Click the Approval Rules tab.

  3. Search for and select the Approve Development Goal rule.

  4. Expand the Approve Development Goal rule.

  5. Enable Bypass Approvals for the subprocesses that you want to commit immediately.

Note: When you enable or disable Bypass Approvals for the parent Approve Development Goal rule, Bypass Approvals is automatically enabled or disabled for all the subprocesses.

After You Bypass Subprocesses

When you enable Bypass Approvals for any of the subprocesses, the corresponding development goal transaction is committed immediately. Users who did the subprocess action on their development goals won't see any approval messages nor receive notifications.

Development goal transactions that were in the draft state and pending approval state will continue through the approval flow and ignore the new partial bypass setting.