My use case is an attempt to use what I have already built and make it east on myself to not have to rework my dashboards (I appreciate you documenting how to use elements) in order to update the dashboard after user driven action from an input block and virtual button press.
I know you have voiced concerns and that there are other ways to accomplish this but I am running short on time to initial deployment, I have already spent three months getting to this point and I am at the limit of the things that I can ask my user to do to get started.
I really don’t want to create additional pages to handle user input but would like my users to do 90% of their work from a dashboard. My users already have enough to do just to get started monitoring their machines:
- Create an Account
- Verify Email
- Claim a Gateway
- Scan for Sensors on Said Gateway
- Create a Machine
- Assign Sensors to that Machine
- Setup Sensor Orientation
- Setup Sensor Alarm Limits
My goal was to pass the information about the experience user that is logged in along with their submission of the input block and within the workflow to use the http node to trigger a GET request to the same page with dashboard that they are on by using the already available client authorization token to do this within the workflow of the virtual button.
If I add any more setup headache or redirection to different setup pages then I fear my users will fall into the “unneccessary complex setup” camp and our offering will not be successful due to too much setup overhead.
I just wanted to make a note that I do appreciate all the help that you guys have provided in the documentation and the forum and my frustration comes from my current level of understanding and competence on the different areas required to use your platform. It is a very nice offering and I have 90% of what I need to impress my customers. Thanks for all your answers and time spent getting your less technically savvy customers up to speed.