10

Update: I upgraded my Random Data Generator Appstore module, containing Herbert's request. new features: Generate random data for all entities and the associations between them. Randomize current data in entities (but leave associations intact). Exclude certain entities that you don't want to randomize (including associations to them). Use sensible default values or setup your own custom randomization setup where you can select what kind of random data to generate. Get a report of generated/randomized entities. View things that went wrong, for example because an entity could not be instantiated or a certain attribute yielded Data Validation errors. Log process on Randomizer debug lognode. Exclude entities inheriting from System.User by default. Option to fill String attributes with a fixed text. Do not write to attributes that actually belong to a System module entity (such as System.FileDocument.HasContents). Automatically shorten random String length so it fits in a certain attribute. Deals with various special cases such as circular references and self references. old features: Call various microflows to generate a random primitive value of a specific type. Pass any object to a Java action to get its attributes filled with random values, including selection of a random enum value. Examples using batching. my personal wish list: Be able to define a mapping on a domain model, so you can select how many associations to generate between 2 specific attributes. Be able to exclude certain attributes within an entity. Allocate a list of possible values for a certain attribute, instead of randomly generating them. Optionally also generate binary attributes and/or FileDocument files (consisting of random binary data) Old post below: Next week on Friday we at Mendix R&D will have another so-called Research Day where we can do whatever we like as long as it is somewhat related to Mendix. Now obviously there are many many features we can do some research on to see how feasible they are but for this day I will try to implement a 'most wanted' feature in a Java action. I'll let you, the Mendix partner or customer, decide what I'm going to do by ways of upvoting in this forum thread. To make this clear: This is about a Java action that anyone could create, not something I will change in the platform itself. About me: I work on the Mendix Business Server (also called runtime or runtime server) that loads your application model, executes it and serves requests from the Mendix client. Keep this in mind when picking something. Some constraints: 1) It must be a problem that is currently not (easily) solvable without using a Java action. 2) It must be a well-defined problem that's possible to implement in a day. You're welcome to submit ideas but I may reject them due to complexity. 3) It can't be a very specific integration for some external system, i.e. it must have some use to a wide audience. Smaller features are welcome too, I might be able to do a few. The end result will be a Java action and/or a set of java classes. If the feature is really useful we can always consider integrating it into the platform but this is not a given. So let's hear some ideas and/or do some upvoting! Disclaimer: I have no idea whether anything non-trivial will be defined well enough by ways of a forum reply, I may pick more understandable features above the highest-voted ones if I don't understand the latter well enough to consider implementing them in a day. I also reserve the right to NOT follow through in case I am required for something else during this day.

asked 2013-09-06

10 answers