ISoft Wiki - User contributions [en]

User:Duff

2016-09-01T15:01:43Z

Duff: Updating employer

Josh Duff was an [[ISoft]] employee.

== Work at ISoft ==
Josh was hired part-time on 2005-09-20, referred by fraternity brother [[Dillon Sadofsky]]. His starting job description was supporting [[ITrack Pro]] by answering customer calls, and maintaining reports.

He became a full-time employee on 2006-12-23.

During his first few years at ISoft, he began transitioning from phone support to software development. He spent much of his time at ISoft as the primary developer for ITrack Pro, while also writing code for [[ITrack Enterprise]] as well as many other smaller projects.

In his later years, he took on more [[web development]], writing [[ITrack/Enterprise/LXW|ITrack LXW]] and other mobile apps.

He left ISoft on 2013-03-01 to work for [http://www.emaildatasource.com/ eDataSource].

He left eDataSource on 2016-08-12 to work for [https://cake.co/ Cake].

== Contact ==
Josh can be contacted by members of the [[ISoft chat]] server at JoshDuff@im.isoftdata.com.

== Other presence on the internet ==
Josh maintains a [http://joshduff.com home page] with sporadic posts, mostly of a libertarian or geeky nature.

Known Ebay Problems

2013-09-18T19:39:46Z

Duff: Misspelling, formatting

This wiki is for fixes to common (but show stopping) problems with our ebay extension and TurboLister

==TurboLister HTML Problems==
===Not Displaying Correctly===
====Cause====
Sometimes HTML won't display correctly if it has certain Javascript or CSS elements.

====Resolution====
One fix for this is to make sure TurboLister is up to date and make sure that you are using Turbo Lister 2. If a Description is still not displaying correctly try taking the Description and putting it into an html document and opening it in your browser.

====Similar Problems====
Problem is HTML or JavaScript related.

===Template===
====Cause====
Sometimes users will have additional templates in turbolister to help with things like return policy and shipping details but this can also cause problems with the price, auction format, title, and description being changed.

====Resolution====
The fix is to delete or change the TurboLister template.

====Similar Problems====
ITrack ebay Template is wrong or wrong ITrack ebay Template is being used

==Image Problems==
Before anything make sure all links look like: "http://www.cyclerecyclers.net/image.php?productcode={?ProductCode}&inventoryid={?PartNum}&imageid={X}" and X is replaced by a number that is greater than 0

===Preview Image not Showing up===
====Cause====
This means that they don't have images in their ITrack image directory which can be found under "imagesdir" in the Host.ini

====Resolution====
Change the directory where ITrack looks for and saves images

===No Images Show up===
====Cause====
This usually means that images aren't sync'd so it assumes there are no pictures associated with the part trying to be listed on HTP/Recyclers/Cyclerecyclers

====Resolution====
Re-sync their images and make sure Replikwando is working

==Steps for Debugging TurboLister Problems==
# Check the CSV Created by ITrack before it is imported into TurboLister and make sure all values are correct and present
# Check to see if TurboLister is Throwing any Errors
# Check Listing in TurboLister to make sure all values are correct and present
# Make sure a TurboLister Template isn't interfering with Values sent from ITrack
# (If Description Related) Copy out description into an HTML document and open it in a Web Browser to see if it displays correctly
# Get TurboLister User File, Information, Settings, and Templates to test independently

ISoft Data Systems

2013-08-12T18:49:47Z

Duff: /* Application Development */ I am no longer available at this extension

ISoft Data Systems is a software development company in Lincoln, Nebraska. They specialize in custom web development and business management solutions for the recycling and salvage industries.

[[Image:Turbine Flats from south side small.jpg|frame|ISoft Data Systems is located in the Turbine Flats Building.]]

== Address ==
2124 Y Street Flat 201 <br>
Lincoln, NE 68503

==Chat==
(8am - ~7pm [http://en.wikipedia.org/wiki/Central_Time_Zone_(North_America) Central]) Call or email us and we will help you set up a chat account so you can easily contact us whenever you like!

==Email==
* ITrack Support: [mailto:support@isoftdata.com?Subject=ITrack%20Support%20Question support@isoftdata.com]
* HeavyTruckParts.net Support: [mailto:support@heavytruckparts.net?Subject=Heavy%20Truck%20Parts%20Support%20Question support@heavytruckparts.net]

==Phone Numbers==
* Toll free phone: 800-929-1829 (8am - 6pm Central)
* Nebraska phone: 402-435-3850 (8am - 6pm Central)
* Fax: 402-435-7076

==Departments==
Those numbers there are our extension numbers!

===Tech Support===
* '''201 - All Support'''
** 110 - [[Cody Hanson]]
** 107 - [[Justin Wheeler]]
** 108 - [[Mark Hardisty]]
** 118 - [[Jordan Bonge]]

=== Management ===
* 106 - [[Brendan Evans]] (Sales)
* 103 - [[Dan Syde]] (Sales)
* 100 - [[Emily Lowell]]
* 101 - [[Matthew Wegener]]
** 301 - Voicemail
* 111 - [[Tony Merritt]]
* 203 - [[Umeda Islamova]]

=== Application Development ===
* 105 - [[Dillon Sadofsky]]
* 115 - [[Justin McKinstry]]
* 102 - [[Dayton Lowell]]

=== Web Development ===
* '''202 - All web development'''
** 114 - [[Amos Sterns]]
** 112 - [[Andrew Johnson]]
** 113 - [[Brian Roy]]

== See also ==
[[:Category:ISoft Employees|ISoft Employees]]

User:Duff

2013-05-17T01:37:32Z

Duff: rm :Category:ISoft Employees

Josh Duff was an [[ISoft]] employee.

== Education ==
Josh was homeschooled by his parents until 2003. At that time, he moved to Lincoln to pursue a business degree (and computer science minor) with a full scholarship at UNL.

After 6 semesters at the university, he stopped taking classes, due to disenfranchisement with university-style education, and failing to complete the necessary credit hours to maintain his scholarship.

== Work at ISoft ==
Josh was hired part-time on 2005-09-20, referred by fraternity brother [[Dillon Sadofsky]]. His starting job description was supporting [[ITrack Pro]] by answering customer calls, and maintaining reports.

He became a full-time employee on 2006-12-23.

During his first few years at ISoft, he began transitioning from phone support to software development. He spent much of his time at ISoft as the primary developer for ITrack Pro, while also writing code for [[ITrack Enterprise]] as well as many other smaller projects.

In his later years, he took on more [[web development]], writing [[ITrack/Enterprise/LXW|ITrack LXW]] and other mobile apps.

He left ISoft on 2013-03-01 to work for [http://www.emaildatasource.com/ eDataSource].

== Contact ==
Josh can be contacted by members of the [[ISoft chat]] server at JoshDuff@im.isoftdata.com.

== Other presence on the internet ==
Josh maintains a [http://joshduff.com home page] with sporadic posts, mostly of a libertarian or geeky nature.

User:Duff

2013-03-06T00:47:29Z

Duff: *cough*

Installing LXW

2013-03-01T17:09:43Z

Duff: /* Configure config.json */ Removing unnecessary data

The new version of ITrack LX, colloquially known as LXW, is the faster and sexier version of ITrack designed to run in the browser, primarily on handheld scanner devices.

== Dependencies ==
Besides the regular version of [[MySQL]] used by ITrack Enterprise, LXW requires:
* [http://httpd.apache.org/download.cgi Apache] 2.2 or higher
* [http://php.net/downloads.php PHP] 5.3 or higher
* [http://nodejs.org/download/ Node.js] 0.8 or higher
* [http://subversion.apache.org/ SVN] 1.6 or higher

== Installing the server-side code ==
This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.

The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release].

To configure the database connection, edit /lxw/configs/database.php.

== Installing the client-side code ==
This is the code that is accessible via HTTP! Check it out to your Apache htdocs folder, or whatever other folder will get it served up to the tubes.

The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client].

To configure the connection to the server-side code: edit line 15 of server/index.php to point it at the path where you checked out the server-side code.

To configure client application settings (which should all have reasonable defaults), you can edit the config.js file in the client path.

== Setting Up the Auto-Updater ==
This is the process that will download updates for LXW and then install them.

[https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/ https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/]

#Transfer contents of this directory to the server hosting LXW. The standard directory for Linux based servers is /var/www/lxw/updater (This directory will not exist yet.)
#Configure config.json
#Run the .sh files
##install.sh
##run.sh
#Add updater to crontab

===Configure config.json ===
An example of a config.json

<code lang="json">

{
"update_url": "autoupdate URL here",
"product_code": "valid product code here",
"download_directory": "/var/www/lxw-release/updater/downloaded-all",
"destination_directories": {
"default": "/var/www/lxw-release/updater/downloaded-latest",
},
"extraction_directories": {
"LXW-client.zip": "/var/www/html/lxw",
"LXW-server.zip": "/var/www/lxw-release"
}
}
</code>

After the updater is run properly then a new section will appear below this section and it will look like this.

<code>

"versions": {
"LXW-client.zip": "#####",
"LXW-server.zip": "#####"
}

</code>

===Run .sh Files===
Unfortunately as of February 25th 2013 you are unable to run the .sh files as they will be unable to find the config file. Instead you can run the contents of the files without any problem. Here is an example of each file as you would use it for LKQ.

'''install.sh'''
<code>
sudo npm install isoft-updater -g
</code>

'''run.sh'''
<code>
node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
</code>

===Add Updater to Crontab===
The last bit to setting up the auto updater is the "auto" part. Here is how to access and edit the crontab.

<code>
crontab -e
</code>

This is what LKQ's crontab looks like for the autoupdater.
<code>
12 21 * * * node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
</code>

This is the format that crontab uses.

<code>
* * * * * command to be executed
- - - - -
| | | | |
| | | | +----- day of week (0 - 6) (Sunday=0)
| | | +------- month (1 - 12)
| | +--------- day of month (1 - 31)
| +----------- hour (0 - 23)
+------------- min (0 - 59)
</code>

====Note====
Removing the version section in config.json will cause it to redownload the latest update during the next scheduled update cycle or forced update. Can be used to test the process.

== Testing ==
Browsing to the [the URL you would expect to correspond to the client-side files you installed]/server/index.php should show you a snide remark embedded in JSON.

Browsing to the regular URL should show you a screen asking you to identify your store number (assuming that your web server is configured to serve up index.html files when you browse to a directory).

ITrack/Enterprise/LXW

2013-03-01T17:02:20Z

Duff: Adding section for Fast Inventory Move

The mobile version of ITrack, for running warehouses with scanners!

== Picking ==
# Scan a sales order barcode (on a picking label)
# Scan a part
# Scan the source location where you found the part
## If the location is not one of the locations where the part was currently allocated from, you will need to select the allocation location that you are picking the part for
# Scan a destination location (if you want to, otherwise you can close the screen or scan a new sales order)

The part gets marked as picked in the delivery system, and gets moved to the destination location. If you don't specify a destination location, it uses the default, which is set in the store settings.

== Inventory move ==
# Scan a location
# Scan any number of parts at the location
# Scan a destination location

All the parts you scanned get moved!

== Inventory Detail ==
Scan any part to see information about it!

== Inventory Count ==
# Scan a location
# Scan all the parts at that location
# Scan a new location to count at, or close the screen

All of the parts that you found at that location are moved there, if necessary. All parts that should have been found there, but weren't, get moved to the Variance location!

== Fast Inventory Move ==
# Scan any number of parts
# Scan a location to move those parts to

Scanned inventory records will be moved if:
* All quantity for a scanned inventory record are located at the same location
OR
* All quantity for a scanned inventory record has been scanned to move
Otherwise, none of the quantity for part will be moved.

The screen will show whether or not the part will be moved by coloring the line green, and warn you that a move will not happen by coloring the line red.

User:Duff

2013-03-01T16:59:10Z

Duff: It's been fun

Josh Duff was an [[ISoft]] employee.

== Education ==
Josh was homeschooled by his parents until 2003. At that time, he moved to Lincoln to pursue a business degree (and computer science minor) with a full scholarship at UNL.

After 6 semesters at the university, he stopped taking classes, due to disenfranchisement with university-style education, and failing to complete the necessary credit hours to maintain his scholarship.

== Work at ISoft ==
Josh was hired part-time on 2005-09-20, referred by fraternity brother [[Dillon Sadofsky]]. His starting job description was supporting [[ITrack Pro]] by answering customer calls, and maintaining reports.

He became a full-time employee on 2006-12-23.

During his first few years at ISoft, he began transitioning from phone support to software development. He spent much of his time at ISoft as the primary developer for ITrack Pro, while also writing code for [[ITrack Enterprise]] as well as many other smaller projects.

In has later years, he took on more [[web development]], writing [[ITrack/Enterprise/LXW|ITrack LXW]] and other mobile apps.

He left ISoft on 2013-03-01 to work for [http://www.emaildatasource.com/ eDataSource].

== Contact ==
Josh can be contacted by members of the [[ISoft chat]] server at JoshDuff@im.isoftdata.com.

== Other presence on the internet ==
Josh maintains a [http://joshduff.com home page] with sporadic posts, mostly of a libertarian or geeky nature.

[[Category:ISoft Employees]]

Web development/model-router

2013-02-20T20:36:51Z

Duff: Adding a note about method-specific routing

model-router does a few things that make writing data servers easier:
* Routing
* Session handling/state
* Wrapping up authentication
* Checking for parameters existence

== Including ==
You could have multiple router-things if you wanted to - you know, in case you were running multiple sites from the same node.js server, or something - but for your purposes you'll probably just want to instantiate one.

<source lang="javascript">
var Router = require('model-router')
var router = new Router()
</source>

It doesn't launch any servers of its own, that would be rude. You'll want to create your own server in the usual way, and then tell model-router to handle it if appropriate.

model-router only sends back JSON responses, and doesn't do anything with static content out of the box, so if you want to serve HTML/JavaScript files or something, you'll have to do it yourself:

<source lang="javascript">
require('http').createServer(function(req, res) {
var pathname = require('url').parse(req.url).pathname
var match
if (match = /^\/static(\/.*)$/.exec(pathname)) {
require('send')(req, match[1]).root('./static/').pipe(res)
} else {
router.handleRequest(req, res)
}
}).listen(8080)
</source>

== Routing ==
All right, your server is running. You want to add a new response to certain messages - so that requests to yourdomain.com/information/time would get the current server time back, or something dumb like that.

<source lang="javascript">
router.route('/information/time', function(parameters, session, next) {
next(new Date())
})
</source>

Browsing to the URL should immediately get you back this response:
<pre>{"success":true,"output":"2013-02-19T22:00:56.507Z"}</pre>
But let's say that something bad happens on the server - maybe it's an error if a client asks for the server time on a Sunday. You could reflect that by rewriting the function like so:
<source lang="javascript">
router.route('/information/time', function(parameters, session, next) {
var date = new Date()
if (date.getDay() === 0) {
var err = new Error("Don't bother me on Sunday!")
err.code = 'RESTING'
next(err)
} else {
next(date)
}
})
</source>
Visiting that same URL on a Sunday would get you this response instead:
<pre>{"success":false,"message":"Don't bother me on Sunday!","code":"RESTING"}</pre>

In realistic scenarios, you'll probably want to only respond with errors in the case of legitimate server errors, like a query failing or a missing file or something.

== Session state ==
All right, so you can easily fling data back to the client. Unbeknownst to you (before you read this sentence), it turns out that model-router also stores a session variable for each visitor (using a cookie that it sets on the client)! You can set parameters on this object whenever you like, and access them again later:
<source lang="javascript">
router.route('/counter/increment', function(parameters, session, next) {
session.counter = (session.counter || 0) + 1
next()
})
</source>
But now let's say that you want to see the current value of that pointless counter! But let's use a new feature that I feel like telling you about: guaranteed parameters. Like, you know, where a request is only valid if a certain value is provided? You could do a bunch of input parsing, and check to see if certain values were defined or whatnot, but model-router handles some of that for you.

Let's only give back the current value if the user provides a parameter called "please" - we won't even bother to check what it is, as long as it's set:

<source lang="javascript">
router.route('/counter/value', function(parameters, session, next) {
next(session.counter || 0)
}, ['please'])
</source>

If you don't pass in a parameter with the request (either as part of the query string in the URL, or in the headers), you'll get back this response:
<pre>{"success":false,"message":"You must provide these parameters: please","code":"MISSING_PARAMETERS"}</pre>
...but if the client does visit /counter/value?please=lol or whatever, they'll totally get the value back! And remember, that value is session-specific - visiting the same URL in a different browser could get you a completely different number.

It's up to you to maintain whatever state you like in those session variables. Obvious candidates are user information, and state about current high-traffic jobs that the user is engaged in (if they're sending requests every second, you probably don't want to hit the database more than is necessary).

You can (and probably want to) have session state expire after a certain amount of time. This function call will cause sessions to expire after 10 minutes of inactivity:
<source lang="javascript">
router.setSessionInactivityTimeout(10, function(session) {
console.log("A user just timed out! They got their counter up to " + session.counter + " first, though.")
})
</source>

== Authentication ==
But you probably want to have users log in before you do anything else, right? Well, hold on to your pants, because model-router makes that easy too.

<source lang="javascript">
router.route('PUT', '/authenticate', function(parameters, session, next) {
if (parameters.username === 'duff' && parameters.password === 'butts123') {
session.username = 'duff'
next("You're logged in now!")
} else {
next(new Error('Invalid login!'))
}
}, ['username', 'password'])

router.setSessionAuthentication(function(parameters, session, next) {
var logged_in = typeof session.username !== 'undefined'
next(logged_in)
})
</source>

Wait, what's that extra parameter there at the beginning? Oh, that's just how you specify a route for a specific HTTP method! The above code will only route requests to /authenticate to that function if the HTTP request was the PUT method. If you want, you can still specify a handler for /authenticate without giving a method - in that case, the most specific routing will be used.

We can now define routes that are only accessible to authenticated users:

<source lang="javascript">
router.routeAuthenticated('/counter/vip-value', function(parameters, session, next) {
next((session.counter || 0) * 10)
})
</source>

Try to visit /counter/vip-value without having authenticated, and you'll see
<pre>{"success":false,"message":"You have to be authenticated to access /counter/vip-value","code":"NOT_AUTHENTICATED"}</pre>
...but visit it after authenticating, and you'll see that your session's magical incrementable value is much larger than it would otherwise appear! Zoinks!

Web development/model-router

2013-02-19T22:40:15Z

Duff: All right, it's a page that tells you some stuff now.

model-router does a few things that make writing data servers easier:
* Routing
* Session handling/state
* Wrapping up authentication
* Checking for parameters existence

== Including ==
You could have multiple router-things if you wanted to - you know, in case you were running multiple sites from the same node.js server, or something - but for your purposes you'll probably just want to instantiate one.

<source lang="javascript">
var Router = require('model-router')
var router = new Router()
</source>

It doesn't launch any servers of its own, that would be rude. You'll want to create your own server in the usual way, and then tell model-router to handle it if appropriate.

model-router only sends back JSON responses, and doesn't do anything with static content out of the box, so if you want to serve HTML/JavaScript files or something, you'll have to do it yourself:

<source lang="javascript">
require('http').createServer(function(req, res) {
var pathname = require('url').parse(req.url).pathname
var match
if (match = /^\/static(\/.*)$/.exec(pathname)) {
require('send')(req, match[1]).root('./static/').pipe(res)
} else {
router.handleRequest(req, res)
}
}).listen(8080)
</source>

== Routing ==
All right, your server is running. You want to add a new response to certain messages - so that requests to yourdomain.com/information/time would get the current server time back, or something dumb like that.

<source lang="javascript">
router.route('/information/time', function(parameters, session, next) {
next(new Date())
})
</source>

Browsing to the URL should immediately get you back this response:
<pre>{"success":true,"output":"2013-02-19T22:00:56.507Z"}</pre>
But let's say that something bad happens on the server - maybe it's an error if a client asks for the server time on a Sunday. You could reflect that by rewriting the function like so:
<source lang="javascript">
router.route('/information/time', function(parameters, session, next) {
var date = new Date()
if (date.getDay() === 0) {
var err = new Error("Don't bother me on Sunday!")
err.code = 'RESTING'
next(err)
} else {
next(date)
}
})
</source>
Visiting that same URL on a Sunday would get you this response instead:
<pre>{"success":false,"message":"Don't bother me on Sunday!","code":"RESTING"}</pre>

In realistic scenarios, you'll probably want to only respond with errors in the case of legitimate server errors, like a query failing or a missing file or something.

== Session state ==
All right, so you can easily fling data back to the client. Unbeknownst to you (before you read this sentence), it turns out that model-router also stores a session variable for each visitor (using a cookie that it sets on the client)! You can set parameters on this object whenever you like, and access them again later:
<source lang="javascript">
router.route('/counter/increment', function(parameters, session, next) {
session.counter = (session.counter || 0) + 1
next()
})
</source>
But now let's say that you want to see the current value of that pointless counter! But let's use a new feature that I feel like telling you about: guaranteed parameters. Like, you know, where a request is only valid if a certain value is provided? You could do a bunch of input parsing, and check to see if certain values were defined or whatnot, but model-router handles some of that for you.

Let's only give back the current value if the user provides a parameter called "please" - we won't even bother to check what it is, as long as it's set:

<source lang="javascript">
router.route('/counter/value', function(parameters, session, next) {
next(session.counter || 0)
}, ['please'])
</source>

If you don't pass in a parameter with the request (either as part of the query string in the URL, or in the headers), you'll get back this response:
<pre>{"success":false,"message":"You must provide these parameters: please","code":"MISSING_PARAMETERS"}</pre>
...but if the client does visit /counter/value?please=lol or whatever, they'll totally get the value back! And remember, that value is session-specific - visiting the same URL in a different browser could get you a completely different number.

It's up to you to maintain whatever state you like in those session variables. Obvious candidates are user information, and state about current high-traffic jobs that the user is engaged in (if they're sending requests every second, you probably don't want to hit the database more than is necessary).

You can (and probably want to) have session state expire after a certain amount of time. This function call will cause sessions to expire after 10 minutes of inactivity:
<source lang="javascript">
router.setSessionInactivityTimeout(10, function(session) {
console.log("A user just timed out! They got their counter up to " + session.counter + " first, though.")
})
</source>

== Authentication ==
But you probably want to have users log in before you do anything else, right? Well, hold on to your pants, because model-router makes that easy too.

<source lang="javascript">
router.route('/authenticate', function(parameters, session, next) {
if (parameters.username === 'duff' && parameters.password === 'butts123') {
session.username = 'duff'
next("You're logged in now!")
} else {
next(new Error('Invalid login!'))
}
}, ['username', 'password'])

router.setSessionAuthentication(function(parameters, session, next) {
var logged_in = typeof session.username !== 'undefined'
next(logged_in)
})
</source>

We can now define routes that are only accessible to authenticated users:

<source lang="javascript">
router.routeAuthenticated('/counter/vip-value', function(parameters, session, next) {
next((session.counter || 0) * 10)
})
</source>

Try to visit /counter/vip-value without having authenticated, and you'll see
<pre>{"success":false,"message":"You have to be authenticated to access /counter/vip-value","code":"NOT_AUTHENTICATED"}</pre>
...but visit it after authenticating, and you'll see that your session's magical incrementable value is much larger than it would otherwise appear! Zoinks!

Web development/model-router

2013-02-19T22:30:09Z

Duff: moar

model-router does a few things that make writing data servers easier:
* Routing
* Session handling/state
* Wrapping up authentication
* Checking for parameters existence

== Including ==
You could have multiple router-things if you wanted to - you know, in case you were running multiple sites from the same node.js server, or something - but for your purposes you'll probably just want to instantiate one.

<source lang="javascript">
var Router = require('model-router')
var router = new Router()
</source>

It doesn't launch any servers of its own, that would be rude. You'll want to create your own server in the usual way, and then tell model-router to handle it if appropriate.

model-router only sends back JSON responses, and doesn't do anything with static content out of the box, so if you want to serve HTML/JavaScript files or something, you'll have to do it yourself:

<source lang="javascript">
require('http').createServer(function(req, res) {
var pathname = require('url').parse(req.url).pathname
var match
if (match = /^\/static(\/.*)$/.exec(pathname)) {
require('send')(req, match[1]).root('./static/').pipe(res)
} else {
router.handleRequest(req, res)
}
}).listen(8080)
</source>

== Routing ==
All right, your server is running. You want to add a new response to certain messages - so that requests to yourdomain.com/information/time would get the current server time back, or something dumb like that.

<source lang="javascript">
router.route('/information/time', function(parameters, session, next) {
next(new Date())
})
</source>

Browsing to the URL should immediately get you back this response:
<pre>{"success":true,"output":"2013-02-19T22:00:56.507Z"}</pre>
But let's say that something bad happens on the server - maybe it's an error if a client asks for the server time on a Sunday. You could reflect that by rewriting the function like so:
<source lang="javascript">
router.route('/information/time', function(parameters, session, next) {
var date = new Date()
if (date.getDay() === 0) {
next(new Error("Don't bother me on Sunday!"))
} else {
next(date)
}
})
</source>
Visiting that same URL on a Sunday would get you this response instead:
<pre>{"success":false,"message":"Don't bother me on Sunday!"}</pre>

In realistic scenarios, you'll probably want to only respond with errors in the case of legitimate server errors, like a query failing or a missing file or something.

== Session state ==
All right, so you can easily fling data back to the client. Unbeknownst to you (before you read this sentence), it turns out that model-router also stores a session variable for each visitor (using a cookie that it sets on the client)! You can set parameters on this object whenever you like, and access them again later:
<source lang="javascript">
router.route('/counter/increment', function(parameters, session, next) {
session.counter = (session.counter || 0) + 1
next()
})
</source>
But now let's say that you want to see the current value of that pointless counter! But let's use a new feature that I feel like telling you about: guaranteed parameters. Like, you know, where a request is only valid if a certain value is provided? You could do a bunch of input parsing, and check to see if certain values were defined or whatnot, but model-router handles some of that for you.

Let's only give back the current value if the user provides a parameter called "please" - we won't even bother to check what it is, as long as it's set:

<source lang="javascript">
router.route('/counter/value', function(parameters, session, next) {
next(session.counter || 0)
}, ['please'])
</source>

If you don't pass in a parameter with the request (either as part of the query string in the URL, or in the headers), you'll get back this response:
<pre>{"success":false,"message":"You must provide these parameters: please","code":"MISSING_PARAMETERS"}</pre>
...but if the client does visit /counter/value?please=lol or whatever, they'll totally get the value back! And remember, that value is session-specific - visiting the same URL in a different browser could get you a completely different number.

It's up to you to maintain whatever state you like in those session variables. Obvious candidates are user information, and state about current high-traffic jobs that the user is engaged in (if they're sending requests every second, you probably don't want to hit the database more than is necessary).

You can (and probably want to) have session state expire after a certain amount of time. This function call will cause sessions to expire after 10 minutes of inactivity:
<source lang="javascript">
router.setSessionInactivityTimeout(10, function(session) {
console.log("A user just timed out! They got their counter up to " + session.counter + " first, though.")
})
</source>

Web development/model-router

2013-02-19T22:25:34Z

Duff: moar

Web development/model-router

2013-02-19T21:58:40Z

Duff: First stuff

ISoft Data Systems

2013-02-19T15:54:16Z

Duff: Reverted edits by AntoinetteRosa1970 (talk) to last revision by Codeman

ISoft Data Systems is a software development company in Lincoln, Nebraska. They specialize in custom web development and business management solutions for the recycling and salvage industries.

[[Image:Turbine Flats from south side small.jpg|frame|ISoft Data Systems is located in the Turbine Flats Building.]]

== Address ==
2124 Y Street Flat 201 <br>
Lincoln, NE 68503

==Chat==
(8am - ~7pm [http://en.wikipedia.org/wiki/Central_Time_Zone_(North_America) Central]) Call or email us and we will help you set up a chat account so you can easily contact us whenever you like!

==Email==
* ITrack Support: [mailto:support@isoftdata.com?Subject=ITrack%20Support%20Question support@isoftdata.com]
* HeavyTruckParts.net Support: [mailto:support@heavytruckparts.net?Subject=Heavy%20Truck%20Parts%20Support%20Question support@heavytruckparts.net]

==Phone Numbers==
* Toll free phone: 800-929-1829 (8am - 6pm Central)
* Nebraska phone: 402-435-3850 (8am - 6pm Central)
* Fax: 402-435-7076

==Departments==
Those numbers there are our extension numbers!

===Tech Support===
* '''201 - All Support'''
** 110 - [[Cody Hanson]]
** 102 - [[Dayton Lowell]]
** 107 - [[Justin Wheeler]]
** 108 - [[Mark Hardisty]]
** 118 - [[Jordan Bonge]]

=== Management ===
* 103 - [[Brendan Evans]] (Sales)
* 100 - [[Emily Lowell]]
* 101 - [[Matthew Wegener]]
** 301 - Voicemail
* 111 - [[Tony Merritt]]
* 203 - [[Umeda Islamova]]

=== Application Development ===
* 105 - [[Dillon Sadofsky]]
* 104 - [[Josh Duff]]
* 115 - [[Justin McKinstry]]
* [[Svyatoslav Voznyuk]]

=== Web Development ===
* '''202 - All web development'''
** 114 - [[Amos Sterns]]
** 112 - [[Andrew Johnson]]
** 113 - [[Brian Roy]]

== See also ==
[[:Category:ISoft Employees|ISoft Employees]]

Presage/Barcodes

2013-01-24T23:18:19Z

Duff: First barcodes

Barcodes in Presage:

{| class="wikitable"
! Object
! Barcode contents
! Notes
|-
| Sample
| S[sampleid]
| Used in barcodes where the users will not be changing the sample's tag number
|-
| Work order
| W[workorderid]
|
|-
| Physical sample (bag)
| T[tagnumber]
| Identifies a sample to be submitted to multiple analyses. Is not globally unique, must be paired with a Work Order.
|}

Image Naming Conventions (Pro)

2013-01-04T17:58:38Z

Duff: Redirects to redirects are bad

#REDIRECT [[ITrack/Pro/Image Naming Conventions]]

Web development/CatHerder

2012-12-29T20:25:28Z

Duff: More data

The CatHerder framework is the equivalent of ITrack's [[ITrack/Master|Master]] extension loader. It started out handling authentication and the menu for passing users from screen to screen, but is now product-agnostic and can be used to load any arbitrary JavaScript extensions which may or may not have views.

These extensions have two components: a controller and a view (though the view is optional!). This springs from my initial assumption of how a reasonable client-side code structure might look, and my experience writing MVC code on the server.

In practice, this has not quite sufficient. Currently, most of the extensions that represent screens juggle what we would probably call a "document" inside of the controller, with the view containing some logic and containing the functions that update the DOM when the document's state changes, with the controller doing everything else.

Moving forward, I foresee there being some sort of document object that receives new data from user scans or user interaction in the view, handles communicating the data back and forth with the server, and gives the view hookups that fire whenever there is updated data to be changed in the display.

Right now, all that stuff has been going in the controllers. In the future, I see the controllers evolving to become simply the part of the extension that is exposed to other extensions. At the moment they are that, but also all the document-juggling,

But enough of my blathering, let's blither over some examples.

== Launching the app ==
It used to be slightly more complicated, but now it's not. In body onload or $(document).ready() or whatever, just call the catHerder function, passing an array containing strings of extension names.

<source lang="javascript">
catHerder([
'DeviceRegistration',
'Login',
'MainMenu',
'InventoryCount'
])
</source>

A new div is created in the body, and the specified extensions will be loaded and initialized in the order that they are found in the array. Once all extensions are initialized, the first one in the array will be shown.

== Making a new extension ==
To make a new extension, you just need a function named whatever you want the extension's name to be - that's your controller. If the extension has a view, create a second function with the same name as the controller, but with "View" at the end of the name. 8-|

You can create these functions in your controller, and they will be automatically called at the appropriate time (you shouldn't call them yourself):

* '''onCreate''' - called after the extension has been constructed (obviously), but also after the view has been constructed, and the prototypes and event emitter functions are in place.
* '''onAllExtensionsCreated''' - called after every extension has been initialized (and after onCreate has been called on them all). This is where you would attach your event handlers to other extensions.

Beyond those functions, you can also implement onShow, onHide, and onClose. They will be called whenever the show, hide, or close functions (which every controller has via the prototype object) are called.

These functions are optional, and you don't have to implement any of them - they are called using the callFunctionIfExists function that the controller prototype has. You can call optional functions on other extensions to by using the same function, but you probably don't want to, because you probably want to use...

== Events ==
Extensions are event emitters (via [https://github.com/bentomas/smokesignals smokesignals])! The closest equivalent in the ITrack framework is the inter-DLL messages.

Generally speaking, events should emit events on themselves, and other extensions should subscribe to those events by adding a handler to that extension.

Some events are emitted automatically by the extension prototype's functions - namely "shown", "hidden", and "closed". In the case of those events, the parameter passed along to the event's subscribers is the extension itself.

But wait, to subscribe to an event on an extension, you need to be able to access it! How do you reference other extensions? You use...

== Shared framework functions ==
How extensions access the world beyond their view!

* '''catHerder.getLastShownExtension()''' - probably pretty self explanatory, eh? The coordinator keeps track of every "shown" event emitted by all extensions, and returns whichever the last shown extension was when this function is called.
* '''catHerder.getExtension(extension_name)''' - grabs the extension that was instantiated by the coordinator when the catHerder function was originally called.
* '''catHerder.instantiateExtension(extension_name)''' - that's right, instantiating new extensions isn't just just for the coordinator!

At this point, I should stop and explain. I did make it possible for extensions to summon up new instances of other extensions. At the moment this is primarily used in places that want to have their own version of the "Menu" or "UserInput" extensions.

I'm not sure if I want to keep this paradigm - I suspect that eventually it might be best to just have a standard for calling extensions for one-time use. Still, I'm not yet sure how else to handle the sort of subclassing that currently happens between the MainMenu and Menu extensions.

Anyway, the point is - currently there are two classes of extensions: the ones instantiated by the coordinator itself, and the ones instantiated by other extensions at some point.

* '''catHerder.onExtension(extension_name, event, callback)''' - this attaches an event handler to *all* currently existing extensions of the given name. This is not the general case - the general case is to attach event handlers to the one version of the extension that was originally instantiated by the coordinator, using '''catHerder.getExtension(extension_name).on(event, callback)'''
* '''catHerder.showNextExtension()''' - you generally won't need to call this, since it is called automatically whenever an extension is closed. The extension that will be shown is decided like so:
*# If a "next extension" has been set, it is shown. That extension is then forgotten, and showNextExtension will continue with its normal behavior the next time it is called.
*# If a "default next extension" has been set, it is shown.
*# Otherwise, the coordinator proceeds through the extension list in the order the extensions were loaded.
* '''catHerder.setDefaultNextExtension(extension)''' - right now, the LXW menu screen calls ''catHerder.setDefaultNextExtension(this)'' as soon as it first gets shown. This makes it so that by default, whenever an extension is closed, the user is sent back to the menu. Pass in null to reset this value.
* '''catHerder.setNextExtension(extension)''' - the extension passed in will be shown next... just once!

Web development/CatHerder

2012-12-29T19:10:12Z

Duff: Getting started

Web development

2012-12-29T18:40:53Z

Duff: Initial page with redlinks for CatHerder and model-router

Development on various mobile web development projects has necessitated some new tools! Tools that need to be documented! I will try to do so here.

The equivalent of ITrack's [[ITrack/Master|Master]]/[[ITrack/Extension|Extension]] framework is the [[Web development/CatHerder|CatHerder]].

While [[ITrack/Enterprise/LXW|ITrack LXW]] uses a stateless PHP back-end, we also have the [[Web development/model-router|model-router]] for quickly building servers that can sling data back and forth with our webapps.

ITrack/Extension

2012-12-29T18:37:09Z

Duff: Fixing redirect link

In ITrack lingo, an extension is a general name for a DLL (dynamically loaded library) that can be loaded into [[ITrack/Master|ITrack.exe]]. This implies a certain conformation to ITrack standards and APIs. These extensions are located in the installation directory (normally: C:\Program Files\ISoft Data Systems\[Product Name]) with ITrack.exe. In order for Master to load an extension, it must be specified in its [[Configuration File]].

==Extension Types==
Extensions all conform to the same standards, but fall into one of several logical categories depending on their purpose in ITrack:
* [[Module Extensions]]
* [[Utility Extensions]]
* [[Third Party Extensions]]
* [[User Created Extensions]]
* [[Database Connection Extensions]]

==Extension Features==
Extensions can have some or all of the following features included in them; though the presence or absence of some of these features might change its 'extension type'.
* [[Menu|Menu Options]] displayed at the top of Master
* [[Module|Modules]] displayed in the "Main Menu" in Master.
* [[Database Connection|Database Connections]] used for connecting to a [[Database]].
* [[Extension Function|Extension Functions]] used by other extensions and modules.

== See Also ==
* [[ITrack/Creating_an_Extension|Creating an Extension]]

[[Category:ITrack]]

ITrack/IDispatch error 522

2012-12-22T00:16:48Z

Duff: Minor formatting

[[File:IDispatch Error 522.png]]

== Cause ==
This error occurs because the directory path listed in the QuickBooks Toolkit in ITrack Pro must be the same as what was opened when the user opened QuickBooks.

== Solution ==
Try using a mapped network drive to the QuickBooks company file instead of the direct path (or vice versa).

For example, if the the QuickBooks Toolkit has the path listed as: '''\\server\QuickBooks\CompanyFile.qbw'''

Try using something like this instead: '''Z:\QuickBooks\CompanyFile.qbw'''

ITrack/Pro/Part Configuration Screen

2012-12-19T16:52:02Z

Duff: /* Selecting Parts for Drop Down Lists */ Fixing some broken links to other manual pages

[[Image:Pro_Part_Config_Screen_1.png|thumb|right|600px|Parts Configuration Screen]]
==Selecting Parts for Drop Down Lists==
The Part Configuration Screen allows you to decide which parts will show up in the drop down lists on the [[ITrack/Pro/Parts Screen|Part Management Screen]] and the [[ITrack/Pro/Search Screen|Search Screen]].

Click on Part Configuration in the Main Menu to open the Part Configuration Screen. Make sure the Parts List tab is selected. When you first install ITrack, all the parts will be checked. You can choose to disable parts from the list that are infrequently or never used.
Now, when you enter or search for a part, only the parts you have checked will be displayed. On the previous page, we unchecked hood hinge. The image below shows the Search Screen and the hood hinge is now gone.

==Adding, Editing, or Removing Parts==
The Parts List tab also allows you to add, edit, or remove parts. On the bottom of the screen you will see these buttons.
It is important to remember there is a difference between removing and disabling a part.
To remove a part, click on that part and click Remove. If you ever want the part back, you must add it into ITrack.
Disabling a part is when you uncheck the box next to the name of the part. The part will still appear in the Parts List but will not show up when you are entering parts.

Clicking the Add button brings up the Add New Part Type box. From here, you can enter in information about a part. When you are satisfied with your new part, click the OK button.

The More fields are very useful. For some parts, ITrack already has the more fields filled out. You can always change what the More fields contain, whether they were filled out by ITrack or blank.

After entering information into the More fields, they will show up on the Part Management Screen.

To edit an existing part, click on the part you wish to edit and then click the Edit button and the Edit Part Type box will appear. Make any changes to the part and click OK when you are done.

If you want to delete a part from the Parts List, click on the part and then click the Remove button. When you click Remove you will get one of two different messages. You may get a dialog box asking you to confirm that you want to delete a part or you may get a message that the part you want to delete is in inventory. If a part is in your inventory, you cannot delete it.
[[Image:Pro_PartConfig_Questions_1.png|thumb|left|500px|Parts Configuration Questions Screen]]

==Part Questions==
Part Questions allows you to create questions that will be asked about specific parts when you enter them in your inventory. This allows you to have specific information about every part type that is entered.
To create a part question, first select a part by clicking on it in the Parts List tab. Next, click the Edit Part Questions button in the lower right corner. This brings up the Questions dialog box.

Now, click the Add button to create a question. You can add as many questions as you would like. Click on a question and then click the Move Down or Move Up buttons to change the order of your questions. You may want more important questions towards the top of your list.

When you are finished creating questions for a part, click the OK button to save.
Once your questions are saved they will show up in the Part Management Screen. When you enter the part that has these questions, the questions will show up in the [[:File:Pro_PartConifig_Q&AScreen_1.png|Q And A tab]].

Click in the Value field to type in the answer to you question. Now, when your sales people look up parts, they can have access to this valuable and more detailed information about the part.

==Part Manufacturers & Models==
From the Part models tab you can add and edit part manufacturers and models.

===Adding New Manufacturer or Model===
{{Tip| You can also add Part manufacturers and models directly from the Parts screen by click the Add button or pressing Alt+d}}
# Click the '''Add model''' button
# If your creating both a new manufacturer and model, check the '''Create new manufacturer''' checkbox.
# The existing manufacturers dropdown will disappear and a new field will appear directly below the checkbox where you can type in the new manufacturer name.
# Fill in the remaining fields in the dialog to create the new manufacturer and model.

{{Tip|Manufacturers that appear at the bottom of the manufacturers list and whose text appears in a shade of gray have no models for that part type. Note that Part manufacturers are not per part type(they're global) but part models are per part type}}

===Edit Manufacturer or Model===
# Select the Part type from the dropdown on the '''Part models''' tab
# Click the manufacturer you want to edit
# You'll notice the manufacturer field is editable, you can type in this field to rename Manufacturers
# Once you select a manufacturer the corresponding models will appear in the pane on the right
# Clicking any of the fields on the '''Models''' pane will cause the field to become editable, inline.
# Default pricing is configured per model and can be configured (once a model is selected) in the bottom right pane(also inline editing).

{{Tip|If you are having trouble finding the manufacturer in the Part Management Screen once you have edited it in the Part Configuration Screen, then try setting the '''First Year''' field to zero and the '''Last Year''' to 9999}}

[[Category:ITrack/Pro/Extensions]]

ITrack/Pro/Part Configuration Screen

2012-12-19T16:48:12Z

Duff: /* Part Questions */ Fixing internal wiki link

[[Image:Pro_Part_Config_Screen_1.png|thumb|right|600px|Parts Configuration Screen]]
==Selecting Parts for Drop Down Lists==
The Part Configuration Screen allows you to decide which parts will show up in the drop down lists on the [[Parts Screen (Pro)|Part Management]] Screen and the [[Search Screen (Pro)|Search]] Screen.

Click on Part Configuration in the Main Menu to open the Part Configuration Screen. Make sure the Parts List tab is selected. When you first install ITrack, all the parts will be checked. You can choose to disable parts from the list that are infrequently or never used.
Now, when you enter or search for a part, only the parts you have checked will be displayed. On the previous page, we unchecked hood hinge. The image below shows the [[Search Screen (Pro)|Search]] Screen and the hood hinge is now gone.
==Adding, Editing, or Removing Parts==
The Parts List tab also allows you to add, edit, or remove parts. On the bottom of the screen you will see these buttons.
It is important to remember there is a difference between removing and disabling a part.
To remove a part, click on that part and click Remove. If you ever want the part back, you must add it into ITrack.
Disabling a part is when you uncheck the box next to the name of the part. The part will still appear in the Parts List but will not show up when you are entering parts.

Clicking the Add button brings up the Add New Part Type box. From here, you can enter in information about a part. When you are satisfied with your new part, click the OK button.

The More fields are very useful. For some parts, ITrack already has the more fields filled out. You can always change what the More fields contain, whether they were filled out by ITrack or blank.

After entering information into the More fields, they will show up on the Part Management Screen.

To edit an existing part, click on the part you wish to edit and then click the Edit button and the Edit Part Type box will appear. Make any changes to the part and click OK when you are done.

If you want to delete a part from the Parts List, click on the part and then click the Remove button. When you click Remove you will get one of two different messages. You may get a dialog box asking you to confirm that you want to delete a part or you may get a message that the part you want to delete is in inventory. If a part is in your inventory, you cannot delete it.
[[Image:Pro_PartConfig_Questions_1.png|thumb|left|500px|Parts Configuration Questions Screen]]

==Part Questions==
Part Questions allows you to create questions that will be asked about specific parts when you enter them in your inventory. This allows you to have specific information about every part type that is entered.
To create a part question, first select a part by clicking on it in the Parts List tab. Next, click the Edit Part Questions button in the lower right corner. This brings up the Questions dialog box.

Now, click the Add button to create a question. You can add as many questions as you would like. Click on a question and then click the Move Down or Move Up buttons to change the order of your questions. You may want more important questions towards the top of your list.

When you are finished creating questions for a part, click the OK button to save.
Once your questions are saved they will show up in the Part Management Screen. When you enter the part that has these questions, the questions will show up in the [[:File:Pro_PartConifig_Q&AScreen_1.png|Q And A tab]].

Click in the Value field to type in the answer to you question. Now, when your sales people look up parts, they can have access to this valuable and more detailed information about the part.

==Part Manufacturers & Models==
From the Part models tab you can add and edit part manufacturers and models.

===Adding New Manufacturer or Model===
{{Tip| You can also add Part manufacturers and models directly from the Parts screen by click the Add button or pressing Alt+d}}
# Click the '''Add model''' button
# If your creating both a new manufacturer and model, check the '''Create new manufacturer''' checkbox.
# The existing manufacturers dropdown will disappear and a new field will appear directly below the checkbox where you can type in the new manufacturer name.
# Fill in the remaining fields in the dialog to create the new manufacturer and model.

{{Tip|Manufacturers that appear at the bottom of the manufacturers list and whose text appears in a shade of gray have no models for that part type. Note that Part manufacturers are not per part type(they're global) but part models are per part type}}

===Edit Manufacturer or Model===
# Select the Part type from the dropdown on the '''Part models''' tab
# Click the manufacturer you want to edit
# You'll notice the manufacturer field is editable, you can type in this field to rename Manufacturers
# Once you select a manufacturer the corresponding models will appear in the pane on the right
# Clicking any of the fields on the '''Models''' pane will cause the field to become editable, inline.
# Default pricing is configured per model and can be configured (once a model is selected) in the bottom right pane(also inline editing).

{{Tip|If you are having trouble finding the manufacturer in the Part Management Screen once you have edited it in the Part Configuration Screen, then try setting the '''First Year''' field to zero and the '''Last Year''' to 9999}}

[[Category:ITrack/Pro/Extensions]]

ITrack/Enterprise/LXW

2012-11-28T21:39:10Z

Duff: /* Picking */ Clarifying a bit

ITrack/Enterprise/LXW

2012-11-27T20:44:25Z

Duff: /* Picking */ Fixed so that it wasn't a pack of lies

The mobile version of ITrack, for running warehouses with scanners!

== Picking ==
# Scan a sales order
# Scan a part
# Scan the location you found the part
## If the location is not one of the locations where the part was currently allocated from, you will need to select the location that you are picking the part for
# Scan a destination location (if you want to, otherwise you can close the screen or scan a new sales order)

The part gets marked as picked in the delivery system, and gets moved to the destination location. If you don't specify a destination location, it uses the default, which is set in the store settings.

== Inventory move ==
# Scan a location
# Scan any number of parts at the location
# Scan a destination location

All the parts you scanned get moved!

== Inventory Detail ==
Scan any part to see information about it!

== Inventory Count ==
# Scan a location
# Scan all the parts at that location
# Scan a new location to count at, or close the screen

All of the parts that you found at that location are moved there, if necessary. All parts that should have been found there, but weren't, get moved to the Variance location!

ITrack/Enterprise/LXW

2012-11-12T22:56:53Z

Duff: DOCUMENTATION

The mobile version of ITrack, for running warehouses with scanners!

== Picking ==
# Scan a sales order
# Scan a part
# Scan a destination location (if you want to)

The part gets marked as picked in the delivery system, and gets moved to the destination location. If you don't specify a destination location, it uses the default, which is set in the store settings.

If you don't want to scan a destination location, you can just scan a new document to begin picking another part, or close the screen.

== Inventory move ==
# Scan a location
# Scan any number of parts at the location
# Scan a destination location

All the parts you scanned get moved!

== Inventory Detail ==
Scan any part to see information about it!

== Inventory Count ==
# Scan a location
# Scan all the parts at that location
# Scan a new location to count at, or close the screen

All of the parts that you found at that location are moved there, if necessary. All parts that should have been found there, but weren't, get moved to the Variance location!

User:Jbonge

2012-11-12T20:40:50Z

Duff: Welcome to ISoft!

[[Category:ISoft Employees]]

Category:ISoft Employees

2012-10-15T15:14:50Z

Duff: /* Developers */

Want to talk to one of these people? You can totally [[ISoft Data Systems#Phone_Numbers|call us]]!

Are you one of these people? You should probably read up on the [[things ISoft employees should know]]!

==Administration==
* [[Matthew Wegener]]
* [[Emily Lowell]]

==Art and Advertising==
* [[Amos Sterns]]

==Developers==
* [[Andrew Johnson]]
* [[Brian Roy]]
* [[Dillon Sadofsky]]
* [[Josh Duff]]
* [[Justin McKinstry]]
* [[Steven Patras]]
* [[Svyatoslav Voznyuk]]

==Implementation==
* [[Tony Merritt]]
* [[Mark Hardisty]]

==Sales==
* [[Brendan Evans]]

==Support==
* [[Cody Hanson]]
* [[Dayton Lowell]]
* [[Justin Wheeler]]

Category:ISoft Employees

2012-10-09T20:20:51Z

Duff: /* Developers */ Sure, we'll call Ryan a developer

Want to talk to one of these people? You can totally [[ISoft Data Systems#Phone_Numbers|call us]]!

Are you one of these people? You should probably read up on the [[things ISoft employees should know]]!

==Administration==
* [[Matthew Wegener]]
* [[Emily Lowell]]

==Art and Advertising==
* [[Amos Sterns]]

==Developers==
* [[Andrew Johnson]]
* [[Brian Roy]]
* [[Dillon Sadofsky]]
* [[Josh Duff]]
* [[Justin McKinstry]]
* [[Ryan Geiger]]
* [[Steven Patras]]
* [[Svyatoslav Voznyuk]]

==Implementation==
* [[Tony Merritt]]
* [[Mark Hardisty]]

==Sales==
* [[Brendan Evans]]

==Support==
* [[Cody Hanson]]
* [[Dayton Lowell]]
* [[Justin Wheeler]]

MediaWiki:Sidebar

2012-10-05T22:59:01Z

Duff: Adding link to Presage

Presage

2012-10-05T22:55:44Z

Duff: New Presage landing page

<inputbox>
type=fulltext
searchbuttonlabel=Search Presage
break=no
hiddentext=-(intitle:ITrack/AX) -(intitle:ITrack/Enterprise) -(intitle:ITrack/Pro)
</inputbox>

Please feel free to [[ISoft chat|instant message]], [mailto:support@isoftdata.com email] or [[ISoft Data Systems|call]] us.

ITrack/Enterprise

2012-10-05T22:54:41Z

Duff: Filtering out Presage content

[[Image:ITrack_Enterprise_Logo_for_Wiki2.jpg|frame|center]]

<inputbox>
type=fulltext
searchbuttonlabel=Search ITrack Enterprise
break=no
hiddentext=-(intitle:ITrack/Pro) -(intitle:ITrack/AX) -(intitle:Presage)
</inputbox>

* [http://goo.gl/mod/sYvg Submit suggestions on how to make the software better!]
* [[ITrack_Enterprise_User_'s_Guide|ITrack Enterprise User's Manual]]
* [[ITrack/Enterprise/Troubleshooting|Troubleshooting]]
* [[:Category:ITrack/Problems/Error_Messages|Error Messages]]
* [[ITrack/Enterprise/Changelog|Recent Changes to ITrack Enterprise]]

Please feel free to [[ISoft chat|instant message]], [mailto:support@isoftdata.com email] or [[ISoft Data Systems|call]] us.

ITrack/Pro

2012-10-05T22:54:29Z

Duff: Filtering out Presage content

[[Image:ITrack_Pro_Logo_for_Wiki.png|frame|center]]

<inputbox>
type=fulltext
searchbuttonlabel=Search ITrack Pro
break=no
hiddentext=-(intitle:ITrack/AX) -(intitle:ITrack/Enterprise) -(intitle:Presage)
</inputbox>

* [[ITrack/Pro/User Guide|ITrack Pro User's Manual]]

* [[ITrack/Pro/Troubleshooting|Troubleshooting]]

* [[:Category:ITrack/Problems/Error_Messages|Error Messages]]

* [[ITrack/Pro/Changelog|Recent Changes to ITrack Pro]]

Please feel free to [[ISoft chat|instant message]], [mailto:support@isoftdata.com email] or [[ISoft Data Systems|call]] us.

Template:Search

2012-10-05T22:53:55Z

Duff: Adding link to Presage

Search the entire wiki:
<inputbox>
type=search
break=no
buttonlabel=Go
searchbuttonlabel=Search
</inputbox>
* Search '''[[ITrack/Pro|ITrack Pro]]'''
* Search '''[[ITrack/Enterprise|ITrack Enterprise]]'''
* Search '''[[Presage]]'''
* Search [[Database:Search|database documentation]]
* Search [[Internal:Search|internal documentation]]

Installing LXW

2012-09-25T16:26:56Z

Duff: /* Dependencies */ We actually can work with SVN 1.6 or better

Installing LXW

2012-09-25T16:25:45Z

Duff: Adding dependencies

Conference Room Setup

2012-08-19T04:08:53Z

Duff: Fixing headers

This guide permanently resides at: http://wikido.isoftdata.com/index.php/Conference_Room_Setup

==How to get started==
If nothing is turned on:
# Turn on the receiver [[Image:receiver_power.jpg|thumb|none]]
# Turn on the projector [[Image:remote.jpg|thumb|none]]
# Select the correct source for what you want to do
#* For Media/Presentation Computer: Press BD/DVD [[Image:receiver_bddvd.jpg|thumb|none]]
#* For XBox: Press GAME [[Image:receiver_game.jpg|thumb|none]]
# Turn on your source
#* The media computer should have a solid white light for its power. If not, press the power button on it [[Image:mediapc.jpg|thumb|none]]

==When you're done==
# Turn off your video source
# Turn off the projector [[Image:remote.jpg|thumb|none]]
# Turn off the receiver [[Image:receiver_power.jpg|thumb|none]]

==Further Questions==
Ask Justin M at ISoft (room 103) or Matthew!

Tony Merritt

2012-08-16T21:19:47Z

Duff: He made a new account

#REDIRECT [[User:Tmerritt]]

User:Tmerritt

2012-08-16T21:19:00Z

Duff: Tony's new account

Tony is a sexy man who currently makes a living by pwning other people's problems.

[[Category:ISoft Employees]]

ITrack/Barcodes

2012-08-16T16:53:12Z

Duff: /* Barcode contents */ Adding work order

Several elements of ITrack and ITrack software utilize barcodes. All ITrack products should utilize a similar barcoding scheme.

== Preamble and postamble ==
Virtually every barcode scanner can be programmed to simulate a keypress combination before entering the barcode contents (the preamble) and after (postamble).

=== ITrack Pro ===
ITrack Pro document screens (Sales, Quotes, Purchase Orders) expect a preamble of Ctrl+b and a postamble of \n.

The document screens will take whatever value is between those characters and do a lookup by [[ITrack/Pro/Part Number|partnum]] (the value encoded in barcodes on ITrack Pro tags), and if no values are found by partnum, by UPC (the value encoded into the barcodes printed on most products).

=== Workclock ===
The workclock system expects the barcode scanner to provide a preamble and postamble of ':$:'.

== Barcode contents ==
Depending on the context, the barcode will encode different types of values.

{| class="wikitable"
! Object
! Barcode contents
! Notes
|-
| Inventory
| '''[inventoryid]''' OR '''[UPC code]''' OR '''[OEM Number]'''
| If the number is less than 10 digits, it is assumed to be the primary key of an inventory record (inventoryid in Enterprise, partnum in Pro). Numbers with greater than 10 digits are assumed to be UPC codes.
|-
| Location
| '''%[locationid]''' OR '''[full location name]'''
| Ideally, location barcodes should be the locationid, prefaced by a % sign. In some cases, sadly, they may be an unqualified string.
|-
| ITrack user
| '''U[userid]'''
|-
| Work Order
| '''W[storeid]-[workorderid]'''
|-
| Work Order Job
| '''J[jobid]'''
|-
| Sales Order
| '''S[storeid]-[salesorderid]'''
|-
| Purchase Order
| '''P[storeid]-[purchaseorderid]'''
|-
| Transfer Order
| '''T[transferorderid]'''
|-
| Serialized part
| '''[inventoryid]-[inventoryserialid]'''
|}

=== Other, context-sensitive ===
Prefaced with + - Signifies that the rest of the barcode contains a context-sensitive command, which will probably not have meaning outside of magical bar-code applications.
* CLOCKIN - Clocks the selected user into a selected job
* CLOCKOUT - Clocks the selected user out of an active job