- ABP Framework version: v5.3.3
- UI type: Blazor
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): yes
I've created some custom features, it seems that I can edit them at the 'edition' level in the blazor interface, but not at the tenant level. The textbox is disabled.
public class MailerFeatures : FeatureDefinitionProvider
{
public static string GroupName = "Mailer";
public static string MaxEmail => FeatureName("MaxEmail");
public override void Define(IFeatureDefinitionContext context)
{
var group = context.AddGroup(GroupName);
var maxUsers = group.AddFeature(
MaxEmail,
defaultValue: "1",
valueType: new FreeTextStringValueType(
new NumericValueValidator(0, 1000000)), isVisibleToClients: true);
// Here I tried settings the providers, made no difference.
//maxUsers.WithProviders(new string[] { TenantFeatureValueProvider.ProviderName, EditionFeatureValueProvider.ProviderName });
}
private static string FeatureName(string name)
{
return $"{GroupName}.{name}";
}
}
This is the disabled textarea:
11 Answer(s)
-
0
-
0
Hi,
Some of your own
Edition
configurations can restrict editing values and hence it seems to you as disabled. Could you have a look at here, please?Regards.
-
0
The point is that this is the wrong way around, and I'm guessing by mistake, not by design.
Specific items would always override group permissions. To use a file system as an example, a file permission would override the inherited folder permission. With ABP you have it the other way around which has no use case that I can see.
It should be:
Tenant default permissions are inherited from Edition, but permissions set on the tenant are not overwritten by Edition.
Example. If a feature is causing an issue for a specific customer, we would disable it on their tenant, not the entire edition.
-
0
With regard to the message from @dmeagor, it does seem that it is not the correct functionality. Why did you close the ticket?
Is there any way that it can be made to function in a desirable way?
Hi Luke,
Sorry to close the issue. I thought your issue was solved hence ignored @dmeagor. I think you're in the same team. I've raised your issue with the team and asap will return to you asap.
Regards.