Curious minds want to know: what are YOU asking Limble's MCP server? Drop your favorite AI prompt below 👇
Overview Customers want to view the total number of tasks closed within a selected time period and break that total down by the user who completed each task. This would allow dashboard widgets to show individual technician contributions instead of only grouping results by time intervals. Current Limitations • The “Number…
Overview Customers should be able to merge applicable work requests/work orders regardless of their current work classification, while preserving the complete work history from both records. A merge should consolidate duplicate or related work into a single record without causing previously entered operational data to be…
Hey all! Amanda here 👋 Although we're in the throes of writing content for our upcoming Maintenance Heroes Summit, we're planning the customer webinar calendar for the rest of the year, and when it comes to the topics? Well, we want to hear from you. Tell us what would actually help your team. A few prompts to get you…
Hi all! Our current process for identifying and adding new users is a little clunky because as Limble Admins, we don't know all the personnel at our facilities who need access and what their roles will be. We do not want to give the facilities access to add/remove users themselves, nor do we want to have to keep asking…
Overview Allow users to specify how an individual manual inventory adjustment should affect inventory costing without changing the organization's default FIFO/LIFO configuration. Current Limitations • FIFO/LIFO behavior is controlled by the broader inventory configuration. • A user cannot indicate that a particular manual…
Overview Users need to see the complete financial cost of a task directly from the task instead of building a dashboard or report to determine its total cost. Current Limitations • Task #12345 has Parts and Labor costs associated with it. • The Total report shows values such as Parts: $4,320.81, Labor: $1,236.33, and…
Description When Limble recalculates a Part Price based on a Bill/PO-related inventory transaction, the Part Log records the resulting price as though it were manually changed by the user. The log entry can also appear on a later date than the underlying Bill/receiving transaction that supplied the price, making the audit…
Overview Make the custom field type visible when editing an existing field and provide a supported way to change the field type where technically possible. Currently, users can select a type when creating a field, but that information is not clearly shown on the edit screen afterward. Current Limitations • When creating a…
Overview Dropdown custom fields should enforce unique option values by default. The purpose of using a selection field is to standardize data and prevent users from entering the same information in multiple different ways. Allowing duplicate options undermines that purpose and creates unnecessary inconsistency. Current…
It looks like you're new here. Sign in or register to get started.
