toddgeist

// evaluate within data viewer - add any missing keywords

List(
        False & " False";
	Plain & " Plain";
	True & " True";
	Strikethrough & " Strikethrough";
	SmallCaps & " SmallCaps";
	Superscript & " Superscript";
	Subscript & " Subscript";

toddgeist

$firstName = "Todd" ;
$lastName= "Geist" ; 
$age = 6;
$birthDate = "5/13/2007" ;

toddgeist

"$firstName=" & Quote(contact::firstName) & ";¶" &
"$flastNameName=" & Quote(contact::lastName) & ";¶" &
"$age=" & contact::Age & ";¶" &
"$birthDate=" & Quote(contact::birthDate) & ";¶"

toddgeist

Let (
[
//     set "~parameters" to a Valid Let Variables String for ex. Get (ScriptParameter) or Get (ScriptResults)

        ~parameters =  $LetVariables;

//---------- NO NEED TO EDIT BELOW HERE -----------------

  ~evaluateString =
		"Let( [¶"

toddgeist

Keybase proof

I hereby claim:

• I am toddgeist on github.
• I am toddgeist (https://keybase.io/toddgeist) on keybase.
• I have a public key whose fingerprint is EC10 077F D8B9 9B77 73D1 473C 803D 60BE 4ACE CA12

To claim this, I am signing this object:

toddgeist

<link rel="import" href="../core-icon-button/core-icon-button.html">

<polymer-element name="my-element">

  <template>
    <style>    
      :host {
        position: absolute;
        width: 100%;
        height: 100%;

toddgeist

<link rel="import" href="../components/polymer/polymer.html">

<polymer-element name="my-element">

  <template>
    <style>    
      :host {
        position: absolute;
        width: 100%;
        height: 100%;

toddgeist

##Introduction
This document will specify the API that will be used to send Tax Returns from the FileMaker based 6n1 to the .NET application that is being built by Benchmark to do the actually eFileing with the Federal mEF system.

FileMaker has a reasonable HTTP client, although it is best to keep things as simple as possible.  Complex request types like multi-part forms are more difficult. Its best if we can keep to using only text or json formatted data. Raw binaries are tougher.

The intent is to use a REST like architecture. We may not need to support all of the VERBS for each resource.  There isn’t really a need to DELETE a firm for example.
Authentication
We’ll keep this simple and use Basic Auth.  There will only be two usernames and password pairs needed. One for “end user” access and one for “admin access”.  However, at this point there are no features that require “admin” access.  We should just keep that possibility open.

All of 6n1 users will use the same username and password.  They will never 

toddgeist

Verifying that +toddgeist is my openname (Bitcoin username). https://onename.io/toddgeist

toddgeist

/**
 * Created by toddgeist on 12/28/14.
 */

var faker = require('faker');
var stringify = require('csv-stringify');
var uuid =require('uuid');
var moment = require('moment');
var fs = require('fs');
var Readable = require('stream').Readable;