Quick flow tutorial (13)-configuration file-global. config

Document directory

• Configuration File Parsing
• Whether tasks with independent permissions are used
• Use global_custom.config

Configuration File Parsing

QuickFlow uses global. config in the C: \ Program Files \ Common Files \ Microsoft Shared \ Web Server Extensions \ 12 \ TEMPLATE \ LAYOUTS \ QuickFlow directory.

File to store configuration information. The content of this file is as follows:

<? Xml version = "1.0" encoding = "UTF-8"?> <GlobalConfiguration xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns: xsd = "http://www.w3.org/2001/XMLSchema"> <CustomRoleUserProvider> QuickFlow. core. SPRoleUserProvider, QuickFlow, Version = 1.0.0.0, Culture = neutral, PublicKeyToken = ec1e0fe6e1745628 </CustomRoleUserProvider> <! -- Task proxy configuration --> <! -- <TaskDelegationProvider> QuickFlow. Core. DefaultTaskDelegationProvider, QuickFlow, Version = 1.0.0.0, Culture = neutral, PublicKeyToken = ec1e0fe6e1745628 </TaskDelegationProvider> --> <! -- If DelegationListSiteUrl is empty, system will use current site --> <! -- <DelegationListSiteUrl> http: // codeartserver: 81/sites/s1 </DelegationListSiteUrl> --> <DelegationListUrl> Lists/QuickFlowDelegation </DelegationListUrl> <! -- Enable special permissions for a task --> <EnableSpecialPermissions> false </EnableSpecialPermissions> <! -- Groups with task management permissions --> <WorkflowAdminGroup> WorkflowAdmin </WorkflowAdminGroup> <EventReceivers> <worker er Enabled = "false" Name = "Exception" Type = "QuickFlow. eventBus. predictioneventconfigurer, QuickFlow, Version = 1.0.0.0, Culture = neutral, PublicKeyToken = ec1e0fe6e1745628 "/> <runner Enabled =" true "Name =" Tracing "Type =" QuickFlow. eventBus. tracingEventReceiver, QuickFlow, Version = 1.0.0.0, Culture = neutral, PublicKeyToken = ec1e0fe6e1745628 "/> </EventReceivers> </GlobalConfiguration>

Description of each configuration node:

CustomRoleUserProviderUsed to configure a custom Role user to provide a logical class. For the custom role provider, see QuickFlow tutorial (5): RuleDriven activity, role provider customization, mail Template

TaskDelegationProviderTo configure the implementation of the task proxy. If you cancel the comments in the TaskDelegationProvider line, the default proxy is used (a list is used to store the agent information). For details about the Custom agent provider, see: task proxy of QuickFlow-TaskDelegation

TaskDelegationDelegationListSiteUrlIf the default proxy provider is used, you can specify the path of the proxy configuration list.

EnableSpecialPermissionsIf it is set to true, the permissions of each task are bound to the task operator. Otherwise, all users (with the task list operation permissions) have the permission to operate the task.

WorkflowAdminGroupWhen EnableSpecialPermissions is set to true, you can set an Administrator group with the operation permissions of the task. QuickFlow supports Reassign of the task. The administrator wants ReassignTask, you must first see this task.

EventReceiversWe recommend that you enable the default Exception processor while disable the Tracing processor by setting the Enabled attribute ). The event processor can also be customized. For details, refer to: SharePoint workflow solution QuickFlow series (6)-event bus (EventBus)

Whether tasks with independent permissions are used

The EnableSpecialPermissions configuration item is introduced because of a problem with SharePoint:

When a task with independent permissions is used (EnableSpecialPermissions = true), the following log information appears in the SharePoint log file:
ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads.

Detail: http://quickflow.codeplex.com/workitem/29739

This information does not affect the normal operation of the system. This information does not appear when the task permission directly inherits the task list. Therefore, you can configure the value of EnableSpecialPermissions according to your actual situation:
If you want to use strict permission control, you can use independent permissions. In this way, non-task operators and administrators are absolutely not authorized to view and operate tasks of other users. Alternatively, you can use a non-independent permission to filter the view. In this way, the interface is used for control. Theoretically, the performance will be better.

Use global_custom.config

A problem exists in earlier versions of QuickFlow: every time you update QuickFlow. global. the config file will be overwritten with the default version. If the global. the content of the config file, which needs to be modified every time it is updated.
Versions later than 101228 provide solutions to this problem:
After QuickFlow. wsp is installed, copy global. config and change its name to global_custom.config. Then modify the content of global_custom.config.

The internal logic of QuickFlow preferentially loads the global_custom.config file. When the global_custom.config file does not exist, global is used. config, global_custom.config will not be packaged into QuickFlow. wsp. In this way, the update solution will not be overwritten.

Note:
1) After global_custom.config or global. config is modified, iis must be restarted to take effect.
2) if you find that global. config in your environment is inconsistent with the content in this article, update it to the latest version.