Just to remind you all of the the what we should be doing when setting up customers/korecs/Trimble workflow setups. Its all based around company name setup in the General settings of workflow - but allowing an individual manager to track there OWN allocated jobs requires just a little consideration

Situation 1

Simple situation where a customer has 1 workflow manager issuing jobs would simply have company=ABCLTD setup in workflow / with a corresponding ABCLTD ftp space and ABCLTD tracking table.

Situation 2

if a company has multiple managers issuing jobs, but ALL the managers maintain job status information on a SINGLE MDB stored on a network drive - then the sitaution is exactly the same as above (This is ideally how a customer should be setup)

Situation 3 (as for Trimble & Korec)

If a company has multiple managers issuing jobs and the each storing their OWN workflow MDB's locally (as we do & korec sales reps will do) - then setting up the above will cause problems as Manager1 could end up downloading jobs that where intended for Manager 2

The remedy is to use separate company names company =TRIMBLE_PJB setup in workflow / with a corresponding TRIMBLE_PJB ftp space / But these will all communicate tracking/incidents with a single TRIMBLE company tracking table.

use the '_' to effectivly differentiate between COMPANIES and DEPARTMENTS within that company. Each Deaprtment has there own FTP site but all communicate back with a single COMPANY tracking/incident database.

 
devnews/workflow_setups.txt · Last modified: 2009/03/16 07:11 by wynsleeman
Recent changes RSS feed Creative Commons License Driven by DokuWiki