loan_transactions.rb

[geekelo]

FILE

# frozen_string_literal: true

ActiveAdmin.register LoanTransaction do
  actions :all, except: [:new, :create, :destroy]
  includes :user, :transfer

  config.sort_order = 'created_at_desc'

  menu parent: 'Loans & Insurance', label: 'Loans'
  # See permitted parameters documentation:
  # https://github.com/activeadmin/activeadmin/blob/master/docs/2-resource-customization.md#setting-up-strong-parameters
  #
  # Uncomment all parameters which should be permitted for assignment
  #
  permit_params :order, :order_date, :product_slug, :order_key, :status, :active

  index do
    selectable_column
    id_column
    column :user
    column 'Interest' do |loan_transaction|
     loan_transaction.interest
    end
    column :transfer
    column :status
    column :active
    column :order
    column 'Loan Item' do |loan_transaction|
      loan_transaction.product_slug
    end
    column :order_date
    column :created_at
    column :updated_at
    actions
  end
end

[geekelo]

This ActiveAdmin configuration sets up an admin interface for managing LoanTransaction records. The interface is designed to allow for viewing and updating existing records while preventing the creation or deletion of records. Here's a detailed explanation:

1. Menu Configuration

• menu parent: 'Loans & Insurance', label: 'Loans':
  • This line places the LoanTransaction resource under the "Loans & Insurance" menu in the ActiveAdmin dashboard with the label "Loans."

2. Actions Configuration

• actions :all, except: [:new, :create, :destroy]:
  • This configuration allows all actions (e.g., index, show, edit, update) except for new, create, and destroy. Admins can view and edit existing loan transactions, but they cannot create new ones or delete existing ones.

3. Includes

• includes :user, :transfer:
  • This line includes the associated user and transfer records in the query, which can help optimize the queries by reducing the number of database calls when displaying related data in the index view.

4. Sorting Configuration

• config.sort_order = 'created_at_desc':
  • This sets the default sorting order for the index page of the LoanTransaction resource. The records will be sorted by the created_at field in descending order, showing the most recent transactions first.

5. Permitted Parameters

• permit_params :order, :order_date, :product_slug, :order_key, :status, :active:
  • This specifies the attributes that can be mass-assigned in the admin interface. It ensures that only these listed attributes can be updated, which helps protect against mass-assignment vulnerabilities.

6. Index Page Configuration

• index do:

  • This block defines how the LoanTransaction records will be displayed in the index view.

  • Columns:

  • selectable_column: Adds checkboxes to each row for batch actions.

  • id_column: Displays the ID of each LoanTransaction.

  • column :user: Displays the associated user for each transaction.

  • column 'Interest' do |loan_transaction|: Custom column displaying the interest associated with the loan transaction.

  • column :transfer: Displays the associated transfer record.

  • column :status: Displays the status of the transaction.

  • column :active: Displays whether the transaction is active.

  • column :order: Displays the order associated with the transaction.

  • column 'Loan Item' do |loan_transaction|: Custom column displaying the product_slug (the loan item).

  • column :order_date: Displays the date the order was made.

  • column :created_at: Displays the date the transaction was created.

  • column :updated_at: Displays the date the transaction was last updated.

  • actions: Adds standard edit, view, and delete actions to each row, though delete actions are disabled by the actions configuration.

Summary

This ActiveAdmin configuration provides a well-structured interface for viewing and managing LoanTransaction records. Admins can filter and sort through transactions, view detailed information, and edit records as needed. By excluding actions such as creating or deleting records, the configuration ensures that only existing data can be managed, which may be a deliberate choice to maintain data integrity for loan transactions.