Things are starting to look a little different around here. This month’s update took place during the evening of the 30th May. For a full list of changes in v2.59, please visit the Alloy Changelog.

New logo ⚡

Alloy has rocked the same logo since its inception in 2017. The big, bold letters represented our desire to make an impact and disrupt the marketplace with a similarly big and bold product, making it possible to manage all asset classes in one place for the first time.

Seven years later, Alloy is now one of multiple products offered by Causeway Technologies, the UK’s largest software solution provider for the construction and infrastructure industries.

Following the recent announcement of the new CausewayOne platform, our products are being rebranded with a new visual identity that’s modern and consistent. The new logo represents Causeway’s ongoing mission to digitise and connect each stage of the construction process, enabling data to flow freely between them.

We hope you like the new look!

Responsive Geometry Editor and pickers ↔️

We’ve been gradually improving Alloy’s usability on devices with smaller screens.

The Geometry Editor now renders properly at low screen widths, with the Draw tools appearing at the top to avoid collisions with other buttons. The GeoJson panel is no longer shown by default, but can still be enabled via the bottom-right menu if needed.

Similarly, the colour, icon and calendar pickers have also been adapted to work on smaller screens. In particular, the arrow buttons on the side of the calendar picker have moved to the top blue bar, enabling you to cycle through the months and years.

Renamed Parents section on Mobile 👪

When viewing an item’s details in Alloy Mobile, the “Originates From” section has been renamed to “Parents” to match how it appears in Alloy Web.

Access policy changes ✅

While we don’t often mention API-only features in release notes, we know some of you have started implementing access policies to govern user access on a per-item basis.

Therefore, we thought you might like to know about a couple of recent changes!

First, we’ve added three new expression types, providing more ways to define an access rule. To learn about how they work, check out HasAccess, User condition and Boolean condition in this Alloy Help article.

Secondly, access policies are now supplemental to permissions, rather than functioning on their own. If a user doesn’t have the Read permission enabled for the item’s design, an access policy will no longer have an effect.

Put simply, permissions let you grant access to all items of a particular design. Access policies let you refine that access by making it conditional, based on whether an item’s values fulfil the defined condition(s).