Global Layouts
This is a reusable layout (for either Transaction Objects or Lookup Layouts) the admin creates once and can assign to multiple sync profiles. The key benefit is when the admin edits the global layout (field positions in Layout, or rule-only fields in Hidden), the changes propagate to every sync profiles using it. There is no rework per sync profile.
Transaction Object Layouts
When you edit a global layout (such as rearranging fields on the Details tab or add rule-only fields to Hidden), those changes propagate automatically to every sync profile using that layout. This eliminates repetitive edits and ensures consistency across teams.
Global layout take precedence: If a sync profile references a global layout, any updates to that global layout apply immediately.
Profile-specific layout overrides global: If you assign a custom layout to a profile, that layout takes precedence for that profile.
Best practice: Use global layouts for standardization and minimize profile-specific layouts to reduce maintenance overhead.
Lookup Layouts
Each sync profile has sections for Transaction Objects and Lookup Objects. For each object, you select which layout it will use—either:
-
a global layout (shared across profiles), or
-
a profile‑specific layout (unique to that profile, if you decide to diverge)
Once assigned, the Layout tab determines the fields and arrangement the mobile user will see; the Hidden tab carries non‑UI fields your rules, filters, and automations depend on. Both tabs are honored by the mobile app runtime.
The FieldFX Mobile App renders these lookup layouts directly, ensuring consistency between Back Office and Mobile.
Global vs Profile-specific
Global layout ➜ many profiles: Any edit to a global layout (on Layout or Hidden) is centralized and automatically reflected everywhere that layout is assigned. This is the fastest way to keep multiple teams aligned.
Profile‑specific layout: If a profile needs a different arrangement or set of hidden fields, you can create (or clone) a layout and assign that variant to just that profile. That profile then follows its assigned layout rather than the global one.
Assignment determines precedence. The layout assigned to the profile/object combination is the one the mobile user sees; a global layout only applies where it is assigned.
Best Practices: |
|