Flows or Lightning Components - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
Neelima ThotaNeelima Thota 

Flows or Lightning Components

I am trying to build out a wizard to capture information from the user. What is a better approach - use flows or lightning components? The little reading I have been doing says it is possible to use lightning components to acheive this as well.

Would love to hear some thoughts?
Best Answer chosen by Neelima Thota
Deepak AnandDeepak Anand
Well, the answer really depends on a couple of factors:
  1. Using the Lightning Components
    • If you have access to the Lightning App Builder, then I am not sure but I guess it could speed up the process of creating it using the available out of the box Lightning Components. But the caveat is that I haven't got a chance to test that out and neither am I sure if you really have components that makes a Wizard kinda of UI possible!
    • But the major advantage is that it makes the UI responsive and makes it capable enough to adapt to any  screen resolution thus opening up smooth access over gadgets!
    • And more over requests back and forth from the Server has all become asynchronous which even makes it more usable and user friendly.
  2. Using the Visual Workflows
    • This is when you want it to be done pretty easily and switfly - Rapid Development with no code and just clicks!
    • But the disadvantages are:
      • The UI isn't responsive meaning it only looks good when you're using it on Desktop or Laptop not when you're viewing it from a Mobile Device running a Salesforce 1 App.
      • Each Next/Previous clicks has postbacks back to the Server. This isn't a major issue but just pointing it out.
      • Lack of options to customize the User Interface.
    • But one major advantage is the ability to Pause Flows which is coming this Spring'15. This is reallly awesome. This can be definitely acheived even using the former method but that would require code and so comes effort!
    • And of-course, last but not the least, the canvas with all it's powerful newly added elements like Collections[Primitive, SObject], SObject Variables, Wait and the Fast Elements makes development incredibily fast!

All Answers

Deepak AnandDeepak Anand
Well, the answer really depends on a couple of factors:
  1. Using the Lightning Components
    • If you have access to the Lightning App Builder, then I am not sure but I guess it could speed up the process of creating it using the available out of the box Lightning Components. But the caveat is that I haven't got a chance to test that out and neither am I sure if you really have components that makes a Wizard kinda of UI possible!
    • But the major advantage is that it makes the UI responsive and makes it capable enough to adapt to any  screen resolution thus opening up smooth access over gadgets!
    • And more over requests back and forth from the Server has all become asynchronous which even makes it more usable and user friendly.
  2. Using the Visual Workflows
    • This is when you want it to be done pretty easily and switfly - Rapid Development with no code and just clicks!
    • But the disadvantages are:
      • The UI isn't responsive meaning it only looks good when you're using it on Desktop or Laptop not when you're viewing it from a Mobile Device running a Salesforce 1 App.
      • Each Next/Previous clicks has postbacks back to the Server. This isn't a major issue but just pointing it out.
      • Lack of options to customize the User Interface.
    • But one major advantage is the ability to Pause Flows which is coming this Spring'15. This is reallly awesome. This can be definitely acheived even using the former method but that would require code and so comes effort!
    • And of-course, last but not the least, the canvas with all it's powerful newly added elements like Collections[Primitive, SObject], SObject Variables, Wait and the Fast Elements makes development incredibily fast!
This was selected as the best answer
Neelima ThotaNeelima Thota
Those are some very good points, Deepak. Thank you!