2 results found

1. 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

   New  ·  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

2. 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

   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