Hi All,
We want to integrate prioritizing of tasks in our application.
The priotity of each instance of a task will differ. Now we found that K2 only allows three types of priorities, High, Medium and Low. This causes an issue because we have different level of importence per task.
Is there a way to add more priorities?
What would happen if we added priorities in the _Priority table on the K2Log DB?
If we made any changes like this to the K2Log would this affect the support that we have on K2? If we arent allowed to make changes like this could someone be sent out to do this for us?
Thanks
Page 1 / 1
Hi Van
Adding entries to the _Priority table in the database is not the solution to your problem for various reasons. The first is that active Process and Activity data is stored in the K2 database, which we also refer to as the Transaction Database, and not the K2Log database. The second is that while we support customers writing custom queries against the K2 Log database for reporting purposes, we don't support customers making changes to the K2/K2 Log database structure/content.
What I would suggest is that you use a Process- or Activity Datafield and create a worklist filter to differentiate between priorities. The advantage is that you would have total control over the priorities, which would then be 100% customizable and would not be affected by a K2 upgrade. The choice of a repository for your priorities is up to you (string tables, flat files etc.), but I would suggest a SQL table since it is easily accessible for lookup through the SQL Event.
Regards
Emile
Adding entries to the _Priority table in the database is not the solution to your problem for various reasons. The first is that active Process and Activity data is stored in the K2 database, which we also refer to as the Transaction Database, and not the K2Log database. The second is that while we support customers writing custom queries against the K2 Log database for reporting purposes, we don't support customers making changes to the K2/K2 Log database structure/content.
What I would suggest is that you use a Process- or Activity Datafield and create a worklist filter to differentiate between priorities. The advantage is that you would have total control over the priorities, which would then be 100% customizable and would not be affected by a K2 upgrade. The choice of a repository for your priorities is up to you (string tables, flat files etc.), but I would suggest a SQL table since it is easily accessible for lookup through the SQL Event.
Regards
Emile
Hi Emile,
Thanks for your reply.
Thanks for your reply.
Reply
View our Community Site Map
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.