Skip to main content
Cuts a stream of dated properties down to the periods the employee was actually employed. Salaries and similar values often have a start date and no end date in the source system, even after the employee has left. Left alone, the value stays in force forever. This node ends it on the employee’s last day and picks it up again on a rehire date. Example: a salary of 30 000 from 2025-01-01, for an employee employed 2025-01-01 to 2025-12-31 and rehired 2026-03-01, becomes 30 000 from 2025-01-01, nothing from 2026-01-01, and 30 000 again from 2026-03-01.

​
Inputs

  • Data / default in — the dated properties to limit.

​
Settings

  • Grace days — how many days past the last day of employment a value may stay in force. Leave at 0 to stop on the last day. Use it for pay that is settled after the employee has left.

​
Good to know

  • A value registered before the hire date is moved forward to the hire date, not dropped.
  • A value registered after the last day is dropped.
  • One-off payments are events rather than ongoing values, and a final settlement is usually dated after the last day. Do not run them through this node.
  • The employment periods are read from the employee, so the node is only available where the mapping sends data from Twine to the system.
  • Each independent id is limited on its own.

​
Ports