{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":10016,"path":"employee-service-management/employee-experience-foundation/customizing-approval-notifications.md","title":"Customizing approval notification fields","bundle":null,"doc_type":null,"release":"australia","body":"\n# Customizing approval notification fields\n\nYou can customize the approval notification fields by creating the methods in a script include.\n\n**Note:** The topic uses the API names of the script includes.\n\nActionable Notifications are sent for approval and comments on tickets. You can customize the fields displayed in the approval notifications by creating methods in the `sn_now_teams.ApprovalsVAUtil()` script include. These methods override the ones in the `sn_now_teams.ApprovalsVAUtilSNC()` script include.\n\nFor information about script includes, see [Script includes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/c_ScriptIncludes.md).\n\n## Creating the method\n\nThe notification logic calls a method based on the table that the approval record is created for. The method names follow this format: get<TableName>Fields\\(\\), which you can use to create a method for any table in the base system.\n\n**Note:** Custom tables aren’t supported for approval notifications.\n\nFor example: If the table name is sc\\_request, the method name is getScRequestFields\\(\\). If the table name is incident, the method name is getIncidentFields\\(\\).\n\n## Overriding the method fields\n\nThe methods that you create in the `sn_now_teams.ApprovalsVAUtil()` script include override the ones in `sn_now_teams.ApprovalsVAUtilSNC()`.\n\nWhile creating the method, you can enter the field names that are displayed in the approval notification.\n\n-   For TASK extended tables, you can dot-walk to the referenced field by using the *sysapproval* field.\n\n    For example:\n\n    ```javascript\n    getChangeRequestFields: function() {\n     return {\n      \"fields\": [\"sysapproval.number\", \"sysapproval.short_description\", \"sysapproval.risk\", \"sysapproval.start_date\", \"state\"]\n      }\n    },\n    ```\n\n-   For NON-TASK tables, you must enter the table fields directly.\n\n    For example:\n\n    ```javascript\n    getKbKnowledgeFields: function() {\n     return {\n      \"fields\": [\"number\", \"short_description\", \"kb_knowledge_base\", \"author\", \"workflow_state\"]\n      }\n    },\n    ```\n\n-   You can create a default method, getDefaultFields\\(\\), which is used if the system doesn’t find a method for the table in the approval record. The field references follow the TASK extended tables.\n\n    For example:\n\n    ```javascript\n    getDefaultFields: function() {\n     return {\n      \"fields\": [\"sysapproval.number\", \"sysapproval.requested_for\", \"sysapproval.price\", \"sysapproval.due_date\", \"state\"]\n      }\n    },\n    ```\n\n\n**Parent Topic:**[Configure IT Service Management integration with Microsoft Teams](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/employee-experience-foundation/sn-ms-teams-config-it.md)\n\n"}}