Settings and activity
4 results found
-
1 vote
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Thank you for submitting this request! While we do allow configuration of max character limits in the Application Dictionary for some fields; we do have a database nvarchar limit of 255 characters for Attribute field which cannot be easily increased at this time and could cause additional risks.
Do you frequently have attributes greater than this limit or is this an edge case for the "Suitable For Use With" use case?
There are current alternatives for this particular use case that could be approached by reaching out to an implementation partner customize it using the extensions table.
We do encourage facetable attributes to be as small and 'normalized' as possible. If these model numbers/data were normalized in ERP or integration layer it could be brought over as individual attributes. As individual attributes the users on the front end can interact with them with greater flexibility. -
2 votes
An error occurred while saving the comment Thank you for submitting this request! We have updated this request status to Gathering Feedback for future consideration and prioritization.
Sliders, and Swatches have been mentioned to which I'll assume are currently the 'most important' options which are missing. Please feel free to add more comments to this request if there are other important display options to keep in consideration.
-
1 vote
An error occurred while saving the comment Thank you for submitting this request!
Questions regarding the flexibility of this type of control:
1. Is this a setting that would be necessary to change based on the Site/Customer/Location?
2. Would there be a time where one location or customer would be allowed to purchase over max where another would not?
We may be reviewing and improving the VMI-ReOrder website flow in the near future, and I would like to review this type of setting in relation to the upcoming project. Having a better understanding of the desired flexibility will help ensure we are keeping the desired use cases in mind.
Thank you for submitting this request! I believe this is being reported based on an earlier version of our application and has been resolved, please review the changes that have been made and if there are still ongoing concerns. We have made a number of changes to help protect our client users from making unintended changes, using this setting improperly, resulting in a destructive action.
Below are the changes that have been released in Cloud between December 2023 and January 2024 (screenshot is attached to this request for visual display) -
1. Limited User Role Option to a single 'high level CMS Administrator' user role only, and hid the option from view for all other user roles
2. Renamed from 'Restore Content' to 'Sitewide Content Reset' and move under Content Management alongside "Import/Export Content" and "Redo Page State"
3. Improved description within the modal presented to the User
4. Disallow and rename 'continue' button - Empty text box for User to fill in is present to confirm their action, once the user enters their full username the "Reset" button becomes active