Activity log is used in alert framework to pass dynamic values to message template of the alert. For OOTB alerts the activityLog is defined in the service and is not available for modification. However, for approval related events, activity log mapper class can be configured to have extra fields in activity log from the transaction dto. This mapper class can be configured based on the task id. Steps to write custom activity log mapper class.

• Create a mapper class and implement interface com.ofss.digx.app.approval.alert.mapper.ITransactionActivityLogMapper.
• Override com.ofss.digx.app.alerts.dto.eventgen.ActivityLog getActivityLogForTransaction(com.ofss.digx.app.approval.dto.transaction.TransactionDTO transactionDTO) method to provide mapping logic.
• Make an entry in digx_fw_config_all_b table with category_id ‘transaction_activity_log_mapper’, prop_id as task_code of the transaction going through approval and prop_value as fully qualified name of above custom class.