applies to version: 8.1.x; author: Marcin Wiktor
WEBCON BPS offers possibility to store Active Directory organization structure in cache. Except performance issues, Active Directory cache is necessary if we want to use organization structure functionality. It allows superior to access subordinate documents and takeover their tasks in processes in which organization structure permissions are turned on. Downloading company structure occurs automatically according to schedules set by user, but there is also possibility to manually refresh cache. Cache is stored in database which gives possibility to use few predefined SQL functions, which allow to, for example check if given user is in certain SP or AD group.
1. Functionality configuration
In order to turn AD company structure cache, in BPS Studio, go to “System settings” and choose menu “Cache”.
In “Organizational structure” section we may check, when last synchronizations were performed, number of errors or warnings and check their content (details column).
In order to turn on AD Cache, click “Settings” button
Check “Synchronize organization structure from Active Directory”. Connections to server will use data of user running application pool.
If for some reasons we want to connect to server using other user account, it may be changed in “Active Directory server” menu.
It is necessary to remember that simply checking “Synchronize organization structure from Active Directory” will not make this functionality available everywhere. Additionally “Synchronize organization hierarchy from Active Directory” has to be checked for every process in which we want to use such functionality.
In next step it is necessary to configure hours in which synchronization will occur (it may take place multiple times during the day) and list of domains which will be cached. By default, current domain is set, but it is possible to add new domains.
Last thing we may configure is column mapping. It allows to save AD properties (which may be downloaded) in additional columns in table storing cache.
After saving all changes it is necessary to reload configuration or restart WEBCON WorkFlow Service.
2. Functionality example
Simple example of using cache may be displaying form fields different than basic ones (name/login/email/superior). In this example we want to display some basic information about user localization, which are stored in AD. Such data is stored in CacheOrganizationStructure table. Form field responsible for storing localization “l” may be mapped in cache configuration as COS_ExtensionLAttribute01. We will also use columns COS_AD_Company and COS_AD_StreetAddress.
select cos_login, cos_ad_company, cos_ad_streetaddress, COS_ExtensionAttribute01 FROM CacheOrganizationStructure where COS_login like '%sala.f1%'