Is there an easy solution to this problem that is (at least somewhat) scaleable to a high number of agents and plottable elements? When the model runs the user is supposed to be able to press the button which adds "flow" to "plot". In agent a theres the flow "flow", in agent b a plot "plot" and a button "button" (Or any other Controls element if it's more useful in this case). I could make an event for every single element of my model each, but i hoped there was a way to more directly translate user-input into a useable path of the element.Īs an example: I have two agents, a and b. The problem however is that I have to predefine the element I want to plot in my user-triggered event. I've found some success in triggering a cyclic event with a radio button, then the event updates a helper variable in my analysis-agent with a predefined element from another agent and plots the variable. The idea is to have multiple radio buttons or combo boxes which allow the user to select any element of any agent and automatically create a plot of the element. I want to let the user add a time plot for any flow/stock/variable during the simulation run. This type of data variable is always an object whose schema matches the data resource schema.I've got a model with multiple agents, each with a couple of flows and stocks, and an analysis-agent. They are most often used in forms whose purpose is to create a new record, by binding the input fields to the data variable. The difference between the new and single data record types is simply that new data record type data variables do not contain any logic to fetch data from the data resource, they simply initialize as empty. a movie you haven't yet added to your database. This type of data variable defines an empty object, e.g. This type of data variable is always an object whose schema matches the data resource schema. For Client-side storage, and for most APIs, this happens by the ID property. Since we always want to fetch some specific record from the data resource, the data resource must define a property or properties to uniquely identify the record we're interested in. For example, a single specific movie from a Movies resource. This type of data variable gives you access to a single data record fetched from the data resource. This type of data variable is always an array of objects whose schema matches the data resource schema. In contrast, REST API direct integrations can define any number of properties, depending on the source API. get all movies whose title matches "Lord of the rings", sorted by release date, limited to 5 movies. For example, a On-device storage resource has the Filters, Sorting criteria and Limit properties. These are configurable when using the data variable. Typically, the data resource defines some properties that allow you to affect what records are returned from the backend. For example, all movies from a Movies resource. This type of data variable gives you access to multiple records fetched from the data resource. There are three types of data variables, chosen when you add one to a page. Their schema is always the same as their data resource's schema. They are added to a page via the variable editor, and contain default logic to populate themselves with data from the data resource. The most straightforward way to use data is via data variables. To use data from a data resource, we can connect a data variable or usedata flow functions individually. Resource URL - external resource for data.Resource Schema - a schema, which defines the structure and type of data stored in the resource.Short description - a brief text description, used also when publishing the data resource for others to use via the Marketplace.Resource ID - an unique Identifier/name used to refer to the data resource.Here, you can see a list of all data resources configured for your app, and can create new ones via the Add data resource button on the top right corner.Īll data resources have several common properties: To define a new data resource, open the Data configurator via the global toolbar at the top. Custom resources found on the marketplace.REST API direct integration – direct integration to an external JSON-based API.On-device storage – data stored on the device/web browser itself cannot be shared between different devices.a client-side storage resource called Session or REST API integration called Incidents.Ĭurrently, the available data resource types are: A data resource defines access to such data, e.g. Typically, this means that the data is available online via an API, but it could also be stored on the device itself as a client-side storage. When we talk about data in the context of Composer apps, we mean data that is stored outside the context of the running app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |