Delete Records

overview the delete record action enables you to programmatically delete records from swimlane applications within playbooks the action identifies records by their unique tracking id (trackingfull) and removes them from the specified application key benefits native action integrated directly into the playbook builder for streamlined workflow creation simple identification uses tracking id to uniquely identify records for deletion flexible inputs application and tracking id can be static values or dynamic references from upstream actions at most once execution ensures the record is deleted exactly once, even if the playbook is retried error handling provides clear error messages when records or applications are not found inputs the delete record action requires the following inputs required inputs tracking id the tracking id (trackingfull) of the record to delete this is a unique identifier for each record in the application can be a static value (e g , "inc 2024 001" ) can reference a playbook property from upstream actions (e g , $actions createrecord result\['tracking id'] ) can reference playbook inputs (e g , $inputs recordtrackingid ) can be an expression that evaluates to a tracking id application selection you must provide either application id the unique identifier of the application containing the record, or application name the name of the application containing the record note you must provide either applicationid or applicationname , but not necessarily both if both are provided, applicationid takes precedence configuring the delete record action step 1 select application from the inputs tab, select an application choose from the dropdown list of available applications, or use an expression to reference an application id or name dynamically step 2 configure tracking id the tracking id field automatically displays in the inputs tab set the tracking id value by clicking the + icon next to the tracking id field choose from playbook property select a property from upstream actions or playbook inputs expression write an expression to calculate the tracking id dynamically static value enter a tracking id directly example to delete a record that was created earlier in the playbook click the + icon next to tracking id select playbook property navigate to $actions createrecordname result\['tracking id'] step 3 apply changes click apply to save your configuration outputs the delete record action provides the following outputs success output when the record is deleted successfully, the action returns result a boolean value ( true ) indicating the deletion was successful example access the result in downstream actions error output if the record deletion fails, the action returns error error information containing details about why the deletion failed common error scenarios application not found the specified application id or name does not exist record not found the record with the specified tracking id does not exist in the application permission errors the playbook or user does not have permission to delete records in the application invalid tracking id the tracking id format is invalid or empty use cases example 1 delete record after processing scenario delete a temporary record after it has been processed and archived add a create record action to create a temporary record process the record (e g , extract data, send notifications) add a delete record action application same application as the create record action tracking id $actions createrecordname result\['tracking id'] the temporary record is deleted after processing completes example 2 conditional record deletion scenario delete records that meet certain criteria add a search records action to find records matching criteria add a loop action to iterate over search results inside the loop, add a delete record action application reference from search results tracking id $loop value\['tracking id'] only records matching the criteria are deleted example 3 delete record from event data scenario delete a record when a specific event is received configure an event trigger to receive events add a delete record action map inputs application $event data applicationname tracking id $event data recordtrackingid the record is deleted when the event is received best practices verify before deleting consider adding a conditional check or confirmation step before deleting important records handle errors gracefully use on failure paths to handle deletion errors, especially when records might not exist use tracking ids from upstream actions reference tracking ids from create record or search records actions to ensure accuracy test with sample data test your delete operations with sample records before deploying to production consider record dependencies be aware that deleting a record may affect related records or workflows that reference it log deletions consider logging deleted record tracking ids for audit purposes use conditions add conditional logic to only delete records under specific circumstances troubleshooting record not found error verify the tracking id is correct and matches an existing record ensure the tracking id is from the correct application check that the record hasn't already been deleted application not found error verify the application id or name is correct ensure the application exists and is accessible check that application references are properly formatted permission errors verify the playbook has permission to delete records in the selected application check that the user running the playbook has appropriate access ensure the application allows record deletion operations tracking id not available if referencing from upstream actions, ensure the action completed successfully verify the upstream action returns a tracking id in the expected format check that the property path is correct (e g , $actions actionname result\['tracking id'] ) deletion fails silently check the error output for specific error messages verify the record exists before attempting deletion review playbook execution logs for detailed error information