Is your feature request related to a problem? Please describe.
In order to reduce the number of sfpegCard configuration records and sfpegCardCmp component conditional
display conditions in Lightning pages, it would be great to have the ability to dynamically hide sections within the sfpegCardCmp component.
Describe the solution you'd like
In the sfpegCard configuration, add a hidden property on section definitions,
Describe alternatives you've considered
Enforce a context merge on the sfpegCard configuration to automatically set the value of the hidden properties
out of any available boolean merge field (e.g. {{{NPERM.CustomPermission1}}}, see sfpegMergeUtl).
Additional context
Even though, FLS are automatically applied by the underlying lightning-record-edit-form, it would be great to have this hidden property directly at field definition level to cope with cases where Users may have access to a field but never see it in layouts.
Is your feature request related to a problem? Please describe. In order to reduce the number of sfpegCard configuration records and sfpegCardCmp component conditional display conditions in Lightning pages, it would be great to have the ability to dynamically hide sections within the sfpegCardCmp component.
Describe the solution you'd like In the sfpegCard configuration, add a hidden property on section definitions,
Describe alternatives you've considered Enforce a context merge on the sfpegCard configuration to automatically set the value of the hidden properties out of any available boolean merge field (e.g.
{{{NPERM.CustomPermission1}}}, see sfpegMergeUtl).Additional context Even though, FLS are automatically applied by the underlying lightning-record-edit-form, it would be great to have this hidden property directly at field definition level to cope with cases where Users may have access to a field but never see it in layouts.