{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":33856,"path":"it-service-management/service-operations-workspace/mra-extension-points-batch-processing-sow.md","title":"Extension points for batch processing in Service Operations Workspace","bundle":null,"doc_type":null,"release":"australia","body":"\n# Extension points for batch processing in Service Operations Workspace\n\nUse the implementation extension point to create implementations and execute batch processing to update multiple records, which improves the performance of the system.\n\nThe Multiple Record Associator \\(MRA\\) component enables you to create implementation extension points for batch processing of multiple records.\n\nTo view the extension points that are available by default, navigate to **All** > **System Extension Points ** > **Scripted Extension Points**. You can select the **Create implementation** option to create an implementation extension point.\n\nWhen you have multiple records to update, a business rule executes and updates once for each record, which can affect the performance of the system. Instead of executing the business rule for each record, you can use the `RelatedListIncidentItemUpdateHandler` script include to execute batch processing for updating multiple records.\n\nYou can use the `RelatedListIncidentItemUpdateHandler` script include to update multiple records with batch processing. For example, you could use this script include when associating and updating multiple child incidents with a parent incident.\n\nThe **RelatedListIncidentItemUpdateHandler** script include contains the `global.RelatedListItemUpdateHandler` implementation extension point and is used when batch processing multiple records on a related list.\n\nThe extension point used in the **related\\_list\\_edit\\_helper** script include uses API to facilitate invoking custom code. This extension point overrides the execution of the business rule to ensure that the implementation extension point is executed when updating multiple records instead of the business rule. You can also add a business rule that must be overridden. When multiple records are updated, this script include is triggered, and batch processing occurs that bypasses that business rule.\n\nThe `RelatedListIncidentItemUpdateHandler` script include contains the following functions:\n\n-   Initialize – Executes before multiple records are updated.\n-   Post update – Executes after multiple records are updated.\n\n\\[Omitted image \"related\\_list\\_handler\\_scriptinclude.png\"\\] Alt text: RelatedListIncidentItemUpdateHandler script includes\n\n**Parent Topic:**[Incident Management in Service Operations Workspace reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/service-operations-workspace/sow-im-reference.md)\n\n"}}