How to associate 1 K2-flow with 100+Doclibs

  • 27 April 2006
  • 2 replies
  • 0 views

Badge +1
Hi all,

We're testing a little problem.
We have already written a program that automatically generates Sites with the associated Document Libraries(+-10 per site) based on data that comes from another program.
Now that is done, we want to integrate K2-workflows on some of the (automatically generated) document libraries on the(automatically) generated sites.
We have found out, that it is possible to make a workflow in K2 on 1 document library, but we haven't found out how we can use that flow to use it on other document libraries as well.

* Simply copying and pasting the advanced options of the document library is not enough because that is the same for every document library with a integrated workflow
* selecting more than one document library isn't an option(and not possible I think), because every week some extra sites(and docibs) are generated
* In the map Program files/K2 we have found the maps that keep DLL's of the workflow. problem: NO XML-file, not usefull to copy it and/or rename it to use for other doclibs.

Does anyone have a solution for this???
We just can't make more than 100workflows and weekly another +-10 for each doclib...

2 replies

Badge +6
Hi $Tekkie,

When the SharePoint process template is run in K2.net Studio the event sink details get entered in the Advanced Settings section for the specified doclib. A new list also gets generated in the same website called K2.net Events. This list contains the details for which process to start when an event occurs on a specific doclib.

So in essense you should do two things in your application that creates the doclibs:
1. Populate Advanced Settings section for the doclib on creation in your application.
2. Create the K2.net Events list in the site and add the relevant list entries. (If you have a look at this list you will see that it will be quite easy to do and quite a few clients have done this before.)

I hope this helps.
Badge +1
jeps... it has to work...

this is also the only relevant solution for it.
We'll have te built this into the (generating) code... next week we'll find out :-)

Reply