Understand the unexposed compliance-sync limitation

Do not expect a staff button or controller route to call the model sync method. 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.

What you’ll accomplish

Do not expect a staff button or controller route to call the model sync method. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

1. Go to the case or technical integration area described.
2. Verify the linked property and compatible module/table exist.
3. Use only exposed UI actions; treat model-only methods as unexposed capabilities.
4. Check any resulting record against the source property and document.

Fields and options to review

Rules the system enforces

• The supplied module contains the stated integration helper or hook.
• No user workflow should be invented where the controller/view does not call the model method.

How to confirm it worked

• Understand the unexposed compliance-sync limitation completes through the supplied module flow.
• Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.

Security, privacy and operational checks

• Use the least-privilege account that has the stated permission.
• Use a controlled test record before applying provider, financial, public-link, email or destructive actions in production.

Continue with related guidance