Content Management and Capture

We are deploying a configuration with 400 groups (departments).
Each group has its own batches of documents.
It is expected that each user should only be able to access (datacap navigator) batches from his own department.
With the available configuration options and documentation we are not being able to implement this security requirement.

What additional guidelines can read to solve the issue ?

Regards,
Bruno

------------------------------
Bruno Ferreira
------------------------------

400 groups is too much.  Just logon will take forever to phrase through the user in what group.   You can see the amount of time it check the user in which group just for logon.

Let said you are able to define the right template to your Ldap, LLLDAP, or ASDI to locate the user  and that you are okay with the speed for logon - the next challenge is to look for the workflow and task for certain user.   Best option is to route the batch to that group or user in that group.  This is done by routing the batch to certain user or group. 

Also you don't want to give all your user access to job monitor as they will run query or just the refresh of job monitor will impact the entire system from tm server to the db performance. 

Might I recommend engaging your sales rep. to reach out to our lab services team for assistant.  Lab advocate are pre paid services that you can render to help with architecture your environment.

We are deploying a configuration with 400 groups (departments).
Each group has its own batches of documents.
It is expected that each user should only be able to access (datacap navigator) batches from his own department.
With the available configuration options and documentation we are not being able to implement this security requirement.

What additional guidelines can read to solve the issue ?

Regards,
Bruno

------------------------------
Bruno Ferreira
------------------------------

Hi there,

thanks for the reply.

Ok I didn't know that 400 groups could be a problem, but I will try to populate that amount of groups to check the performance.

About assigning groups to the batch, you are saying first add weight to the group and the execute an update to that batch with the gr_key of the tmgroup (right shift 8 bits)?

example:
UPDATE tmbatch set pb_key=1 where pb_batch='%s'

And if we need to have more than on group?

400 groups is too much.  Just logon will take forever to phrase through the user in what group.   You can see the amount of time it check the user in which group just for logon.

Let said you are able to define the right template to your Ldap, LLLDAP, or ASDI to locate the user  and that you are okay with the speed for logon - the next challenge is to look for the workflow and task for certain user.   Best option is to route the batch to that group or user in that group.  This is done by routing the batch to certain user or group. 

Also you don't want to give all your user access to job monitor as they will run query or just the refresh of job monitor will impact the entire system from tm server to the db performance. 

Might I recommend engaging your sales rep. to reach out to our lab services team for assistant.  Lab advocate are pre paid services that you can render to help with architecture your environment.

We are deploying a configuration with 400 groups (departments).
Each group has its own batches of documents.
It is expected that each user should only be able to access (datacap navigator) batches from his own department.
With the available configuration options and documentation we are not being able to implement this security requirement.

What additional guidelines can read to solve the issue ?

Regards,
Bruno

------------------------------
Bruno Ferreira
------------------------------