kris/afv-library
1
0
Fork 0
mirror of https://github.com/forcedotcom/afv-library.git synced 2026-07-30 03:09:50 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

W-21585248 Updating generate-permission-set skill to improve metadata generation (#47)

Browse Source 
* more changes

* rename file

* change name back

---------

Co-authored-by: Hemant Singh Bisht <hsinghbisht@salesforce.com>
This commit is contained in:
irisli0 2026-03-18 11:08:57 -07:00 committed by GitHub
parent 690f722a0b
commit 0d668f51e7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
skills/generate-permission-set/SKILL.md
View File

@ -1,6 +1,6 @@
--- ---
name: generate-permission-set name: generate-permission-set
description: Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions. Use when creating or editing permission set metadata, PermissionSet XML, object permissions, field-level security (FLS), tab visibility, or deploying permission sets. description: Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions. Use this skill when creating or editing permission set metadata, object permissions, field-level security (FLS), tab visibility, or deploying permission sets.
compatibility: Salesforce Metadata API v60.0+ compatibility: Salesforce Metadata API v60.0+
metadata: metadata:
author: afv-library author: afv-library
@ -59,6 +59,9 @@ Define field permissions for sensitive or custom fields:
- Required fields must NEVER appear in list of field permissions. Granting field-level security on required fields is not allowed by the platform and will cause deployment failure. - Required fields must NEVER appear in list of field permissions. Granting field-level security on required fields is not allowed by the platform and will cause deployment failure.
- Before adding any field, confirm from the object metadata that the field exists and is not required - Before adding any field, confirm from the object metadata that the field exists and is not required
- A field is required when its metadata contains `<required>true</required>`: - A field is required when its metadata contains `<required>true</required>`:
- Formula fields cannot be editable
- Master-detail fields are required fields on the child (detail) object
```xml ```xml
<fields> <fields>
<fullName>FieldName__c</fullName> <fullName>FieldName__c</fullName>
@ -114,9 +117,9 @@ Make applications and tabs visible to users:
- <visible> can be true or false - <visible> can be true or false
**Tab visibility options:** **Tab visibility options:**
- `Visible`: Always shown - `Visible`: The tab is available on the All Tabs page and appears in the visible tabs for its associated app. Can be customized.
- `Available`: Available but not default - `Available`: The tab is available on the All Tabs page. Individual users can customize their display to make the tab visible in any app
- `Hidden`: Not visible - `None`: Not visible
**CRITICAL - Tab Naming:** **CRITICAL - Tab Naming:**
- Custom object tabs: MUST include the __c suffix (e.g., MyCustomObject__c) - Custom object tabs: MUST include the __c suffix (e.g., MyCustomObject__c)