RelashionShips in Appian do not reflect FOREIGN KEY definitions in a database

My perspective on this is, that the database is only a integrated system like any other. Appian at its core does not need a relational database and the platform tries to limit dependencies on these integrated systems.

I am building enterprise Appian applications for > 12 years now and try to keep the relational DB as dumb as possible. And I never had the urge to do more than a simple view or a stored procedure for ETL jobs.

Low-Code with Appian gives you the opportunity to make the whole development a lot easier. Give it a try.

This is just my humble opinion and there are other perspectives on this.

My perspective on this is, that the database is only a integrated system like any other. Appian at its core does not need a relational database and the platform tries to limit dependencies on these integrated systems.

I am building enterprise Appian applications for > 12 years now and try to keep the relational DB as dumb as possible. And I never had the urge to do more than a simple view or a stored procedure for ETL jobs.

Low-Code with Appian gives you the opportunity to make the whole development a lot easier. Give it a try.

This is just my humble opinion and there are other perspectives on this.