CRM integrations and automation

Understand automatic currency-rate cron updates

Follow this guide to review the after-cron-run currency-rate action. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Inventory staff, warehouse managers, finance teams and administratorsPermission: Relevant inventory capabilityModule v1.5.2
Jump to steps
Where to goAdmin Area → Setup → Settings → Cron Job
Before you start
  • Verify the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What you’ll accomplish

Review the after-cron-run currency-rate action. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Admin Area → Setup → Settings → Cron Job.
  2. Select the record or action required for understand automatic currency-rate cron updates.
  3. Complete the displayed fields and choices described in this guide.
  4. Save, submit, approve or confirm the action as shown on screen.
  5. Refresh the relevant list, record or report and verify the expected result.

Fields and options to review

WorkspaceAdmin Area → Setup → Settings → Cron Job
ActionCheck the after-cron-run currency-rate action.

Rules the system enforces

  • Only controls rendered by the supplied module are documented; hidden AJAX helpers are mapped to their visible parent workflow.
  • Core CRM record permissions and module permissions are both enforced where the code checks them.

How to confirm it worked

  • The understand automatic currency-rate cron updates action completes without a validation or permission error.
  • The affected record, stock balance, response, session or style reflects the saved state.
  • Audit, notification, report or portal evidence appears only where the module code creates it.

Security, privacy and operational checks

  • Use a controlled test record before applying changes to live inventory, recipients, visitor tracking or global styling.
  • Grant only the minimum module and core CRM capabilities needed for the task.