Using separate subprocesses called from a master process allows each department’s work to be encapsulated and executed sequentially as required. The master process provides the overall structure and coordination, enabling clear reporting on the entire onboarding workflow’s status while maintaining the necessary dependencies between stages.

Using a!queryEntity() within a rule input (creating a query rule) is the recommended best practice. It separates data retrieval logic from the interface, promotes reusability, and allows for efficient caching. Calling this rule from the interface’s data parameter ensures the query executes with the proper security context and filters can be passed as parameters to the rule.

Process model-level timeout settings in Advanced Settings override the application default. This allows you to set a longer duration (e.g., 60 days) specifically for the ‘Order Approval’ model without affecting other processes in the application, providing a targeted solution for the unique needs of this workflow.

For complex but stable business logic, a decision rule is ideal. It uses a literal map to explicitly pair conditions with outcomes, making the logic far more readable and maintainable than deeply nested if() statements. It clearly separates the condition definitions from the return values, which is perfect for rules like discount calculations.

The a!richTextDisplayField() component is specifically designed to safely render HTML content stored as text. It will correctly display the formatted text (bold, italics, lists, etc.) that was created in the a!richTextEditorField(), unlike standard text fields which will show the raw HTML source.

Replacing script tasks with Appian-native logic (like expression rules) is a key modernization practice. It eliminates external dependencies, leverages Appian’s security and auditing, and makes the logic transparent, debuggable, and reusable. The node expression can call the new expression rule, passing the necessary inputs from the process.

This hybrid approach is optimal. A CDT holds Appian-owned data (status, assignee, notes). For real-time financial data from the ERP, a!queryEntity() with a data sync is used. This ensures users always see the latest financials without the latency of batch syncs, avoids data duplication issues, and keeps Appian as the system of record for its own workflow data.

‘Assigned by Expression’ provides the necessary flexibility. The expression rule can encapsulate the complex business logic: first, check if a specific lawyer is named in the contract (using rule inputs from the process). If not, it can query active lawyers in the ‘Legal’ group, apply the ‘most junior’ logic (e.g., by hire date), and return the appropriate user. This is dynamic and automated.

Appian’s data security model allows for permission-specific filters. You can grant the ‘Regional Managers’ group ‘Viewer’ permission on the CDT with a filter like ‘region = loggedInUser.region’. Separately, grant them ‘Editor’ permission with a stricter filter: ‘region = loggedInUser.region AND createdBy = loggedInUser()’. This ensures they see all regional records but can only edit their own, enforced at the database level.

Using separate subprocesses called from a master process allows each department’s work to be encapsulated and executed sequentially as required. The master process provides the overall structure and coordination, enabling clear reporting on the entire onboarding workflow’s status while maintaining the necessary dependencies between stages.0