Inconsistent Behaviour with Setting of Out Of Office


Badge +12


 

Symptoms

 


Seeing inconsistent behaviour when an Out Of Office delegate is specificed either via the Worklist option or the Workspace option. For some users this is working fine, but for other users, despite who is set as delegate, that person never sees the delegators tasks in their worklist.
 

 

Diagnoses

 


If you have a look within the K2 database: Server.ActionShare
you can see the dates being cached in one the rows, this not the expected behaviour as it is supposed to contain NULL Values.
The following script will show if the users out of office had been set on a DB level:

Select 'OOF Setup FOR: [' [A1].ActionerName '] TO: [' [A2].ActionerName ']',
'[' [A1].ActionerName '] Status is: ' CASE WHEN [A1].Status = 1 THEN '[OUT of Office]' ELSE '[IN Office]' END
From [K2].[Server].[Actioner] [A1]
Join [K2].[Server].[ActionerShare] [AS] On [AS].ActionerID = [A1].[ID]
Join [K2].[Server].[ActionerShareWorktype] [ASWT] On [ASWT].ActionerShareID = [AS].[ID]
Join [K2].[Server].[Worktype] [WT] On [WT].[ID] = [ASWT].WorktypeID
Join [K2].[Server].[WorktypeShare] [WTS] On [WTS].WorktypeID = [WT].[ID]
Join [K2].[Server].[Actioner] [A2] On [A2].[ID] = [WTS].ActionerID

 

 

 

Resolution

After the above has been confirmed, go back to the table Server.ActionShare and change the value within the row with dates NULL.

Restart the service and go back to test to see if OOF is working.
Please do log a support call to get assistance when perform direct DB modifications. It is also wise to take a back up of the database.

 

 

 



 

0 replies

Be the first to reply!

Reply