Overview The current PM structure requires users to create separate PMs for each asset. While assigning one PM to multiple assets exists as a workaround, it introduces new issues—specifically identical naming and bulk generation. The goal is to make multi-asset PM assignment a fully supported workflow by improving naming…
Overview Rearranging widgets on Limble dashboards is unnecessarily difficult, regardless of whether the widgets are large or small. Moving widgets around the dashboard should be simple and intuitive. Currently, repositioning widgets can require excessive dragging, scrolling, and trial and error to achieve the desired…
Overview When a Work Request is converted into a task in the new Limble mobile app, the original problem description should appear directly in the Details tab, without requiring technicians to navigate to Instructions. Current Limitations The Description section displays a generic message identifying who submitted the Work…
Overview The customer requests that Limble automatically account for outstanding quantities on open Purchase Orders (POs) when generating new POs through the stock parts reorder process. Currently, parts already ordered but not yet received are added to new POs without adjusting for pending quantities, resulting in…
Hey Limble Community, Your friends on the Customer Success team are looking forward to this week’s Office Hours, and we'd love for you to join us! Think of this as an open forum to connect, share, and learn more about making Limble work best for you. In every session, you'll have the opportunity to: Ask Anything Limble:…
I’m preparing for the AWS Certified Solutions Architect Professional (SAP-C02) exam and find it challenging to choose the best architecture when a scenario includes several requirements. Different AWS services may solve the same problem, but factors such as availability, cost, operational effort, and disaster recovery…
Every maintenance team is sitting on an untapped asset: completion notes. Every closed work order has a tech's honest account of what actually failed. "Bearing seized, no grease." "Belt frayed, misalignment again." Thousands of them. And you can do almost nothing with them, because failure causes live in the comments and…
We have seen a recurring issue where a Team is created after assigning multiple users to a work order. We have not been able to intentionally reproduce it, and it appears to happen randomly. We have seen it roughly 5–6 times this year. The main issue is that our widgets are filtered to specific users or Teams we created,…
It looks like you're new here. Sign in or register to get started.