processing 50000+ entries

I would tend to agree that you probably don't want to do the ETL or validation rules directly in Appian processes, but context on data size, how often this is running, complexity of validation rules is going to be important when deciding on a final solution design.

How often is this validation process occurring? If this is a one time validation and approval process than you can probably get away with a less elegant solution. Are your databases all on-premise or are you utilizing the Appian Cloud MySQL database as well as other on-premise databases? Can stored procedures be utilized in the databases to run some or all of the validation rules prior to moving any data? Processing the data before it is moved between system will lighten the load.

I would try to get the data processed before doing any sort of transfer to minimize the amount of data that needs to be moved and subsequently processed within the transactional system. If you do need to process the data within the bounds of the transactional system, I would try to do it in stored procedures or Java. Hopefully that could be done off hours so you aren't consuming processor cycles or memory while users are actively working in the system. Once the data is processed you probably want to clean up data that won't be used and allow Appian to kickoff approval workflows for only the subset of data that requires an approval.

I would tend to agree that you probably don't want to do the ETL or validation rules directly in Appian processes, but context on data size, how often this is running, complexity of validation rules is going to be important when deciding on a final solution design.

How often is this validation process occurring? If this is a one time validation and approval process than you can probably get away with a less elegant solution. Are your databases all on-premise or are you utilizing the Appian Cloud MySQL database as well as other on-premise databases? Can stored procedures be utilized in the databases to run some or all of the validation rules prior to moving any data? Processing the data before it is moved between system will lighten the load.

I would try to get the data processed before doing any sort of transfer to minimize the amount of data that needs to be moved and subsequently processed within the transactional system. If you do need to process the data within the bounds of the transactional system, I would try to do it in stored procedures or Java. Hopefully that could be done off hours so you aren't consuming processor cycles or memory while users are actively working in the system. Once the data is processed you probably want to clean up data that won't be used and allow Appian to kickoff approval workflows for only the subset of data that requires an approval.

The process should run every day during the night. We have on premise databases. I am going to receive more Information soon but what I believe is that we dont want to load 50k objects in Memory to run some Validation that can be done with a stored procedure or a Java plugin.

Thanks for your answer.