Workflow Migration — Procurement Hardware
/plan-workflow-to-flow-migration
for legacy wf
@Procurement Process Flow - Hardware
Response to:
/plan-workflow-to-flow-migration · @Procurement Process Flow - Hardware
Analyzing Procurement Hardware workflow & designing Flow Designer migration…
0s
Viewed 49 Records
Viewed 3 Tables
Searched 24 Sources
Ran 4 Scripts
Legacy OOB workflow created 2012 on
sc_req_item
.
Never executed
on this instance — zero execution history.
10 activities, 1 conditional branch, 0 scripts/integrations. Fully declarative.
All activities map cleanly to OOB Flow Designer actions.
Migration Assessment
Procurement Process Flow - Hardware
· low-complexity, OOB-flagged for deprecation
Complexity
Low
OOB coverage
100%
Custom actions
0
Human est.
4–6
hrs
1
Drop the redundant
Is Procurement turned on
branch — property always enabled on this instance.
2
Collapse two sequential
Wait for Condition
activities into one compound condition.
3
Add top-level
Try/Catch
error handler — legacy workflow has none.
Agree — drop the procurement-toggle branch & collapse the waits. Build it.
Building flow in Flow Designer — 16 steps incl. Try/Catch…
0s
Modified Files
Saved 43 Records
Browsed Flow Designer UI
Trigger +
Ask For Approval
+ If/Else routing built
4×
Create Catalog Task
with RITM stage updates between each
Rejected-path + top-level
Error Handler
attached
Flow
published
& active — verified in Flow Designer UI
Flow Built & Published
Active / Published
Scope:
Global
· 16 steps · Trigger:
sc_req_item
▶
Trigger
01
Ask Approval
02
If: Approved
03
Stage: Fulfill
04
Task: Source
05
Stage: Await
06
Task: Receive
07
Stage: Config
08
Task: Configure
09
Stage: Deliver
10
Task: Deliver
11
Stage: Complete
12
End ✓
13
Else: Reject
14
Stage: Cancel
15
End ✗
⚠
Try/Catch
Ask Echelon to migrate, refactor, or test a workflow…
Replay