Settings Saving Model for CT Mobile iOS
This article explains how the CT Mobile Control Panel 2.0 supports two settings object models—the old model (used for CT Mobile iOS versions prior to version 3.0) and the new model (introduced in version 3.0), and how administrators can switch between them, transfer settings in either direction, and decide which approach to use at different stages of a project.
When to Use Which Model
| Your situation | Recommended action |
|---|---|
If you are on 2.9 or earlier (not migrating) |
Continue using the old model, no transfer needed. |
If you are migrating to 3.0 (in progress) |
Remain on the old model during the transition and use Transfer Settings to New Model periodically. |
If you are on version 3.0+ (migration complete, or you work with this version from the beginning) |
Switch to the new settings model and use it as the primary configuration. |
Need to test older builds after migration |
Run Transfer Settings to Old Model to recreate old settings for the test cycle. |
| While backward compatibility is provided, some features may require a manual setup in the old model (e.g., Today’s agenda widget). Plan and validate accordingly. |
Switching to the New Settings Model
-
Click Switch Panel to New Settings Model.
-
In the switch dialog, optionally:
-
select the also transfer settings checkbox to migrate existing old settings into the new model during the switch;
-
leave this checkbox unselected to migrate existing old settings later by clicking Transfer Settings to New Model.
-
-
Confirm the action.
The CT Mobile Control Panel will write settings exclusively using the new model going forward.
| If you need to return the Control Panel to old model for any reason, please contact the Customertimes Support team. |
Before Migrating to 3.0
-
Before migrating to version 3.0, we highly recommend validating all existing records in Custom Settings.
-
In CTM Settings, the OrgProfileId field must contain either an Org ID or a Profile ID. Records where this field is empty will not be processed by the application.
To avoid issues during migration, you can do one of the following:-
Populate the required values in Custom Settings before transferring the settings; or
-
If you are confident in your data after the transfer, populate the field using Salesforce Inspector or Workbench.
-
Transferring Settings Between Models
These tools let you recreate settings in the other model for validation, testing, or migration support.
|
If you have any custom fields in Custom Settings the migration logic does not modify or handle those fields when transferring records from Custom Settings to CTM Settings and vice versa. As a result, when migrating settings:
|
A. Transfer Settings to New Model (Recommended during migration)
Fully recreates the current old settings into the new model (CTM Settings object). Use it if you are still operating in the old model (e.g., in the process of migration to 3.0) but want the new model to mirror the old configuration for verification.
-
Click Transfer Settings to New Model.
-
Confirm the action.
The CTM Settings are recreated to reflect current old settings.
B. Transfer Settings to Old Model (For testing older builds after migrating)
Recreates the old Custom Settings based on your current CTM Settings.
| It deletes existing old Custom Settings (if present) and creates new ones from CTM Settings. |
Use it if your project is fully on the new model (3.0+), but you need to test specific features on older builds that read old settings.
-
Click Transfer new to old.
-
Confirm the action and acknowledge the non‑upsert overwrite behavior.
FAQ
Do I need to switch to the new model when upgrading to 3.0?
The new model is optional but recommended for 3.0+ because all new development will target it. You may remain on old model with backward compatibility, but plan for potential manual configurations for some features.
Can I compare behaviors between models during migration?
Yes. Stay in old model and use Transfer Settings to New Model to mirror settings into the new model for side‑by‑side validation.
What happens if I click “Transfer Settings to Old Model”?
The system deletes existing old Custom Settings and recreates them based on CTM Settings. This is not an upsert/merge.
What happens if I click “Transfer Settings to New Model”?
The system fully recreates the current old settings into the new model. This is not an upsert/merge.
How do I roll back after switching to the new model?
Contact Support to revert the Control Panel to the old model.
We’re on 2.9 and not migrating. What should we do?
Continue using the old model. The transfer tools and switching are not needed.
How does settings selection work if the organization has both the old‑scheme settings and the new‑scheme settings at the same time?
-
For versions 2.9 and below, this does not affect anything. The settings selection works as before and is taken from Custom Settings.
-
For version 3.0+, the CTM Settings have priority. Only if they are missing will the system fall back to reading settings from Custom Settings.
See also: