Task List

  • 17 March 2016
  • 7 replies
  • 2 views

Badge +1

K2 Tasks not showing up in the application for new users who have granted access but it is showing for the users who had access previously


7 replies

Badge +15

Hi,

 

By tasks, are you refering to existing K2 tasks, or new K2 tasks? If you have added new users to the destination in your workflow, the existing tasks will not appear for the new destination users. Only new tasks will be sent to the new users. By new tasks, I mean new tasks from the new process instance.

Badge +1

We have a web application deployed in sharepoint that displays all the new Tasks from all processes for all users and we grant users access through AD group and Azman roles. The application then validates the user and displays all the K2 Tasks from all processes. Recently we have moved our K2 servers to a new location and since then any new users that have granted access cant see any Tasks from all processes. But it is showing the Tasks for the all the other users who have access earlier

Thanks in Advance.

Badge +1

Any help with the above?

Thanks in Advance.

Userlevel 1
Badge +8

Hi Ven,

 

Can you tell us how your desitiantion users are configured for the tasks in question? That would be the place to start to walk through what may be causing the issues you are seeing.

 

S.

Badge +1

We use Azman to grant users access to the worklistitmes. Recently we have changed the default port with which the application connects to K2 server from 5555 to other port number. Since then we are having the issues.

And also I could see that in the [K2_HostServer].[dbo].[Role]  table we have those roles that are configured in Azman as smart objects but the role data is still connecting to the server using the old port number 5555. Do you think this might be the issue?

Userlevel 1
Badge +8

When you say you changed the port number the application uses are you saying you changed K2's default port number or the number in your application? K2's standard ports are 5555 for every but workflow which is 5252.

 

S.

Badge +1

We have changed the [K2HOSTCONNECTIONSTRING]  from 5555 to 6666 and the [K2WFCONNECTIONSTRING] is still 5252

Reply