Projects and work slips live in abas, the team's time tracking lives in awork. Before, that meant maintaining everything twice and transferring times from awork to abas by hand. Today an invisible interface does the job — fully automated, twice a day, with no user interface of its own.
Around 30 employees work with it without ever seeing the interface.
When a project is created in abas, it automatically shows up as an awork project on the next run — including the project tags from abas. The associated work slips become task lists beneath it. Nobody creates anything twice anymore.
The team records its times in awork as usual. The interface posts them to abas automatically — via REST to an abas infosystem, exactly where work slips and post-calculation need them. Almost 30,000 time entries have been posted this way so far, without anyone having to retype a single one.
The interface deliberately has no user interface for the employees: the systems people like simply remain their systems. In the background, every run logs how many projects were created and how many times were posted — a small monitoring dashboard shows the state at a glance.
No magic — just craftsmanship.
Cloud APIs change, and not every documentation keeps its promises. Every assumption about both sides — awork and abas alike — is verified against the real system before it's cast into code.
Projects, work slips, infosystems: the times land via REST exactly where abas expects them — no detours and no changes to your master data.
Faulty individual entries are skipped and logged — the rest is posted as usual. No run aborts, no time is lost, and the log shows what needs clarifying.
awork is just one example. The same craftsmanship connects abas ERP with the cloud tool your team really works in — anywhere there's an API.
On the left, the team tracks time in awork — in the background, the interface keeps watch.
This is how the team tracks time in awork: type an entry, pick a duration, save — that is all. A few hours later, the interface posts exactly these entries to abas automatically. (Product view: awork)
The weekly view in awork: everyone sees their entries in the calendar. The projects and task lists behind them come from abas automatically. (Product view: awork)
The only visible part of the interface: the monitoring. Every run with its timestamp, time entry count and newly created projects — and ideally it simply says: no errors found.
If your team works in a cloud tool and abas never hears about it: tell us about it. An invisible interface is often closer than you think.
Get in touch