Okay, I will check and update you
Okay so once I am done with all, then it will work and hide form permission when I disable that tour feature right?
But if the feature tour is not checked, then also get permission?
Hi,
We have deployed the diagnostic services and collected the logs. Please find the detailed diagnostic output attached in the email.
Thanks
Hello i have created another query please reply in that
No you did not understand what i am asking
i have check this query also in administation host and tenant databse
SELECT * FROM AbpFeatureValues WHERE Name LIKE '%TourModule%' OR Name LIKE '%TourService%' ORDER BY ProviderName, ProviderKey;
no record
ABP Commercial v9.2.0, .NET 9.0
Features are configured at Host level via SaaS Tenant management. When TourModule.TourService feature is disabled for a tenant, that tenant's Permission Management UI still shows all Tour permissions.
Tenant Edition: standard
Feature definition (TMSMSFeature.cs):
public const string GroupName = "TourModule"; public const string Tour = GroupName + ".TourService"; // = "TourModule.TourService"
Feature provider (FeatureProvider.cs):
myGroup.AddFeature(TMSMSFeature.Tour, defaultValue: "false", displayName: LocalizableString.Create<TourServiceResource>("TourServiceModule"), valueType: new ToggleStringValueType());
Permission definitions (all Tour permissions have .RequireFeatures):
var tourCategoryPermission = myGroup.AddPermission( TourServicePermissions.TourCategories.Default, L("Permission:TourCategories")).RequireFeatures(TMSMSFeature.Tour); tourCategoryPermission.AddChild(TourServicePermissions.TourCategories.Create, L("Permission:Create")).RequireFeatures(TMSMSFeature.Tour); tourCategoryPermission.AddChild(TourServicePermissions.TourCategories.Edit, L("Permission:Edit")).RequireFeatures(TMSMSFeature.Tour); tourCategoryPermission.AddChild(TourServicePermissions.TourCategories.Delete, L("Permission:Delete")).RequireFeatures(TMSMSFeature.Tour);
All permissions in TourServicePermissionDefinitionProvider.cs follow this same pattern with .RequireFeatures(TMSMSFeature.Tour).
**Additional issue: **Some permissions generated by ABP Suite do NOT include .RequireFeatures(). When we generate a new entity table using ABP Suite, the auto-generated permission definitions are created without .RequireFeatures(). For example:
// ABP Suite generates this (no .RequireFeatures): var tourGlobalMarkupPermission = myGroup.AddPermission( TourServicePermissions.TourGlobalMarkups.Default, L("Permission:TourGlobalMarkups")); Can ABP Suite be configured to automatically add .RequireFeatures() when generating permissions? Or is there a way to set this at the group level so all child permissions inherit it?
Screenshots attached:
Feature Management UI showing TourModule disabled for "standard" edition The permission management UI still showing Tour permissions for that tenant
Expected:
When TourServiceModule feature is disabled at Host level for a tenant (or its edition), Tour permissions should be hidden from that tenant's Permission Management UI. ABP Suite should support adding .RequireFeatures() automatically during entity generation.
This screenshot for the tenant feature
This from edition feature.
Screenshot of the Feature Management UI with TourModule disabled — and please note whether you're viewing it as Host or as a specific Tenant
see feature only able to see in host under saas of tenants tabs, okay?
and permission I am seeing under tenant login and roles section
The feature values from the database:
no record in tenant
Which ABP version you're using for this environment
ABP Commercial v9.2.0 with .NET 9.0
We checked our TourService backend. All permissions already have .RequireFeatures() configured:
TMSMSFeature.cs:
public const string GroupName = "TourModule"; public const string Tour = GroupName + ".TourService"; // = "TourModule.TourService"
FeatureProvider.cs:
myGroup. AddFeature(TMSMSFeature.Tour, defaultValue: "false", ...);
TourServicePermissionDefinitionProvider.cs:
Every permission already has .RequireFeatures(TMSMSFeature.Tour)—for example:
myGroup.AddPermission(TourServicePermissions.TourCategories.Default, ...) .RequireFeatures(TMSMSFeature.Tour); tourCategoryPermission.AddChild(TourServicePermissions.TourCategories.Create, ...) .RequireFeatures(TMSMSFeature.Tour);
All permissions in the file follow this pattern. So the issue is not missing .RequireFeatures() — it's already there on every permission. Despite disabling the feature in the Feature Management UI, permissions still appear. Could this be a framework-level issue with permission UI not respecting RequireFeatures when listing?