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:
@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.
