Judy Quist
My feedback
6 results found
-
240 votes
Hi all, we're working on analyzing the request for batch item description updates and would love your input to make sure our solution fits your needs.
I would like to propose the following:
The "Rebuild Physical item description" job currently allows auto-generating a description for a set of items (based on enum/chron data) - this option will be kept as is, but the job would allow selection to either auto-generate the description (existing) or enter a description value as free text (meaning all items in the set would get the same description). The free text option would also support updating the field with an empty value as exists in other jobs.
1. What are some examples of descriptions that would be relevant across an entire set of items?
2. As discussed in previous comments, changing the description of an item (manually or via job) causes the pending requests for that…
Judy Quist supported this idea ·
-
218 votes
Hello everyone,
I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed for handling complex normalization tasks. It offers the flexibility of a full programming language, enabling advanced data manipulation. This will complement our existing normalization rules based on DROOLS, maintaining all of its current capabilities.
Would the addition of this new type of normalization rule meet the requirements outlined in this idea?
Judy Quist supported this idea ·
-
5 votes
Judy Quist shared this idea ·
-
18 votes
Judy Quist supported this idea ·
-
135 votes
Judy Quist supported this idea ·
-
413 votes
Judy Quist supported this idea ·