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,…
So, this is clearly an edge case, but it did have me pulling my hair out until I realized it was happening on the API end of things. For condition based PM generation (when the calibration gas gets low, replace the tank), I was adding assets that we're using the API to update a field value automatically from our Ignition…
Overview The customer wants the Purchase Order receiving workflow to be faster and provide clearer visibility into partially received quantities and associated Bills. Receiving a single item currently requires unnecessary manual selection work, while important receipt details are hidden behind additional navigation.…
Overview Enhance the Custom Dashboard task widget so users can clearly see and sort task and asset information separately, making it easier to review multiple tasks across multiple assets. Current Limitations • Task Name and Asset Name are not displayed separately, making sorting by asset difficult. • Asset ID is not…
Overview Enhance the Purchase Order (PO) widget on the Custom Dashboard so users can view more relevant PO details directly from the dashboard without needing to open each Purchase Order. Current Limitations • The PO widget currently provides limited information about each Purchase Order. • Important details such as who…
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:…
Overview Customers need activity logs to accurately distinguish between different task states and clearly identify when a task was created automatically by Limble rather than manually by a user. This is especially important for Min Qty tasks generated when inventory reaches the Part Qty Threshold. Current Limitations •…
Overview The customer needs a way to remove specific inventory quantities while preserving the correct historical cost layer. In this case, recently received parts were incorrect and discarded, but the associated Bill and PO were valid and needed to remain intact for accounting history. The current manual quantity…
Overview The customer wants Limble to protect manually entered pricing during the Purchase Order workflow. Currently, if a user enters a rate first and then selects or changes the vendor, Limble can automatically replace the manually entered rate with the part/vendor price. The customer expects either the manual rate to…
It looks like you're new here. Sign in or register to get started.
