Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

DX API compliance guidelines

Updated on August 5, 2022

Ensure that your application is DX API-compliant, by learning about the appropriate design criteria.

Consider the following guidelines:

  • Harnesses must use a screen layout as the top container.
  • Ensure that you do not use circumstancing in harnesses and sections.
  • Visibility expressions must consist of When rule references only.
  • Sections should be auto-generated.
  • Sections should use one of the following layouts:
    • table
    • dynamic layout
    • repeating dynamic layout (not sourced from data pages)
    • embedded section
  • If a flow action uses editable pages (named pages, thread-level data pages or requestor-level data pages), edited values are not available in post-processing data transforms or activities. In such cases, use the pattern of auto-populated properties (which obtain data from data pages) and savable data pages in the post-processing of flow actions.
  • Ensure that you don't design your application for pessimistic locking. Your application's configuration is overridden to always use optimistic locking.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us