My ideas

Control center currently lets users create a restriction with both the fieldtype and category set. This is a confusing user experience particularly when they are allowed to choose a category and a fieldtype that is not in that category. The better...

How: A tickbox in the settings area to indicate that you want to keep/maintain already existing content. Why: when I need to go through a number of entities and I want to keep existing content, I don't don't want to turn languages on & off all...

How: Add a REST API call which returns a list of all the connectorIds and the count of connectorstates Why: Retrieve all the connectorstates with /api/v1.0.0/extensions/connectorstates can be quite overwhelming, and unneeded. Example Result: Conne...

Hi inriver It doesn't seem possible yet to set the number of characters in the "Inspire me" module. Is this something on the improvements list? If not, I would like to create a feature request for this. With kind regards, Koen Pijnenburg

Please, fill in the below fields to enable the processing of your idea. Who would benefit? Control center users What impact would it make? Ability to manage the rules in a more user friendly way How should it work? Ordering: As a user I want to be...

How: We would like a way to download only the resource files without also getting the data about the resources. Why: Sometimes it's only relevant to get access to the media resources and the data about the resources is not of interest. We would li...

When a certain language (we can call it language1) has been used in an entity's field or in a control center Table, and that language1 is removed from the Model's list of languages, language1 data is still retained and would need an update to the ...

How: Show field FieldID's when configuring Inspire. Example: Brand (ItemChainwheelBrand) Why: It is unclear what field to select at the moment, because many fields have the same name, but for different category of parts For Who: For inspire config...

How: Users would like to be able to sort their Workspaces into a folder structure. Why: To be able to organize many Workspaces into folders will make them easier to find and maintain. It will also mimic how the Workarea structure works. For Who: A...

How: REST API support for managing (administrating) Workflows. Why: In order to maintain the setup in one place and be able to deploy between different environments, as well as having a backup for disaster recovery purposes. For Who: All customers...