This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided “as is” with no warranties.
Some of your Workflows are not sending Task Email Notifications.
This only impacts some of the workflows.
This issue has not been noticed in the new HTML5 Designer, but have occurred in the Thick Client Designers (K2 Studio / K2 for Visual Studio).
This could be caused by trailing spaces in the workflow name.
To confirm if you have trailing spaces in any of your Workflow Names, please request the EWS Debug assemblies and run the following SQL Query:
USE [K2] --todo:Change to K2 Database Name
select [FullName] from [Server].[ProcSet] where substring([FullName],-1,1) = ' ';
If this returns Workflow Names, please contact K2 Support to assist in Modifying the data in the Database and to modify the Process Definition.
Do not modify any database definition or database content unless specifically instructed to do so by K2. No changes to the K2 Database definition or content are supported unless specifically instructed by K2.
Direct read access or modification of the data in the K2 database is also not supported, unless specifically instructed by K2, except for the ServerLog table where direct read access is supported.
Any modification of the K2 database or content may result in system instability or failure, therefore it is highly recommended to make backups of the K2 database prior to performing any modification, even when instructed to do so by K2.
This database schema reference is provided for informational purposes only. Note that database schemas may change between product versions, so if you have written custom queries against the K2 database, those queries may break between product versions.