Overview: A basic summary of the processes used with Mobile WorkForce.
1. User performs a task on their mobile device using the WorkForce site www.porwork.com
2. WorkForce server creates the necessary files for each transaction that is submitted.
3. Rental stores server is setup to run a task every 1 minute (this is setup in Configure Task Runner – Configuration>Store Configuration>Configure Task Runner).
4. This task downloads the WorkForce server transaction files, and upload new data to WorkForce site if necessary.
5. Downloaded transaction files are saved in x:\POR\Pictures\Quote\Mobile\
6. If any transactions files are received, the WorkForceEngine is started.
7. WorkForceEngine reads the transaction files and moves/renames any image/signature files.
a. Files are saved in:
b. Contract Images go into x:\POR\WebTasks\Images\ContractImages\Year\Month\
c. Contract Signatures go into x:\POR\WebTasks\Images\ContractSignatures\Year\Month\
d. Item Images go into x:\POR\WebTasks\Images\ItemImages\Year\Month\
8. WorkForceEngine updates the WebTaskEngine database (x:\POR\WebTasks\WebTaskEngine.mdb) with the transaction detail.
9. WorkForceEngine starts the Counter System with a command telling it to read from the WebTaskEngine database.
10. Counter System processes the tasks and updates the WebTaskEngine database fields ImportedOn (datetime), and ImportingAgent (name of program doing work).
a. If it is a Contract Attachment, a Windows Shortcut .lnk file is added to :\POR\Attachments\ pointing to the file in the folder from step #7 and referencing the contract within the link filename. These show in POR as Contract Attachments.
b. If it is a Contract Signature, the image file is imported into the Database TransactionSignature table.
c. If it is an Item Image, the image file is imported into the POR Database ItemPicture.
d. Any other task is put directly in the corresponding place in the database (i.e. Call Log, Service Contract, Updated arrival time, etc.)
11. Process is complete.