Customization Best Practices

Customization can be expensive, time consuming, and cause unforeseen bugs, deployment issues, and additional maintenance. We recommend the following best practices when customizing Sequence. The general rule is, the less customization, the better. You should use custom code as a last resort.

General Guidelines

  • Before you customize, check if you can achieve the same result  using Sequence's built-in tools. Oftentimes, you can achieve the same result with the built-in tools.
  • If you write custom code, follow the best practices for code writing (insert link to the article).


System Tables and Application Files

  • Do not edit system tables. Editing system tables can cause serious problems, including support, upgrades, functionality, among others.
  • Do not edit the application files. Editing application files can cause serious problems.


Configuration Files

  • Before editing configuration files make sure you:
    • Back up the files
    • Document the changes
    • Add comments where you make changes
  • Perform risk analysis to determine the affect these changes might cause.


Flowtime customization

You can customize Flowtime with pages that display multiple web parts and gauges. When you customize Flowtime, consider that future projects might use the same Sequence infrastructure. Therefore, it is good practice to maintain Flowtime's out-of-the-box configuration.

You must review gauges, reports, and statistics to ensure that the deployment displays the correct KPIs, which drive process optimization.

About this Article
  • Created: 03/07/2017 8:15 am EST
  • Last updated: 03/07/2017 1:35 pm EST
In This Article