Current state: Live
Version release: Aluminium 13.00 (including from 12.07) – LIVE
Release to staging: 20/02/2025
Planned release to production: 06/03/2025
Actual release to production: 07/03/2025
Summary of functionality
Aluminium 13.00’s major function is the cancel leave request functionality, but there is other nice stuff in there you should be aware of. So, grab a cuppa and settle in…
Cancel leave requests workflow – (Core 13.0 and Mobile 3.6)
This duplicates existing workflow functionality to allow councils to set workflows where, when conditions are met and leave requests are cancelled, the request to cancel the leave request must also be approved.
If a leave request is cancelled and meets the conditions to trigger a cancel request workflow then the original request will remain until the request to cancel in approved (in which case the leave request will be cancelled) or declined (in which case the original leave request status will remain as it was before the cancellation).
The addition of this workflow also adds new notifications, allowing control of requests for cancellation, approval, and declining. Requests requiring leave cancellation approval will show on the My teams other requests page in a new tab.
[FEAT 12.12 ] New penalty conditions for blocks starting before or after a defined time
This allows you to create penalties that apply to all hours worked within a time block but only if the start time for the time block is within a set time range. When building penalty conditions, you can now use the conditions of start time after or start time before.
If you use ‘after’, then the penalty will be triggered for all hours within the block of time where the start time for the block is after the value added. If there is no start time before condition, then the condition will apply to any hours within a time block where the start time is between the start time and midnight
If you use ‘before’, then the penalty will be triggered for all hours within the block of time where the start time for the block is before the value added. If there is no start time after condition, then the condition will apply to any hours within a time block where the start time is between midnight and the start time.
All the little things*
*Well, not ‘all’, of course. I mean, that would take ages even though I am an amazing typist. I mean the little things that are in this release. Actually, not all of them are little, either.
Other things (formerly ‘all the little things’)
Workflow
[FIX] Fix issues with workflows that show incorrect data to users on app managers mode, as well as some pages on core. No one wants more information than they need, right? I mean, unless you are talking, well, anything on the internet. But to give you more time on the rest of the internets, we fixed an issue where some role managers were being told they had tasks even though they didn’t actually have them.
[FIX] Fix error on My teams timesheets listing for when viewing as role manager – Aha, kinda related to the above. Actually, it is totally related to the above and also totally fixed now.
[FIX] Fix permission error when skip submit removes the user from workflow – Gosh, this one was annoying. Imagine being told you could skip submit on one of your team’s timesheet because they forgot to do it, except once you did this, you were no longer able to approve the actual timesheet. Well, you can keep on imagining this one because it is, once again, not real. We fixed it.
Timesheets
[FIX 12.15 ] Fix issue with allowances getting removed when the same allowance type is used twice in the same timecard. Sometimes, you need more than one of the same allowance on the same day. We won’t judge; we will just allow you to do it. Unless the settings say you can’t, in which case you… can’t. But at least it will be an on purpose ‘can’t’ not a bug ‘can’t’.
[FIX 12.15] Fix issues on ad hoc allowance calculations when copying from the previous day, which also stuffed the totals in payment view – If you copied records of work from one day to another day, then well, maybe the allowance might magically also be copied from the last time you had an allowance. It was not technically in the spirit of ‘copy from previous day’, so we fixed it, so now it works ‘in spirit’ but also just actually works.
[CHORE] Change message on issues modal when timesheet cannot be approved by workflow reasons but it has no stopper issues – This now just invites the manager to review the timesheet rather than suggests that an issue exists when one does not.
FIX] Fix issue with role managers opening timesheets and schedule values were doubled – This was a rare one, except for the couple of users it impacted for whom it was not rare but instead super annoying. Especially because when you told someone what was happening, they couldn’t actually see what you were talking about. Kinda like the whole dark magic thing leaking into the human world in Harry Potter (TM). But rest assured, ya bunch of muggles, we fixed it.
Leave
[FIX] Fix end time calculation error when applying for full-day leave on flexible shifts – Argh, the end time for full-day leave on flexible shifts if you had no expected hours was defaulting to midnight. That is annoying, right? So now it actually does what it should do. Which is more than I can say for my kids, who should go to bed at 8 pm but never do.
Integrations and reports
[CHORE] Make changes to exclusion of work orders on integration to allow range of codes
[CHORE 12.8] – Plant import file changes – Amend import file and process to allow for plant to be imported with ext ref ID and cost prefix/suffix because sometimes Meg tells me we need the plant ID and the ext ref ID.
[FEAT 12.7] – Create new report for batch upload for Plant on Synergy format – Allows the uploading of plant costing to Synergy as a batch file, which is 100% better than manually typing that in.
[FEAT 12.9] Create new report for Authority batch file including columns for plant data. This allows manual upload of full payrun data plus plant without API timeout limits on the number of timesheet rows. Pretty cool.
[FEAT 12.11] Create new integration rule for Authority payroll integration to allow applying splits to leave hours based on user – as Good Will Hunting would say where user equals ‘a’ and their leave request is ‘b’ then the leave hours can apply to ‘c’ and ‘d’ and even ‘e’. Okay, look, between us, I can’t even remember if I did university-entrance math, let alone the actual math itself. P.S. He probably wouldn’t actually say that.
[FIX] Fix sync issue with committed balances calculations in the end of payrun – For some Authority ERP customers, due to performance issues with the API services, the syncing of leave balances should time out before completing the process, which could cause issues with the balances. Now we have kinda built some processes to track if this happens and fix it.
API services
[FEAT] #API Update API services to reflect changes made on leave cancellation workflow
[FEAT] #API Create API service to list leave cancellation requests
[FEAT] #API Create new API service to get dashboard widgets info
