Add conditions to more extension manifests #20390
jemayn
started this conversation in
Features and ideas
Replies: 1 comment
-
Agreed, being able to specify a default value for document types (not having to rely on blueprint) and for specific properties (alias) on the document type would be welcome, it would indeed support a lot of use cases out there |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've had a few extensions now where I wanted to add a condition to them only to find that their manifests do not support conditions.
I find it hard to understand why they are not just a standard thing in the UmbExtensionManifest?
I don't have a full overview of the extensions that have and do not have condtions enabled, but I specifically have wanted to use them on these:
ManifestBackofficeEntryPoint
- I could understand why this was omitted, but it could be very useful for these to be able to do something based on for example usergroups.ManifestPropertyValuePreset
- this just seems like a no-brainer, being able to limit this to specific doctypes is a very common usecase - especially with this being a replacement for SendingContentNotifications in v13 where that was the norm.Beta Was this translation helpful? Give feedback.
All reactions