Re-submitting a Tactic after Edits

Short Description After editing an approved tactic — or one that was previously rejected — you can re-submit it for approval. This article walks through the flow.

What this article answers

When re-submission is required vs. automatic.
How to re-submit.
What approvers see after re-submission.

When re-submission happens

Re-submission applies in two scenarios:

The tactic was rejected. An approver declined; the tactic returned to Draft (or a Rejected state). You make the changes the approver asked for, then re-submit.
The tactic was approved, then edited. A workflow-triggering edit puts the tactic back into approval. You may need to explicitly re-submit, or the re-submission may happen automatically on save — depends on your workflow's configuration.

How to re-submit

From a Draft / Rejected state

Open the tactic.
Confirm all required (orange-asterisk) attributes are filled.
Click Submit for Approval (or Re-submit).
The tactic's status moves to Submitted / Pending Approval.
The Approval Tracker generates.
Approvers are notified.

[SCREENSHOT NEEDED — Tactic Inspection Window with Submit for Approval button]

From an Approved state after a workflow-triggering edit

Open the tactic.
Make the edit (cost change, Tactic Type change, workflow attribute change, etc.).
Save.
Depending on your instance:
- The tactic auto-re-enters approval. Approval Tracker regenerates. No further action needed.
- Or the tactic returns to a state requiring explicit re-submission. Click Re-submit.

Check your tactic's status after save — Submitted / Pending Approval indicates re-approval started; Approved means the edit didn't trigger re-approval.

What approvers see

After re-submission:

The tactic appears in approvers' My Approvals queues.
The Approval Tracker reflects the new cycle.
Approvers can compare current values against prior approved values via the audit log if they need context.

If re-submission doesn't take

If you click Submit / Re-submit and nothing seems to happen:

Required attributes might be missing. Look for unfilled orange-asterisk fields.
The Approval Workflow attribute references an inactive/deleted workflow. Hive9 will show the inactive-workflow error. See Error: "Selected Approval Workflow is either marked as inactive or deleted".
No eligible approvers exist on the team. Confirm at least one team member has Can Approve = Yes for the relevant team.

How re-submission affects history

Prior approval history is preserved in the tactic's audit log.
The live Approval Tracker resets to reflect the new cycle.
Approvers don't re-do their prior approvals automatically — each must act fresh on the re-submitted version.

Common questions

Can I edit a tactic that's already in approval without re-submission? Most edits are locked when a tactic is in approval. Cosmetic edits (description, internal notes) may be allowed depending on instance configuration. Cost, Tactic Type, and other workflow-driving attributes are typically locked.

Will my approval cycle restart from stage 1 or pick up where it left off? Re-submission typically restarts the workflow from stage 1, unless your instance has stage-preservation logic configured (rare).

What if the approver I need is on vacation? If the workflow uses Role-based or multi-approver stages, another eligible approver can act. If it's a single User approver who's unavailable, an admin may need to reassign or wait.

Will the Approval Tracker show prior approvals? The live Approval Tracker shows the current cycle. Audit logs preserve prior cycles. Some instances surface a "previous approvals" view; check your Inspection Window.