Approach to save Data

RE: Approach to save Data

harshav420 — Wed, 09 Jun 2021 06:06:29 GMT

No stefan, i will maintain it based on the interface level.

RE: Approach to save Data

Stefan Helzle — Wed, 09 Jun 2021 05:59:23 GMT

In my experience creating and maintaining separate interfaces for individual UX-cases is a huge benefit for your users. While I know that it is pretty simple to just switch readOnly, the way of how you create, view and modify data each has its own requirements. Especially with Appian which is about business processes and not just a Create-Read-Update-Delete UI on top of your DB. You typically have no use case like "Modify all data at free will"

RE: Approach to save Data

harshav420 — Wed, 09 Jun 2021 05:41:47 GMT

Hi Stefan,

Thanks for the input yes I did try, I have one more question, We have designed this as an Input where the user tries to submit the Forms, But after this i am planning to design the workflow, where i am planning to do create a DSE Records, Do you suggest to create the same look and feel or to change the View which adapts to Records. If i go in this approach the data will be all in a single page, Please suggest.

RE: Approach to save Data

Stefan Helzle — Tue, 08 Jun 2021 11:18:50 GMT

Did you try this?

docs.appian.com/.../Write_to_Multiple_Data_Store_Entities_Smart_Service.html