IT:AD:K2:Issues

Be aware that if your destination users are not specified using a fully-qualified name (FQN), such as DomainName\UserName, the default user manager security label is pre-pended to the name when the destinations are resolved.

T

he default security label is “K2” and corresponds to Active Directory (AD) users. An example of a user in the DENALLIX domain is “K2:DENALLIX\Mike”. Other user managers, such as the SQL user manager, use different security labels. This means that if you assign tasks to SQL users using their unqualified user names, the server prepends “K2” to the SQL user and assigns tasks to users that don't exist.

Regarding Client Events:

This code could be invoked from a .NET assembly, a web service, or whatever approach best matches your situation; just add a reference to the SourceCode.Workflow.Client assembly. The identity used to connect to the K2 Server needs be assigned the *Server Event* right for the process in the Management Console

How does an asynchronous server event differ from the normal synchronous code event? When the workflow engine encounters a synchronous server event it executes the event and then continues the workflow. In an asynchronous event, the workflow engine executes the event and then stops. When you first drag a server code event onto the workflow design canvas, by default it is synchronous. A server code event can be changed from synchronous to asynchronous by adding one line of code to the event: K2.Synchronous = false;

Regarding Actions / Outcomes

However, it is recommended that lines that

c

ontained modified rules are kept to a minimum. This allows greater process maintainability because if the wizard is re-executed and the lines regenerated, the modifications are lost.

• The option to automatically generate lines based on actions is off by default once lines have been generated the first time, but this is something to be aware

of*