Day 2 - Editing and Understanding the Process Map

The goal is to learn how to interpret, refine, and enhance your recorded processes using the Automize Web Portal.

1. Overview

After recording a process with the Automize Bot, all captured activities appear on the Web Portal as a visual process map. This map represents the structure and logic of your automation from start to finish.

You'll use the editor to:

• Review and rename activities.

• Adjust logic and timing.

• Add new activities or decisions.

• Optimise how the bot understands and executes your process.

2. The Process Map Interface

Layout

• The map flows top-down, from the start node to the end node.

• Each activity (or node) represents one recorded step.

• Connectors define the relationship and order of execution.

Interface Elements

Useful Canvas Shortcuts

• Double-click an activity → Duplicate it
  Quickly creates a copy of the selected activity, including its settings.

• Drag a connector endpoint → Change target activity
  Re-route process flow without deleting and recreating connectors.

• Hold SHIFT + Click multiple activities → Multi-select
  You can then drag all selected activities together to reorganise your layout.

• Click empty canvas area → Deselect all
  Clears all selected activities and resets your focus on the map.

• Creating new connectors when one already exists:
  • If the source activity is a Loop → the new connector becomes a False (Amber) path.
  • For all other activities → the new connector becomes an Exception (Red) path.

Tip: Use multi-select + drag to create tidy, readable layouts quickly.

3. Reviewing and Editing Activities

Renaming Steps

Click on an activity's edit icon name and give it a clear, descriptive label, e.g.:

• Write Calculator

• Press Enter

• Click Equals

• Close Calculator

Consistent naming helps identify errors faster and improves collaboration.

Reordering and Adjusting Flow

• Drag and drop activities to rearrange sequence.

• Adjust connectors by dragging endpoints to new targets.

Best Practice: Always maintain logical top-down flow and avoid unnecessary crossing connectors.

Editing Activity Properties

Each activity exposes editable settings when clicking on the ✏️ icon:

{{popups:rpas/edit:action=click}}

• Action type: click, type, open app, etc.

• Target selector: defines what UI element to interact with.

• Conditional output: define alternate paths on success / failure.

Adding New Activities

You can manually insert new actions that weren't recorded.

{{popups:rpas/add:action=browser-click}}

To add a new activity:

1. Right-click on the canvas or use the toolbar.

2. Select Add Activity → choose the desired action type.

3. Configure its properties and connectors.

4. Introducing Logic and Connectors

Logic allows processes to adapt based on conditions.Connectors control how and when Automize moves from one activity to another.

Connector Types

To change connector type:

1. Click on a connection line to edit it.

2. On the popup, choose the desired type.

Adding a Decision Node

{{popups:decisions/add}}

1. Click on the top-right button's drop-down → + Activity → Select Decision.

2. Enter a condition (e.g., {Result} > 100).

3. Link the True connector to one branch and False to another.

Example:If {Amount} > 1000 → Send approval email.Else → Skip approval.

5. Hands-On Exercises

Exercise 1 - Rename and Tidy

Open your Calculator process from Day 1 and:

1. Rename all activities clearly.

2. Add a description explaining the purpose of the process.

3. Add a note in the process by clicking on the top-right Button's drop-down list → + Note.

Exercise 2 - Add a Decision

Insert a Decision after your "Enter Value" step:

• Condition: if the sum is greater than 500, show a message box that says "High Value!".

• Otherwise, end normally.

Challenge - Two-Path Calculator

Create a process with two possible branches:

• Branch A: Performs addition and displays result.

• Branch B: Performs subtraction if a variable {Mode} = "Sub".

Hint: Add a Decision activity early in the process to test the variable.

6. Best Practices for Editing Processes

1. Keep Process Maps Simple

Avoid overly large, complex flows in one process. Split long automations into smaller sub-processes for reuse and clarity.

2. Use Consistent Naming

Use Title Case (e.g. Write Calculator In Search), PascalCase (e.g. WriteCalculatorInSearch) or underscores (e.g., Write_Calculator_In_Search). This helps other developers understand your process quickly.

3. Document Intent

Add descriptions on why a step exists (or notes that are visually visible on a process map) - not just what it does. Future you (or another developer) will thank you.

4. Validate as You Edit

After each major change, play back or debug the process. Quick testing prevents multiple issues from stacking up.

5. Optimise Timing

Replace long fixed delays with smarter "Wait For" conditions. This reduces runtime and increases reliability.

6. Version Control

If you adjust a working process, save a new version under a different environment (e.g., move from DEV → TEST). Never overwrite production versions directly.

7. Align With Industry Standards

These editing practices are used across all major RPA frameworks:

• Error-safe design: Always include exception branches.

• Readable flow: Layout and naming should tell the process story visually.

• Reusable logic: Build reusable decision or loop patterns.

• Performance checks: Review runtime duration and optimise loops or conditions.

End of Day 2 Summary

By completing Day 2, you should now be able to:

✅ Navigate and understand the Automize process map interface
✅ Edit, rename, and re-order activities
✅ Add decisions and connectors to control logic
✅ Apply best practices for clear, efficient, and maintainable automations

Next Step - Day 3

Learn how to work with variables, loops, and data handling - including Automize's built-in Excel-style formula engine for dynamic data manipulation.
Next