K2 Deployment - Custom SQL service broker

When using SQL Service broker is used with Stored Procedures you need to make sure the service instance user has the view definition permission on DB so that Stored procedures and views are loaded with proper Schema.


If not then following thing will happen.


your Stored Procedure parameters will always show as Required ( even if you have provided default value.)


Thanks

K2 Client Set Up - Error connecting to K2 Server

When installing K2 Client using set up in Windows machine after you have removed existing K2 client installation, if the Type of installation page is not showing during set up , do the following.


1. Go to Registry - start-> run-> regedit
2. HKEY_LOCAL_MACHINE - SOFTWARE - look for source code. if there is registry entry already there. Please remove and restart your machine. the Set up will ask for Type of installation page now.

K2 Blackpearl Roles Update or Refresh (Instantly)

The trick of all this is that K2 won't actually refresh its identity cache until it needs that identity again. Setting the ExpiresOn, etc. fields as mentioned above is only half the equation. The other half is to tell K2 you need that identity object which actually triggers the refresh.

You can force the identity cache to expire for a particular role by running the following SQL query on your K2 database:

update [Identity].[Identity] set
ExpireOn = '2013-01-01',
MembersExpireOn = '2013-01-01',
ContainersExpireOn = '2013-01-01'
where FQN = 'role_name';

where role_name is the name of the role you wish to refresh. To actually trigger the role refresh, execute the Get Role Users method in the UMUser SmartObject on the role you wish to refresh.