Read time: 10 minutes
As promised, today we’re sharing a step-by-step guide on how to successfully upgrade your process owners from employees to Integration System Users (ISUs).
A couple of weeks ago in part 1 of this three-part newsletter, we covered why employees shouldn’t own your scheduled processes. If you missed it, I highly recommend you check it out below before diving into today’s newsletter (which is part 2 out of 3)👇
Fair warning… this guide is jam-packed with information. Some might call it… dense 😅 (it took us 16+ hours and a few shots of espresso to write this one).
This guide is sooo stuffed with information, that we decided to split it into 2 newsletters for digestibility. Here’s what to expect…
— How to Turnover-Proof Your Scheduled Processes —
Part 2 (today):
Step 1: Assess Your Processes
Step 2: Understanding ISUs and ISSGs
Step 3: Create Your Upgrade Plan
Step 4: Create Your ISUs
Step 5: Create Your ISSGs
Step 6: Transfer Ownership of Your Processes
Step 7: Test, Test, TEST!
Step 8: Deploy Your Upgrades to Production
✅ Why you need to turnover-proof your processes
With that, grab your caffeinated beverage of choice, and let’s dive in! 🌊
Step 1: Assess Your Processes
In your Production tenant, run the WD-delivered Scheduled Future Processes report. Check the “Owned by User” column to glance at which of your processes are owned by employees rather than ISUs.
This is where we go deeper.
Free builds awareness. Premium fills all the gaps.
Unlock the restAnd much more:
- Configuration Deep Dives 🤿
- Release Ratings & Reviews ⭐
- Access to the full Archive 🔐
- A say in what gets built 🗳️
