In this module, you've learned how to define your scope within our platform. This article will help you understand the meaning and importance of each part. Remember this rule:
“If it's not clearly listed in your scope, it won't appear in your target system.”
What Are “Scenarios”?
Scenarios help you break down your scope into clear and manageable subjects. Instead of immediately jumping into the details (fields), you first identify broader categories like:
- Personal (basic employee details like name, date of birth)
- Address (location details of employees)
- Contract (employment details, like start date, length of employment)
- Team (organizational details, such as department or team assignment)
- etc.
Breaking your scope into scenarios first makes the process simpler and prevents you from feeling overwhelmed by detailed information too soon.
Predefined Scenarios (Optional)
We offer predefined scenarios within the platform to help you save time. These are common categories that appear in most HR-payroll integrations. You can select and use these directly, speeding up your work. You don't have to use these predefined scenarios—you can always create your own.
Defining “Fields”: Source and Target
After setting scenarios, the next step is defining the detailed fields. A field is simply a specific piece of data that moves from one system (source) to the other (target).
- Source Fields: These are the names of the data fields in your current HR system (source system).
- Target Fields: These are the names of the corresponding data fields in your payroll or receiving system (target system).
For example, your HR system might have fields called “First Name” and “Last Name,” while your payroll system might simply have “Full Name.”
Logic (Transformations and Conditions)
Logic explains any special instructions or transformations needed between source and target fields. Common examples:
- Concatenation (combining fields): “First Name” + “Last Name” → “Full Name”
- Formatting rules: Country code must be “ISO 2 format” (like “NL” instead of “Netherlands”)
Providing clear logic ensures the data transforms correctly from source to target, avoiding mistakes or confusion later.
Leaving Fields Empty or Missing Fields
Sometimes your target system expects fields that don't exist in your source system. In this case, clearly indicate that this field must remain empty. You can use the comments section to clearly communicate this to the developer. Clear instructions help your developer build exactly the right interface.
Using the Comments Section Effectively
In the comments section, you can add critical clarifications or special conditions. Examples include:
- “Each employee may exist only once in the target system.”
- “Do not create duplicates if an employee number already exists.”
Clear comments prevent confusion, save development time, and ensure your interface behaves exactly as intended.
Summary of Your Scope
Once your scenarios and fields are defined, you'll see a clear summary. This summary gives you a full overview of what data will be sent, helping you easily review and confirm everything at a glance.
Why Does Defining Your Scope Clearly Matter?
Clearly defining your scope ensures:
- Correct and complete data transfer between systems.
- Fewer mistakes, less troubleshooting, and smoother payroll processes.
- Greater efficiency and accuracy in HR and payroll administration.
You've now learned the meaning of each part involved in clearly defining your scope. Remember, clear communication in your scope is the key to successful data integration. Let's continue to the next step!
Learning Objectives
After completing this module, you will clearly understand:
- What scenarios are and how they help structure your scope.
- Why clearly defining scenarios first, and fields second, makes your process easier.
- The role and meaning of source fields, target fields, and logic.
- How to clearly communicate your needs through comments.