@IsnardMalafaia

There are several ways you can store/save every request and response from a Service REST rules in PEGA to a database table. Here are a few options:

1. Use PEGA's built-in Audit feature: PEGA's Audit feature allows you to track and store various types of system events, including service requests and responses. You can enable auditing for your Service REST rules and configure it to store the audit records in a database table. To do this, you need to create a database table to store the audit records and configure the Audit settings for your Service REST rules to use this table.

2. Use PEGA's database connector: PEGA provides a database connector rule that you can use to connect to external databases and perform database operations. You can create a custom activity to insert the request and response data into a database table using the database connector rule. You can then call this activity from your Service REST rules to store the data in the database table.

3. Use a third-party logging framework: You can use a third-party logging framework, such as Log4j, to log the request and response data in your Service REST rules. You can configure the logging framework to store the log data in a database table. This approach requires additional configuration and integration work to set up the logging framework and database connectivity.

Ultimately, the best way to store/save every request and response from a Service REST rules in PEGA to a database table depends on your specific requirements and constraints. You should consider factors such as the volume and frequency of requests and responses, the size of the data, the performance requirements, and the available infrastructure and resources.