Skip to content

Commit 7aedabc

Browse files
nwcmnwcm
committed
metadata field fieldManageability set to SubscriberControlled
1 parent 5c3793d commit 7aedabc

9 files changed

Lines changed: 9 additions & 9 deletions

File tree

‎trigger-actions-framework/main/default/objects/DML_Finalizer__mdt/fields/Bypass_Execution__c.field-meta.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<defaultValue>false</defaultValue>
55
<description>Set this to true to bypass this Trigger Action from being called</description>
66
<externalId>false</externalId>
7-
<fieldManageability>DeveloperControlled</fieldManageability>
7+
<fieldManageability>SubscriberControlled</fieldManageability>
88
<inlineHelpText>Set this to true to bypass this Trigger Action from being called</inlineHelpText>
99
<label>Bypass Execution</label>
1010
<type>Checkbox</type>

‎trigger-actions-framework/main/default/objects/DML_Finalizer__mdt/fields/Bypass_Permission__c.field-meta.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
<fullName>Bypass_Permission__c</fullName>
44
<description>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will be bypassed if the running user has the custom permission identified.</description>
55
<externalId>false</externalId>
6-
<fieldManageability>DeveloperControlled</fieldManageability>
6+
<fieldManageability>SubscriberControlled</fieldManageability>
77
<inlineHelpText>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will be bypassed if the running user has the custom permission identified.</inlineHelpText>
88
<label>Bypass Permission</label>
99
<length>255</length>

‎trigger-actions-framework/main/default/objects/DML_Finalizer__mdt/fields/Required_Permission__c.field-meta.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
<fullName>Required_Permission__c</fullName>
44
<description>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will only execute if the running user has the custom permission identified.</description>
55
<externalId>false</externalId>
6-
<fieldManageability>DeveloperControlled</fieldManageability>
6+
<fieldManageability>SubscriberControlled</fieldManageability>
77
<inlineHelpText>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will only execute if the running user has the custom permission identified.</inlineHelpText>
88
<label>Required Permission</label>
99
<length>255</length>

‎trigger-actions-framework/main/default/objects/Trigger_Action__mdt/fields/Bypass_Execution__c.field-meta.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
<description
66
>Set this to true to bypass this Trigger Action from being called</description>
77
<externalId>false</externalId>
8-
<fieldManageability>DeveloperControlled</fieldManageability>
8+
<fieldManageability>SubscriberControlled</fieldManageability>
99
<inlineHelpText
1010
>Set this to true to bypass this Trigger Action from being called</inlineHelpText>
1111
<label>Bypass Execution</label>

‎trigger-actions-framework/main/default/objects/Trigger_Action__mdt/fields/Bypass_Permission__c.field-meta.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<description
55
>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will be bypassed if the running user has the custom permission identified.</description>
66
<externalId>false</externalId>
7-
<fieldManageability>DeveloperControlled</fieldManageability>
7+
<fieldManageability>SubscriberControlled</fieldManageability>
88
<inlineHelpText
99
>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will be bypassed if the running user has the custom permission identified.</inlineHelpText>
1010
<label>Bypass Permission</label>

‎trigger-actions-framework/main/default/objects/Trigger_Action__mdt/fields/Required_Permission__c.field-meta.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<description
55
>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will only execute if the running user has the custom permission identified.</description>
66
<externalId>false</externalId>
7-
<fieldManageability>DeveloperControlled</fieldManageability>
7+
<fieldManageability>SubscriberControlled</fieldManageability>
88
<inlineHelpText
99
>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will only execute if the running user has the custom permission identified.</inlineHelpText>
1010
<label>Required Permission</label>

‎trigger-actions-framework/main/default/objects/sObject_Trigger_Setting__mdt/fields/Bypass_Execution__c.field-meta.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
<description
66
>Set this to true to bypass all Trigger Actions from being called on this sObject</description>
77
<externalId>false</externalId>
8-
<fieldManageability>DeveloperControlled</fieldManageability>
8+
<fieldManageability>SubscriberControlled</fieldManageability>
99
<inlineHelpText
1010
>Set this to true to bypass all Trigger Actions from being called on this sObject</inlineHelpText>
1111
<label>Bypass Execution</label>

‎trigger-actions-framework/main/default/objects/sObject_Trigger_Setting__mdt/fields/Bypass_Permission__c.field-meta.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<description
55
>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will be bypassed if the running user has the custom permission identified.</description>
66
<externalId>false</externalId>
7-
<fieldManageability>DeveloperControlled</fieldManageability>
7+
<fieldManageability>SubscriberControlled</fieldManageability>
88
<inlineHelpText
99
>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will be bypassed if the running user has the custom permission identified.</inlineHelpText>
1010
<label>Bypass Permission</label>

‎trigger-actions-framework/main/default/objects/sObject_Trigger_Setting__mdt/fields/Required_Permission__c.field-meta.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<description
55
>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will only execute if the running user has the custom permission identified.</description>
66
<externalId>false</externalId>
7-
<fieldManageability>DeveloperControlled</fieldManageability>
7+
<fieldManageability>SubscriberControlled</fieldManageability>
88
<inlineHelpText
99
>Optional. Enter the API name of a permission. If this field has a value, then the triggers on this object will only execute if the running user has the custom permission identified.</inlineHelpText>
1010
<label>Required Permission</label>

0 commit comments

Comments
 (0)