1. Use Visual Studio 2003 to create the standalone 1.1 framework DLL
2. Copy the dll generated (located under the /bin directory) to your webserver hosting Deltek:
Program Files\Deltek\Vision\Workflow
3. Once the dll is loaded it is visible to Deltek’s WF. You can then configure your WorkFlow by using the left navigation:: Configuration | WorkFlow | User Initiated Workflow
4. Select Projects from the Application dropdown to get the Project Info Center WFs
5. WF has a top level and sublevels so you can group things anyway you want – we have a few top categories and many sublevels under each categories separated by New & Edit which are the 2 distinctions since these are actually DB triggers (at least that is what I think launches these) executed on insert, update and delete commands in SQL. Lots here see normal doc and that pdf from the Insight Class.
6. Select Invoke Custom Method from the choices and you will see the following dialog box which “sees” all the dlls in that Workflow directory.
a. Select the dll which is labeled Assembly
b. Select the class from that dll
c. Select the method call from that class
7. The rest is mapping parameters which are all send via strings (ie. no Boolean objects or primitives here checkboxes just send ‘Y’ or ‘N’)
a. To add a parm you cannot just type in the field name like you’d expect . First slide the vertical line between name and value to the left a little so you can see the ellipsis (…) on the far right of each row in the parm grid. Click on that and you get yet another dialogue box. Select your field and make sure you click the Add Column button then OK. You can type in the expression box directly just be careful. If you do this a lot you can save off the field names in ‘[:name]‘ format in text file & cut/paste.
Lastly check the Invoke after all changes are saved checkbox to ensure all your parms are good.
I have noticed timing issues on parms that are filled in from other workflows so show care there. Also be aware these WF can significantly slow down save performance.
Stored Procedures ::
1. Create a viable SP
2. WF “sees” all the SPs so no other migration is needed
3. Select Stored Procedure & load parms the same way as above.
