14 results found

1. Better extensibility options for Search V2 Indexing

   We have a requirement on our project that requires us to change the behavior of the search indexing v2. In trying to do so, our development team ran into an issue where the class we needed to extend was not extensible (internal, sealed, or non overrideable methods).

   Basically what we are trying to do is remove the condition that excludes child products when fetching indexable products that is in line 896 of class Insite.Search.Shared.DocumentTypes.Product.Index.SearchV2.Models.Product (this is in version 5.2.2412.1705)

   What we would like to see changed is:

   1 - Make the SearchV2.Models.Product public instead of internal and remove the sealed keyword (and do the same for other classes in the SearchV2 and SearchV2.Models namespaces)

   2 - If possible, move the lines from 893 to 904 to a virtual method so we can override it - specifically this code:

   var indexableProducts = products
   .Except(inactiveStyleParents)
   .Where(p =>
   p.StyleParentId is null
   && (
   !p.IsDiscontinued
   || (productIdsWithQuantityOnHand.Contains(p.Id) && p.TrackInventory)
   )
   && p.IsActive
   && p.IndexStatus != 2
   )
   .ToArray();

   And it's not really just about this particular piece of code - in that class the entire ReadFromDatabase method has a lot of logic in it, is there any way to break some of that apart into virtual methods, or handler chains / pipelines and make it extensible?

   3 - Make the constructor of class Insite.Search.Shared.DocumentTypes.Product.Index.SearchIndexableProduct public instead of internal

   Without these extension points, we are currently forced to copy / paste a lot of classes from base code, and slightly modify a few of them, in order to achieve the desired functionality. Attached is a screenshot from our pull request showing all of the files we had to copy - the only ones we actually change are the ones highlighted in red.

   And again, this is not just about our specific requirement, but more of a request to open the entire Search V2 Indexing architecture to be more extensible. Right now it's pretty "locked down"

   We have a requirement on our project that requires us to change the behavior of the search indexing v2. In trying to do so, our development team ran into an issue where the class we needed to extend was not extensible (internal, sealed, or non overrideable methods).

   Basically what we are trying to do is remove the condition that excludes child products when fetching indexable products that is in line 896 of class Insite.Search.Shared.DocumentTypes.Product.Index.SearchV2.Models.Product (this is in version 5.2.2412.1705)

   What we would like to see changed is:

   1 - Make the SearchV2.Models.Product public instead of internal and remove the sealed… more

   •  

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Prevent bot spamming logs

   We often see a lot of errors in the application logs related to bots spamming the website with URL requests that do not even exist, quite often these end in .php extension; example: https://[ConfiguredCommerceURL]/admin/function.php. These seem to be attacks that try to find vulnerabilities on the website. While often times these are harmless, they do pollute the application logs, making it harder for developers to find actual errors that are worth reporting. This feature request is to simply capture that kind of spam requests and simply block them, without processing anything else (these often come with errors such as 'Unity.Exceptions.InvalidRegistrationException' that arise from trying to find dependencies), upon finding out that the request is simply not valid as there should simply not exist any PHP resources on a Configured Commerce website, they should simply be blocked without actually logging an error. If we want to keep these maybe they should be logged somewhere else than the application logs so they could be more easily analyzed? maybe a list of these requests including the origin IP address.

   We often see a lot of errors in the application logs related to bots spamming the website with URL requests that do not even exist, quite often these end in .php extension; example: https://[ConfiguredCommerceURL]/admin/function.php. These seem to be attacks that try to find vulnerabilities on the website. While often times these are harmless, they do pollute the application logs, making it harder for developers to find actual errors that are worth reporting. This feature request is to simply capture that kind of spam requests and simply block them, without processing anything else (these often come with errors such as 'Unity.Exceptions.InvalidRegistrationException'… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Inherit Product Assignments in Category Hierarchy for Rule Engine

   Current Behavior: In Optimizely, products are currently assigned only to the most specific (end-node) category within a 3-level taxonomy.
   For example, if the category tree is:

   Power Tools > Drills > Cordless Drills

   Then a product like a cordless drill is assigned only to the "Cordless Drills" category, and not to "Drills" or "Power Tools".

   Problem: This structure causes significant limitations when using the rule engine—specifically the “Product In Category” rule. Since products are not assigned to higher-level categories, those categories cannot be used effectively in rules.

   This creates a major pain point when building dynamic catalog restriction groups. Users are forced to assign rules at the lowest-level categories, resulting in excessive manual configuration and a time-consuming setup process.

   Proposed Enhancement: Enable category inheritance within the rule engine so that:

   If a product is assigned to a subcategory, it is implicitly considered part of all its parent categories.

   Rules applied to a higher-level category should automatically include products assigned to any of its descendant categories.

   Benefits:

   Significantly reduces the time and complexity required to build and maintain catalog rules.

   Makes the rule engine more intuitive and aligned with how category hierarchies are conceptually structured.

   Improves scalability and efficiency for merchandisers and admins managing large product catalogs.

   Current Behavior: In Optimizely, products are currently assigned only to the most specific (end-node) category within a 3-level taxonomy.
   For example, if the category tree is:

   Power Tools > Drills > Cordless Drills

   Then a product like a cordless drill is assigned only to the "Cordless Drills" category, and not to "Drills" or "Power Tools".

   Problem: This structure causes significant limitations when using the rule engine—specifically the “Product In Category” rule. Since products are not assigned to higher-level categories, those categories cannot be used effectively in rules.

   This creates a major pain point when building dynamic catalog restriction groups. Users… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Research & Design  ·  AdminFilip Åström (Product Manager, Optimizely) responded

   Thank you for submitting this request! We have added this item to our roadmap. Although we cannot guarantee a release date, we expect this feature to be available within the next 12 months.

4. Spire CMS - Identifying widgets missing content in current language

   In the Classic CMS, we were able to see a warning or indication style on widgets that did not have content in the current language. However, in Spire CMS, this visual indicator does not seem to be available.

   We would like a way to clearly identify in Spire CMS which widgets have been localized to the current language and which have not, similar to the warning indication available in Classic CMS.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. CMS backup

   I'd like to suggest implementing an automated backup system for the CMS to avoid potential data loss or mishaps. Currently, backups can be done manually, which could leave us vulnerable to issues such as data corruption, system failure, or human error.

   Automating backups (daily or even more frequently) with proper versioning and offsite storage would ensure data integrity, minimize downtime, and provide a reliable rollback option in case of any unforeseen events.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Attribute filters

   We would like the Attribute filters to have more form factors than simply a check box. Some attributes have to many options for this to be useful. we would like the option to use sliders when there are many number values, swatches to display colors, etc.

   •  

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. VMI - Create option to limit order number to the Max setting

   VMI is currently designed so that user is allowed to order more than max 'bin amount' (for example they know they are consuming more than usual they want the ability to order the necessary amount) While we will auto-fill 'up to the max' when ordering, the user can add 'more' than the max bin amount and is able to increase above max in the cart.

   Bunzl has a user case where they do not wish to follow this behavior. They have a user case which if a user enters a count above the "Max" the system will not create an order.

   VMI is currently designed so that user is allowed to order more than max 'bin amount' (for example they know they are consuming more than usual they want the ability to order the necessary amount) While we will auto-fill 'up to the max' when ordering, the user can add 'more' than the max bin amount and is able to increase above max in the cart.

   Bunzl has a user case where they do not wish to follow this behavior. They have a user case which if a user enters a count above the "Max" the system will not create an… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Power BI Integration with Optimizely Configured Commerce for one of the client

   The client requires seamless integration of Power BI reports directly within their Optimizely Configured Commerce site to enable:

   Real-time business analytics dashboards

   Embedded sales, inventory, and customer insights

   Interactive reporting for internal users

   To integrate Power BI reports into Optimizely Configured Commerce site, we need to whitelist the required DLLs.

   DLLs to Whitelist
   The following DLLs need to be whitelisted for Power BI integration:

   Microsoft.PowerBI.Api.dll

   Microsoft.Identity.Client.dll

   Microsoft.Rest.ClientRuntime.dll

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Request for an out of the box configuration setting for when sessions are fully expired

   Request for an out of the box configuration setting for when sessions are fully expired:

   • Session Expiration and let the client decide if they would like to redirect to Session Expired Page, or use Overlay with Session Expired Modal on same page.
   • In this setting we could also provide additional sub-setting with ability to enable a session expiration warning (admin can set the number of minutes)

   Incomplete Client-Side Inactivity Timeout: We have two different issues with this vulnerability,
   • If a customer steps away from their system without an automatic logout after a period of inactivity, there is a risk that others may access sensitive information. (They can’t take any action, however they can see all the information on that current page)
   • Customers believe they are still logged in while attempting to check out or submit orders, only to find themselves logged out unexpectedly. This can be frustrating for them.

   This issue was raised as a security vulnerability by security audit team and it’s also customer experience issue (they are not aware of session expiration). This is already in your tracker but it’s mentioned as “Working as Designed.” but it’s a security issue. Please consider this as a security fix.
   Incomplete Client-Side Inactivity Timeout Low When a user’s session expires, their active window is not redirected to a timeout or login page. Any information on the page remains exposed. Working as Designed. This is currently designed behavior on Storefront, any action on a website after session timeout will redirect user to SignIn page.

   Request for an out of the box configuration setting for when sessions are fully expired:

   • Session Expiration and let the client decide if they would like to redirect to Session Expired Page, or use Overlay with Session Expired Modal on same page.
   • In this setting we could also provide additional sub-setting with ability to enable a session expiration warning (admin can set the number of minutes)

   Incomplete Client-Side Inactivity Timeout: We have two different issues with this vulnerability,
   • If a customer steps away from their system without an automatic logout after a period of inactivity, there is… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Removed the ability to restore all site content in Production

    Remove the ability (or add in a configuration setting to disable the option) to rollback all site content in production. This configuration allow for the opportunity to wipe out all site content very easily.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Attribute Value Character Limit Raise

    I frequently run into products that have more data for specs category attribute values that exceed Optimizely's 255 character limit in Configured Commerce. My source system has a limit of 400. I was wondering if it would be possible to raise the limit in OPTI from 255 to 400 ? An example attribute is "Suitable For Use With" which often has long lists of applicable model numbers.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. PIM - Improve validation with trailing space characters

    The current PIM import process automatically strips trailing space characters from all fields before validating the import. This causes frustrating behavior when a category is named (accidentally or otherwise) with a trailing space character in it.

    The import validation strips the space characters from the file, which causes the import to fail with the "Category Name not found" error. The PIM admin then has no good way of identifying that the trailing space character is what is causing the issue since the error does not specify which category is the one not found.

    In order to avoid this, I would propose two potential solutions:

    A) Improve the category import validation to specify which category name is the one not found

    B) Add a system setting for the import process to accept trailing space characters as-is and not automatically remove them from the file before performing the validation

    The current PIM import process automatically strips trailing space characters from all fields before validating the import. This causes frustrating behavior when a category is named (accidentally or otherwise) with a trailing space character in it.

    The import validation strips the space characters from the file, which causes the import to fail with the "Category Name not found" error. The PIM admin then has no good way of identifying that the trailing space character is what is causing the issue since the error does not specify which category is the one not found.

    In order to avoid this, I would… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. product description

    There are no way to export all product description in bulk from Optimizely PIM. I want to be able to export the descriptions for both the main language and the translated languages.
    When I export only one product at a time it works. But having thousands of products in multiple languages is not sustainable. I want to be able to export all product descriptions in bulk.

    Also, the product description gets exported in "code format", meaning the symbols like "<p>" gets embedded in the text. It would be very good if the descriptions could be exported in a clean format without these symbols.

    There are no way to export all product description in bulk from Optimizely PIM. I want to be able to export the descriptions for both the main language and the translated languages.
    When I export only one product at a time it works. But having thousands of products in multiple languages is not sustainable. I want to be able to export all product descriptions in bulk.

    Also, the product description gets exported in "code format", meaning the symbols like "<p>" gets embedded in the text. It would be very good if the descriptions could be exported in a clean format… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Add the ability to grant impersonate permissions to custom roles

    I want to be able to create a custom role for the admin console users that while given limited permissions through the Application Dictionnary would also be granted the ability to impersonate website users. Currently, the impersonate feature is limited to 4 roles: ISCSystem, ISCImplementer, ISCAdmin, ISCUser. Being able to customize the CanCurrentUserImpersonateAnotherUser method used by the AccountController would give more flexibility.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminFilip Åström (Product Manager, Optimizely) responded

    We appreciate you bringing this to our attention. Our team will investigate further and keep you updated.