Having views in DB vs Data manipulation in Expression rules - What approach is best in terms of Performance?

Certified Lead Developer
Consider simple scenario: I have joining date of an employee in DB, want to find out experience. We can achieve in two ways : 1. Writing a view with DB specific functions to find the date difference 2. Manipulating in Expression rules using Appian functions.
Which approach is best practice/improves performance? and strictly speaking When to go for DB views?
Any suggestions?..

OriginalPostID-241280

  Discussion posts and replies are publicly visible

Parents
  • As per my understanding, If any business rule which required user interaction for evaluation and use other constants/rules value for evaluation then use expressions. However, bussines logic is kind of permanent rule, need data from other tables for manipulation or involve complex evaluation to convert user data into useful information use DB store procedure. DB views are only required when you want to display data from many table in single place form or appian.
Reply
  • As per my understanding, If any business rule which required user interaction for evaluation and use other constants/rules value for evaluation then use expressions. However, bussines logic is kind of permanent rule, need data from other tables for manipulation or involve complex evaluation to convert user data into useful information use DB store procedure. DB views are only required when you want to display data from many table in single place form or appian.
Children
No Data