Modified verifs needed dialogs

1. Changed name from "verifs requested" to "verifs needed" and "verifs
needed (LTC)". Easier to find when they match the script name.
2. Added due date and verif-req-form options on each dialog.

Will upload the scripts separately.
Added current date + 10 button

Because it's awesome.
Verifs needed facelift

Here's what we've got

1. It's just one script now. No more "verifs needed" and "verifs needed
(LTC)" buttons cluttering up the way. I moved the LTC dialog to the
regular script, and am using an if/then to decide where to go.
2. Added DHS-2919A and B checkboxes. Let's start case noting that, shall
we?
3. Added a "verifs due date" field. Because it's good to capture.
4. Added a current date + 10 button. This will fill in CD+10 in the
dialog. Because calendars are so 2013.
5. Modified several functions to match newer offerings in the FUNCTIONS
FILE.
6. Added better comments and tabbing. Code = pretty.
7. A success box at the end, for folks who TIKLed, so that they know the
case note actually happened.
Removed the LTC verifs needed script from the Power Pad

Moved some things around to look prettier.
Merge pull request #25 from theVKC/master

Verifs needed is better
Create Wiki-Images
Delete Wiki-Images

Thought I was creating a folder. Eeek!
Create usage.md
BZSE screenshot
Updated screenshot, circled wrong prog
changed name of file
Hello box
Hello there with variable
STAT to Word 1.1

Changes to the script have stopped it from creating duplicate reads of
panels, have got the dialogs to run properly, and have stopped the
script from getting stuck on WBSN
BILS Updater got some safeguardier

added a DO-LOOP to the BILS_updater_dialog.
Workers can still run the script if the case is stuck in background, but
they cannot get beyond that dialog unless isdate for budget_begin and
budget_end equals True
Merge pull request #27 from RobertKalb/master

Pulling Robert's changes over to master
BILS updater fixes galore

I built on Robert's safeguard, and added some of my own. :)

1. Added comments like crazy. This was an early script of mine, and my
management skills were lacking. I cleaned up some comments and made them
prettier.
2. Replaced several old "= 0" or "= 1" with cancel/checked global
variables. Makes it easier to visualize with what we're working.
3. Replaced several lines of code throughout with new FUNCTIONS FILE
functionality. Big one there would be the date filling issue, which came
from single digit months in budgets starting with a double digit.
Computer would declare as single digit, even when starting with double,
but if the user started with a double digit iteration of a single digit
month (user added their own 0), it'd work. create_MAXIS_friendly_date,
like the mighty honey badger, don't care 'bout this, and works better
here with less lines o'code. Tested it a dozen times, and it's working.
4. Building on Robert's do...loop, I added a check for users NOT filling
in the BILS ver dropdown. BILS requires it, and will freak out if it
isn't there. Now it is.
5. Got rid of those pesky "/////"s when you're using a case without a
budget. Just told the budget_begin and _end to replace a trimmed version
of itself, instead of the default.

Hopefully this solves the problem and I can go back to avoiding my BILS
(see what I did there?). :)
Merge pull request #28 from theVKC/master

BILS updater fixes galore
Merge pull request #29 from MN-Script-Team/master

Moving master changes into beta again