In addition to the best practices listed here, you should also follow all platform best practices as you develop your solutions. Learn more in Nextworld Platform best practices.

Naming conventions

  • When you create or extend applications and application pages, do not use your solution brand name. Name applications and pages based on their function.

Data items

  • Synonyms can't be extended. If you need to add custom synonyms, or if any of the formatting options are different, create your own data items.
  • Reuse common list lookups, such as unit of measure, so that customers do not have to configure the same values twice. You can still create a new data item, but you should configure against an existing list lookup when possible.

Tables

  • Do not insert, update, or delete data into Nextworld tables, with the exception of Directory.
  • Do not insert, update, or delete data in a table that is in a different family. Instead, call a logic block from that family. For any fetch to a Nextworld table, check with partner development support to see if there is a logic block you should call. 

Module Settings

  • Do not fetch a module settings table directly. Use the Retrieve Module Setting action. 

List Lookups

  • Do not hard-code against any Nextworld list lookup that is marked as Complete Unlock.

Extensions and Customizations

  • Do not customize objects as this configuration type is reserved for customers only, and customizations will not migrate to production. To add fields and logic to Nextworld objects, use extensions.

Security Groups

  • All flat report tables must be in the FlatReportData security group.
  • Test your security groups early. You can easily turn roles on and off by clicking on the roles dropdown in the top navigation bar.

Directory

  • Do not hard-code against a specific contact role. This list lookup is a complete unlock and customers manage their own values. Instead, use the ContactRoleGrouping field to code in a logic block. If you need a specific contact role grouping, extend the lookup to add your own value.
  • If you create your own directory application, add the ValidateContactRole logic block to the Before Save event.
  • Set any organizational unit data item to have the primary typeahead as NumericCode, and the secondary type ahead as Name.
  • For any table with a data item that represents the organizational unit, add the Company data item to the table and set the Filtered Table Lookup on the table. Specifically, any transactional table must include the Company field. The exception is module setting tables. For these tables, use the tertiary typeahead to display the Company field.