Overview
The Edit Current Journey and New Journey bulk update options allow users to apply changes across multiple contracts simultaneously — but they serve different purposes.
- Edit Current Journey updates the existing active Journey
- New Journey creates a new Journey record for each selected contract
Understanding when to use each option is critical to ensure data consistency, traceability, and correct payroll behavior.
💡 Choosing the wrong option may lead to loss of historical accuracy or incorrect contract evolution.
Key Difference
| Feature | Edit Current Journey | New Journey |
|---|---|---|
| Data Handling | Updates existing Journey | Creates a new Journey |
| History | No new history created | Full history preserved |
| Use Case | Corrections / minor updates | Structural or contractual changes |
| Traceability | Limited | Full |
| Risk Level | Higher (overwrites data) | Safer (adds new record) |
Edit Current Journey
Purpose
Used to modify the current active Journey across multiple contracts.
Typical scenarios:
- Correcting incorrect data
- Updating classification fields (Area, Function, Category)
- Aligning organizational attributes
- Applying non-structural adjustments
💡 This option does not create a new record — it directly updates existing data.
Process Overview
Follows the same structure as other bulk updates:
-
Filters – Select contracts

-
Journey Details – Define fields to update

-
Review – Validate before applying

Important Behavior
- Only selected fields are updated
- Fields not modified appear as N/A in the review
- N/A means no change, not data removal
⚠️ Changes overwrite current data and do not create history.
New Journey
Purpose
Used to create a new Journey entry for each selected contract.
Typical scenarios:
- Role or function changes
- Department transfers
- Contract evolution (promotion, reassignment)
- Any change requiring historical tracking
💡 This option preserves the previous Journey and ensures full traceability.
Process Overview
Similar structure, but with a key difference:
-
Filters – Select contracts
-
Journey Details – Define the new Journey values
-
Review – Validate new records before creation
Key Behavior
- A new Journey is created per contract
- Previous Journey remains unchanged
- Timeline and history are preserved
When to Use Each Option
Use Edit Current Journey when:
- You are correcting or refining existing data
- No historical tracking is required
- The change is minor and non-structural
Use New Journey when:
- The change represents a new contractual phase
- Historical tracking is required
- The update impacts role, structure, or employment conditions
Risks and Considerations
Edit Current Journey
⚠️ Risk of:
- Overwriting important data
- Losing historical accuracy
- Impacting payroll if used incorrectly
New Journey
✔ Safer approach because:
- Preserves history
- Ensures auditability
- Supports contract evolution tracking
Best Practices
✔ Default to New Journey when in doubt
✔ Use Edit Current Journey only for controlled corrections
✔ Always validate changes in the Review step
✔ Apply updates in smaller groups when possible
✔ Align with HR/Finance before large-scale updates
Summary
Both options enable efficient bulk updates, but they serve distinct purposes:
- Edit Current Journey → best for quick corrections
- New Journey → best for tracked, structural changes
💡 Choosing the correct approach ensures data integrity, compliance, and reliable reporting across the system.
Help Center