If this then that
-
@DustinB3403 said in If this then that:
@IRJ said in If this then that:
That could work, but I was looking for something a little cleaner with drop down boxes that generate different paths based on reply.
For example, this...
https://vsaq-demo.withgoogle.com/vsaq.html?qpath=questionnaires/webapp.json
Not you are purposefully making it "more difficult".
Just draw arrows for each of the cases. If they can't read an arrow and the process within then they are screwed anyways.
There is a big difference in fact, since a chart cannot be easily used to with repeat documentation. VSAQ for example saves a file with all the selections made. That functionality would be ideal, but even if I could get a blank template that this person could fill out each time, it would provide a big advantage over a simple chart.
-
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
@IRJ said in If this then that:
That could work, but I was looking for something a little cleaner with drop down boxes that generate different paths based on reply.
For example, this...
https://vsaq-demo.withgoogle.com/vsaq.html?qpath=questionnaires/webapp.json
Not you are purposefully making it "more difficult".
Just draw arrows for each of the cases. If they can't read an arrow and the process within then they are screwed anyways.
There is a big difference in fact, since a chart cannot be easily used to with repeat documentation. VSAQ for example saves a file with all the selections made. That functionality would be ideal, but even if I could get a blank template that this person could fill out each time, it would provide a big advantage over a simple chart.
You still have to enter all the information, so how much time would that save if it actually existed?
-
It's kind of the entire purpose of having essentially a checklist that is included repeatedly with documentation. For example when doing server builds, it routinely accepted to have a checklist that is filled out each time and saved with the server build process.
Giving techs a build document one time, and just telling them to make sure they do all that stuff every time is no where near as good as having a checklist IMO.
-
@travisdh1 said in If this then that:
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
@IRJ said in If this then that:
That could work, but I was looking for something a little cleaner with drop down boxes that generate different paths based on reply.
For example, this...
https://vsaq-demo.withgoogle.com/vsaq.html?qpath=questionnaires/webapp.json
Not you are purposefully making it "more difficult".
Just draw arrows for each of the cases. If they can't read an arrow and the process within then they are screwed anyways.
There is a big difference in fact, since a chart cannot be easily used to with repeat documentation. VSAQ for example saves a file with all the selections made. That functionality would be ideal, but even if I could get a blank template that this person could fill out each time, it would provide a big advantage over a simple chart.
You still have to enter all the information, so how much time would that save if it actually existed?
Well the nested answers drastically change the document. There could be as few as 2 questions and as many 22 questions. So it would save a ton of time because there are so many different variable routes.
-
How is having a "selection box" better than a diagram like listed?
Also the purpose seems to be evolving from what was described originally.
-
@DustinB3403 said in If this then that:
Also the purpose seems to be evolving from what was described originally.
Are you new in IT
-
@IRJ said in If this then that:
@travisdh1 said in If this then that:
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
@IRJ said in If this then that:
That could work, but I was looking for something a little cleaner with drop down boxes that generate different paths based on reply.
For example, this...
https://vsaq-demo.withgoogle.com/vsaq.html?qpath=questionnaires/webapp.json
Not you are purposefully making it "more difficult".
Just draw arrows for each of the cases. If they can't read an arrow and the process within then they are screwed anyways.
There is a big difference in fact, since a chart cannot be easily used to with repeat documentation. VSAQ for example saves a file with all the selections made. That functionality would be ideal, but even if I could get a blank template that this person could fill out each time, it would provide a big advantage over a simple chart.
You still have to enter all the information, so how much time would that save if it actually existed?
Well the nested answers drastically change the document. There could be as few as 2 questions and as many 22 questions. So it would save a ton of time because there are so many different variable routes.
All of that could still be put into a diagram. . .
Installing Exchange > Yes > 2016 > No > 2019 > Yes > Some process of steps
-
@DustinB3403 said in If this then that:
How is having a "selection box" better than a diagram like listed?
Because it can be used to create a file that is attached with each instance.
-
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
How is having a "selection box" better than a diagram like listed?
Because it can be used to create a file that is attached with each instance.
I guess, but you're hoping that this person who can't read and follow a diagram will be able or willing to select the correct answer and do the correct process as outlined.
When the solution you linked actually doesn't list any process to go through. But instead just asks a question with a list of possible answers.
-
@DustinB3403 said in If this then that:
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
How is having a "selection box" better than a diagram like listed?
Because it can be used to create a file that is attached with each instance.
I guess, but you're hoping that this person who can't read and follow a diagram will be able or willing to select the correct answer and do the correct process as outlined.
When the solution you linked actually doesn't list any process to go through. But instead just asks a question with a list of possible answers.
It was an example of a nested solution that creates an exportable file that can be saved with parameters and easy to pull up in the future if needed. It isnt an exact fit for what I want, It was an example.
-
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
How is having a "selection box" better than a diagram like listed?
Because it can be used to create a file that is attached with each instance.
I guess, but you're hoping that this person who can't read and follow a diagram will be able or willing to select the correct answer and do the correct process as outlined.
When the solution you linked actually doesn't list any process to go through. But instead just asks a question with a list of possible answers.
It was an example of a nested solution that creates an exportable file that can be saved with parameters and easy to pull up in the future if needed. It isnt an exact fit for what I want, It was an example.
A diagram as I provided is literally the same thing.
Have an initials box next to each step in the process if you are looking for a means of verification that the job was completed.
-
@IRJ said in If this then that:
@travisdh1 said in If this then that:
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
@IRJ said in If this then that:
That could work, but I was looking for something a little cleaner with drop down boxes that generate different paths based on reply.
For example, this...
https://vsaq-demo.withgoogle.com/vsaq.html?qpath=questionnaires/webapp.json
Not you are purposefully making it "more difficult".
Just draw arrows for each of the cases. If they can't read an arrow and the process within then they are screwed anyways.
There is a big difference in fact, since a chart cannot be easily used to with repeat documentation. VSAQ for example saves a file with all the selections made. That functionality would be ideal, but even if I could get a blank template that this person could fill out each time, it would provide a big advantage over a simple chart.
You still have to enter all the information, so how much time would that save if it actually existed?
Well the nested answers drastically change the document. There could be as few as 2 questions and as many 22 questions. So it would save a ton of time because there are so many different variable routes.
How much programming do you want to do?
What you want to accomplish, the only way I know to do it, is build a full application stack with a database backend that dynamically updates contents on a page. Sounds a lot like a modern web app.
There is a reason why documentation is hard for people, because you quickly get into this exact problem.
-
@travisdh1 said in If this then that:
@IRJ said in If this then that:
@travisdh1 said in If this then that:
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
@IRJ said in If this then that:
That could work, but I was looking for something a little cleaner with drop down boxes that generate different paths based on reply.
For example, this...
https://vsaq-demo.withgoogle.com/vsaq.html?qpath=questionnaires/webapp.json
Not you are purposefully making it "more difficult".
Just draw arrows for each of the cases. If they can't read an arrow and the process within then they are screwed anyways.
There is a big difference in fact, since a chart cannot be easily used to with repeat documentation. VSAQ for example saves a file with all the selections made. That functionality would be ideal, but even if I could get a blank template that this person could fill out each time, it would provide a big advantage over a simple chart.
You still have to enter all the information, so how much time would that save if it actually existed?
Well the nested answers drastically change the document. There could be as few as 2 questions and as many 22 questions. So it would save a ton of time because there are so many different variable routes.
How much programming do you want to do?
What you want to accomplish, the only way I know to do it, is build a full application stack with a database backend that dynamically updates contents on a page. Sounds a lot like a modern web app.
There is a reason why documentation is hard for people, because you quickly get into this exact problem.
That VSAQ tool is open source, I may mess with it again when I have time. I spun it up a year or so ago and played with it a bit.
-
-
@DustinB3403 said in If this then that:
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
@IRJ said in If this then that:
@DustinB3403 said in If this then that:
Have an initials box next to each step in the process if you are looking for a means of verification that the job was completed.
That kind of file isn't as helpful because it is not searchable as easily when you are doing things in a very large scale. There will be hundreds or thousands of these saved eventually.
Yeah my wants are evolving
-
@IRJ said in If this then that:
Yeah my wants are evolving
Good luck keeping it within a reasonable scope!
-
@travisdh1 said in If this then that:
@IRJ said in If this then that:
Yeah my wants are evolving
Good luck keeping it within a reasonable scope!
Yeah, that really is the issue here. We are documenting all software used in the org. Which happens to be in thousands. Security assessments were not done on everything. Sure cloud based stuff and major applications went through the hoops, but I am talking about onesies and twosies of software here and there. That alone accounts for thousands of software. We are trying to consolidate and re-assess everything.
Since there will be thousands done, it may be worth the time to do this right.
-
This is more on the compliance side which is another reason drop down boxes will be nice.
-
@IRJ said in If this then that:
This is more on the compliance side which is another reason drop down boxes will be nice.
Take a look at LibreOffice Base. It can use a real database as a backend, unlike that low-end junk from Microsoft. If I remember correctly, it supports NoSQL as well.
-
You might be able to use a BPM software to accomplish this. Sounds like you just want a runbook.
