TechAppForce

Best practices

Habits that keep TechAppForce applications easy to change.

  • Build in Development, release forward. Change definitions in Development and move them to QA and Production with releases.
  • Filter platform tables by name, not id. Ids differ between tenants and environments. Saved queries should filter statuses by name.
  • Reuse platform entities. Use the platform's person, contact and location entities through lookups rather than adding copies of the same columns.
  • Check scripts before publishing. A validation hook that does not compile blocks every save on its entity.
  • Keep hooks small and fast. They run on every matching operation.
  • Grant the smallest scope that works. Start from None or Own and widen deliberately.
  • Treat custom code as your own code. Review it like any other code your team ships; it runs inside the platform's services.
  • Read back asynchronous writes. A 202 response means the write was accepted, not that it is visible yet.