Skip to main content
H
harshav420
June 8, 2021
Question

Approach to save Data

  • June 8, 2021
  • 4 replies
  • 0 views

Hi All,

This is the screen which we are planning to build, and the user tries to enter the data on each and every subsection in the screen. However i wanted to understand which is the best approach to save the data.

Each tab in the left hand side will go into one table where these details if i am doing in process model, there might be more nodes. so i want to reduces the nodes and take the best approach. Could you please let me now which is the best approach.

    4 replies

    stefanhelzle0001
    stefanhelzle0001
    Brainy
    June 8, 2021

    Did you try this?

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

    H
    harshav420Author
    June 9, 2021

    Hi Stefan, [mention:126a676c85024855948336691b0a7b92:e9ed411860ed4f2ba0265705b8793d05]

    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.

    stefanhelzle0001
    stefanhelzle0001
    Brainy
    June 9, 2021

    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"

    Terms & ConditionsAccessibility statement