DocAve Governance Automation - AvePoint · About DocAve Governance Automation ... Changing the...

User Guide

for Administrators

DocAve®

Governance Automation

Service Pack 5

Revision K Issued August 2014

Table of Contents

About DocAve Governance Automation ..................................................................................................... 10

Submitting Documentation Feedback to AvePoint .................................................................................... 11

Understanding Governance Automation Terminology............................................................................... 12

Updating Previous Versions of Governance Automation ........................................................................... 13

Updating Your Governance Automation Instance .................................................................................. 13

Reinstalling Governance Automation Web Part and/or Governance Automation Site Directory Web Part .......................................................................................................................................................... 13

Planning Your Governance Automation Installation .................................................................................. 15

Where should I install the Governance Automation Manager? ............................................................. 15

How many DocAve/Governance Automation servers do I need? .......................................................... 15

Which DocAve modules are required for Governance Automation? ..................................................... 15

What about SQL Server? ......................................................................................................................... 15

Minimum Server (Hardware) Requirements .......................................................................................... 16

DocAve 6 and Governance Automation Services on Same Server ..................................................... 16

Dedicated, Single-Instance SQL Server ............................................................................................... 16

Server Requirements for DocAve Agents ............................................................................................ 16

Supported Software ................................................................................................................................ 17

Required Permissions for Governance Automation Service Accounts ................................................... 18

Required Services on DocAve 6/Governance Automation Server .......................................................... 19

Ports Used by Governance Automation ................................................................................................. 20

Installation of Governance Automation ..................................................................................................... 21

Updating Your DocAve Version ............................................................................................................... 21

Installing Governance Automation ......................................................................................................... 21

Installing DocAve Update for Governance Automation ..................................................................... 21

Installing Governance Automation via the Installation Wizard .......................................................... 22

Unattended Installation .......................................................................................................................... 26

Generating the Answer File ................................................................................................................ 26

Importing the UnattendedInstallation.dll File .................................................................................... 30

Installation Commands ....................................................................................................................... 30

Optional Governance Automation Installations ......................................................................................... 33

2

DocAve Governance Automation

Installing the DocAve Governance Automation Web Part ..................................................................... 33

Deploying the DocAve Governance Automation Web Part Solution .................................................. 33

Inserting the Web Part into a SharePoint Site .................................................................................... 35

Installing DocAve Governance Automation Site Directory Web Part ..................................................... 37

Deploying the DocAve Governance Automation Site Directory Web Part Solution ........................... 37

Inserting the Web Part into a SharePoint Site .................................................................................... 39

Installing the Governance Automation App ........................................................................................... 41

Governance Automation App Pre-Installation Checklist .................................................................... 41

Preparing the Environment to Host Apps ........................................................................................... 41

Modifying App File .............................................................................................................................. 44

Uploading Governance Automation App to App Catalog ................................................................... 45

Configuring Governance Automation Web Site Authentication ........................................................ 45

Adding Governance Automation App to a SharePoint Site ................................................................ 46

Inserting Governance Automation App Part....................................................................................... 47

Deploying the Governance Automation Policy Bar Solution .................................................................. 48

Post-installation Procedures ....................................................................................................................... 49

Allowing Full Control Permission to the DocAve Private Key ................................................................. 49

Enabling the Service Account to Listen to the Governance Automation Workflow Service Port .......... 49

Changing the Certificate in IIS Manager ................................................................................................. 50

Applying User-Defined Certificates ......................................................................................................... 51

Applying a Governance Automation License .......................................................................................... 52

Logging into Governance Automation for the First Time ....................................................................... 52

Configuring Authentication Types .......................................................................................................... 52

Configuring AD Authentication ........................................................................................................... 52

Setting Windows Authentication as the Default Login Method ......................................................... 52

Configuring E-mail Notification Settings ................................................................................................. 54

Registering SharePoint Online Admin Centers/Site Collections ............................................................. 54

Configuring Language, Time Zone, Date/Time Format, and Office 365 Account Settings ..................... 54

Getting Started with Governance Automation ........................................................................................... 56

Configuring Account Manager ................................................................................................................ 56

Managing Governance Automation Groups ....................................................................................... 56

Managing Administrator Accounts ..................................................................................................... 57

3


Managing Business Users .................................................................................................................... 58

Creating New User Groups.................................................................................................................. 58

Adding or Removing Users .................................................................................................................. 58

Enabling a User Profile Service ............................................................................................................... 59

Retrieving User Information from a Custom Database ...................................................................... 59

Configuring Departments........................................................................................................................ 60

Retrieving Department Information from a SharePoint User Profile Service..................................... 60

Manually Adding New Departments ................................................................................................... 61

Configuring Approval Process ................................................................................................................. 61

Creating or Editing Approval Processes .............................................................................................. 62

Building Customized Approval Processes ........................................................................................... 68

Configuring Policies ................................................................................................................................. 69

Creating or Editing Site Collection Policies ......................................................................................... 70

Creating or Editing Content Database Policies ................................................................................... 81

Configuring Services ................................................................................................................................ 82

Create Site Collection Service ............................................................................................................. 83

Create Site Service .............................................................................................................................. 94

Create My Site Service ...................................................................................................................... 103

Create Library/List Service ................................................................................................................ 108

Site Collection Lifecycle Management Service ................................................................................. 114

Site Lifecycle Management Service .................................................................................................. 118

Clone or Transfer User Permission Service ....................................................................................... 122

Change Site Collection Contact or Administrator Service ................................................................. 127

Change Site Contact Service ............................................................................................................. 131

Content Move Service ....................................................................................................................... 134

Change Site Collection Settings Service ............................................................................................ 144

Change Site Metadata Service .......................................................................................................... 148

Change Library/List Settings Service ................................................................................................. 151

Grant Permissions Service................................................................................................................. 154

Remove Permissions Service............................................................................................................. 160

Custom Service .................................................................................................................................. 163

Additional Governance Automation Configurations ................................................................................ 167

4


Importing Existing Site Collections and Sites ........................................................................................ 167

Creating an Export Plan ..................................................................................................................... 167

Modifying the Scan Result File .......................................................................................................... 168

Importing the Configured Scan Result File ....................................................................................... 169

Validating Data after Importing a Scan File ...................................................................................... 170

Configuring Metadata ........................................................................................................................... 172

Searching and Filtering Metadata ..................................................................................................... 172

Creating or Editing Metadata ............................................................................................................ 173

Deleting Metadata ............................................................................................................................ 175

Configuring Questionnaires .................................................................................................................. 175

Displaying and Searching Questionnaires ......................................................................................... 175

Creating or Editing Questionnaires ................................................................................................... 175

Activating, Deactivating, and Deleting Questionnaires .................................................................... 177

Configuring E-mail Templates ............................................................................................................... 177

Searching and Filtering E-mail Templates ......................................................................................... 177

Creating or Editing E-mail Templates ................................................................................................ 177

Deleting E-mail Templates ................................................................................................................ 178

Configuring the Execution Schedule ..................................................................................................... 178

Displaying and Searching Execution Schedules ................................................................................ 178

Creating or Editing Execution Schedules .......................................................................................... 178

Deleting Execution Schedules ........................................................................................................... 179

Configuring Request Access Settings .................................................................................................... 179

Preparing SharePoint ........................................................................................................................ 179

Configuring Request Access Settings ................................................................................................ 181

Restarting IIS (for SharePoint 2010 Only) ......................................................................................... 182

Exporting and Importing Configuration Data........................................................................................ 182

Exporting Configuration Data ........................................................................................................... 182

Importing Configuration Data ........................................................................................................... 183

Configuring External Workflow Integration Settings ............................................................................ 183

Starting Microsoft SharePoint Foundation Sandboxed Code Service ............................................... 184

Displaying and Searching External Workflow Integration Profiles ................................................... 184

Creating or Editing External Workflow Integration Profiles ............................................................. 184

5


Deleting External Workflow Integration Profiles .............................................................................. 185

Creating External Workflows in SharePoint ...................................................................................... 185

Hiding or Revealing Sections to Business Users .................................................................................... 190

Configuring the Report Export Location ............................................................................................... 191

Searching Report Export Locations ................................................................................................... 191

Creating or Editing Report Export Locations ..................................................................................... 191

Deleting Report Export Locations ..................................................................................................... 191

Configuring SharePoint Permission Levels ............................................................................................ 192

Displaying and Searching Permission Levels ..................................................................................... 192

Creating or Editing Permission Levels ............................................................................................... 192

Deleting Permission Levels ............................................................................................................... 192

Configuring Administrator Notifications ............................................................................................... 192

Configuring the Timer Service ............................................................................................................... 193

Configuring Session Timeout Settings................................................................................................... 195

Configuring Category Management ...................................................................................................... 195

Displaying and Searching Categories ................................................................................................ 195

Creating or Editing Categories .......................................................................................................... 195

Deleting Categories ........................................................................................................................... 195

Synchronizing Authentication Configuration Changes to Governance Automation ............................ 196

Modifying Governance Automation Configuration Settings after Installation ......................................... 197

Re-registering Governance Automation after Uninstalling DocAve ..................................................... 197

Monitoring and Reporting ........................................................................................................................ 198

Monitoring All Requests ....................................................................................................................... 198

Monitoring All Tasks ............................................................................................................................. 199

Create, Archive, Delete, Extend Site Collection, and Create Site Tasks ............................................ 199

Site Collection Lifecycle Management Tasks .................................................................................... 200

Site Lifecycle Management Tasks ..................................................................................................... 200

User Permission and Manual Archive Tasks ..................................................................................... 201

Change Actions, Content Move, and Create Tasks ........................................................................... 202

Permission Recertification Tasks....................................................................................................... 202

Quota Threshold Tasks ...................................................................................................................... 204

Content Database Policy Threshold Warning Task ........................................................................... 204

6


Error Tasks ......................................................................................................................................... 205

Audit Reports ........................................................................................................................................ 205

User Activity Report .......................................................................................................................... 206

Service Request Report ..................................................................................................................... 207

Approval Process Report ................................................................................................................... 208

Administration Reports ......................................................................................................................... 209

Site Collection Report ....................................................................................................................... 209

Site Report ........................................................................................................................................ 211

Content Database Report ................................................................................................................. 212

Public Site Collection Directory ............................................................................................................. 213

Managing Public Site Collection Directory Reports .......................................................................... 213

Filtering Public Site Collection Directory Reports ............................................................................. 213

Exporting Public Site Collection Directory Reports ........................................................................... 214

My Sites ................................................................................................................................................. 214

Managing My Sites Reports .............................................................................................................. 214

Filtering My Sites Reports ................................................................................................................. 215

Exporting My Sites Reports ............................................................................................................... 215

Working with Requests and Tasks ............................................................................................................ 216

Starting a Request ................................................................................................................................. 216

Viewing My Requests ............................................................................................................................ 217

Submitted Requests .......................................................................................................................... 217

Saved Requests ................................................................................................................................. 218

Viewing My Tasks .................................................................................................................................. 219

Create, Archive, Delete, Extend Site Collection, and Create Site Tasks ............................................ 219

Site Collection Lifecycle Management Tasks .................................................................................... 220

Site Lifecycle Management Tasks ..................................................................................................... 220

User Permission and Manual Archive Tasks ..................................................................................... 221

Change Actions, Content Move, and Create Tasks ........................................................................... 222

Permission Recertification Tasks....................................................................................................... 222

Quota Threshold Tasks ...................................................................................................................... 224

Content Database Policy Threshold Warning Task ........................................................................... 224

Error Tasks ......................................................................................................................................... 225

7


Changing Branding Elements in Governance Automation ....................................................................... 226

Changing the Title Style ........................................................................................................................ 228

Changing the Logo and Logo URL.......................................................................................................... 230

Changing the Theme Color.................................................................................................................... 232

Changing the Navigation Bar Color ....................................................................................................... 236

Changing the Table Style ....................................................................................................................... 239

Changing the System Name Image on Login Page ................................................................................ 241

Changing the System Logo Image on Login Page .................................................................................. 243

Changing the About Background Image ............................................................................................... 245

Changing the Governance Automation App Logo ................................................................................ 247

Changing the Site Information Card Logo ............................................................................................. 247

Supporting Custom CSS Files................................................................................................................. 247

Governance Automation Web API SDK ..................................................................................................... 248

Getting Started ...................................................................................................................................... 248

Environment Requirement ............................................................................................................... 248

Required DLL File............................................................................................................................... 248

Supported Features in Governance Automation Web API SDK ............................................................ 248

Implementing Governance Automation API for Create Site Collection Request ................................. 249

Logging into Governance Automation .............................................................................................. 249

Managing Create Site Collection Requests ....................................................................................... 250

Appendix A: Configuring a Filter Policy ..................................................................................................... 254

Configuring Filter Policy to Use DocAve Granular Backup and Restore ............................................... 254

Configuring Filter Policy to Use Audit Controller in DocAve Report Center ......................................... 255

Configuring Filter Policy to Use Dead Account Cleaner in DocAve Administrator ............................... 255

Configuring Filter Policy to Use DocAve Deployment Manager ........................................................... 256

Appendix B: Configuring DocAve Archiver Profiles ................................................................................... 258

Appendix C: Configuring DocAve Deployment Manager Plans ................................................................ 260

Creating a Deployment Mapping .......................................................................................................... 260

Creating a Deployment Plan ................................................................................................................. 262

Appendix D: Configuring a Policy Enforcer Profile .................................................................................... 263

Configuring a Source Collection Policy ................................................................................................. 263

Creating a Policy Enforcer Profile ......................................................................................................... 264

8


Notices and Copyright Information .......................................................................................................... 265

9


About DocAve Governance Automation Traditionally, administrators create SharePoint objects or manage their data in SharePoint manually by following a series of requirements. The number of human interactions that occur in business processes can inhibit speed and the quality of decisions.

Governance Automation provides ways to create and govern your SharePoint 2010 and SharePoint 2013 objects automatically, both SharePoint on-premises and SharePoint Online, by submitting rich and customizable predefined service requests which can trigger corresponding approval processes and policies to accomplish the processes. This automation results in more speed, overall effectiveness of the interactions and often a reduction in errors.

This documentation is for administrators to leverage Governance Automation for the automated, end-to-end service and information management; if you are a business user of Governance Automation, refer to the DocAve Governance Automation User Guide for Business Users.

10


http://www.avepoint.com/assets/pdf/sharepoint_user_guides/DocAve_Governance_Automation_Business_User_User_Guide.pdf

Submitting Documentation Feedback to AvePoint AvePoint encourages customers to provide feedback regarding our product documentation. Click the following URL to access the Submit Your Feedback form on our Web site:

http://www.avepoint.com/resources/documentation-feedback/?flush=1

11


http://www.avepoint.com/resources/documentation-feedback?flush=1

Understanding Governance Automation Terminology If you are new to Governance Automation, it may be helpful to review the Key Terms list to familiarize yourself with terms such as “service”, “policy”, and “approval process”, which will be used throughout this user guide.

Once you have familiarized yourself with Governance Automation terminology, it is important to understand how the different features and functionalities work together. This knowledge is essential to properly configure the software for your organization.

In Governance Automation, administrators can set up services that perform SharePoint or DocAve operations. These services can be made available to only the relevant departments/purposes so that they can be customized to be most effective for each department/purpose. A Service may have a policy associated with it so that if your organization has specific rules on certain SharePoint operations, you can ensure that all services with the same associated policy will be compliant to your organization’s standards. Services will also have at least one approval process configured so that when a user submits a request for a specific service, the appropriate parties (such as the user’s manager) are notified and can provide the necessary approval. Once the service request has been fully approved, Governance Automation performs the SharePoint and/or DocAve processes according to the customized settings configured for that service.

12


http://www.avepoint.com/assets/pdf/sharepoint_user_guides/Governance_Automation_Key_Terms.pdf

Updating Previous Versions of Governance Automation Before you update to Governance Automation Service Pack 5, be sure that you have followed the instructions in Updating Your DocAve Version.

After updating DocAve, proceed with the Governance Automation update procedure described below.

*Note: If you used the Governance Automation Web Part and/or the Governance Automation Site Directory Web Part in Governance Automation Service Pack 4, you must uninstall and then reinstall the Web parts after you update your Governance Automation instance to Service Pack 5.

Updating Your Governance Automation Instance This procedure assumes that you have met the conditions described in Updating Your DocAve Version and that you have already downloaded and extracted the DocAve_Governance_Automation_SP5_UpgradePackage.zip file.

Complete the following steps to update your Governance Automation instance:

1. Extract the DocAve_Governance_Automation_SP5_UpgradePackage.zip file. You will see the following ZIP files in the DocAve_Governance_Automation_SP5_UpgradePackage folder: DocAve_Update_for_Governance_Automation_1.5.zip and DocAve_Governance_Automation_SP5_UpgradePackage.zip.

2. In the DocAve Control Panel > Update Manager, install the DocAve_Update_for_Governance_Automation_1.5.zip update. This update ensures proper communication between DocAve and Governance Automation. For more information about how to install this update, refer to Installing DocAve Update for Governance Automation.

3. In the DocAve Control Panel > Update Manager, install DocAve_Governance_Automation_SP5_UpgradePackage.zip update in the Governance Automation tab to update Governance Automation on your selected servers.

4. Verify that the DocAve Manager and Agent update was applied successfully by navigating to Control Panel > Update Manager > View History and checking the Version and Date columns of the newly installed update.

Reinstalling Governance Automation Web Part and/or Governance Automation Site Directory Web Part To reinstall the Web parts after a Governance Automation update, uninstall the previously installed Web parts first by completing the following steps:

1. Navigate to SharePoint Central Administration > System Settings > Farm Management, and then click Manage farm solutions.

2. Click gawebpart.wsp or gasubsitedirectorywebpart.wsp, and then click Retract Solution.

13


3. Click Back to Solutions and the status of the previously selected solution is Not Deployed.

4. Click the solution, and then click Remove Solution. A confirmation window appears.

5. Click OK to remove the solution.

6. After uninstalling the Web parts, reinstall them. For more information, refer to Installing the DocAve Governance Automation Web Part and Installing DocAve Governance Automation Site Directory Web Part.

14


Planning Your Governance Automation Installation Governance Automation provides for several installation scenarios that depend upon the size of your organization. This guide provides both minimum and recommended specifications and configurations for small- and large-scale deployments. Before proceeding, note the following:

• To install Governance Automation, DocAve 6 (Manager and Agents) must be installed first. For more information on installing DocAve 6, refer to the DocAve 6 Installation Guide.

• Ensure that your versions of DocAve 6 and Governance Automation are compatible. Refer to the AvePoint KB article Governance Automation, DocAve, and SnapManager for SharePoint Support Matrix for more information.

Where should I install the Governance Automation Manager? To minimize network calls between DocAve 6 and Governance Automation, the Governance Automation Manager should always be installed on the same server as the DocAve Control Service, Media Service, and Report Service (if applicable). Note that this may require you to increase your server (hardware) specifications, so carefully review the information in Minimum Server (Hardware) Requirements.

How many DocAve/Governance Automation servers do I need? Governance Automation is an end-user-facing application, so for high availability and load balancing purposes, you should always plan for at least two Governance Automation servers in your production environment.

However, larger environments should plan on additional Governance Automation servers. As a general rule, each DocAve/Governance Automation server can handle about 300 concurrent requests. AvePoint’s recommendation is that for environments with more than 200,000 users, three (3) DocAve/Governance Automation should be used.

Which DocAve modules are required for Governance Automation? At a minimum, you must be running DocAve 6 Administrator to use Governance Automation.

What about SQL Server? For all Governance Automation installations, AvePoint recommends a separate dedicated, single-instance SQL Database. Note that SQL Server clustering is not mandatory but is recommended for high availability purposes.

15


http://www.avepoint.com/assets/pdf/sharepoint_user_guides/DocAve_6_Installation_Guide_SP4.pdf

http://www.docave.com/KB/Lists/KB/DispErrorArticle.aspx?ID=850


Minimum Server (Hardware) Requirements The following specifications are the minimum required. AvePoint recommends exceeding these values for improved Governance Automation performance.

DocAve 6 and Governance Automation Services on Same Server Component Minimum Specification Number of CPU Cores 64-Bit, 4 Cores Physical Memory 16 GB (Available) Available Disk Space 50 GB or above

Dedicated, Single-Instance SQL Server Component Minimum Specification Number of CPU Cores 64-Bit, 4 Cores Physical Memory 16 GB (Available) Available Disk Space 60 GB or above

Server Requirements for DocAve Agents For some operations, Governance Automation leverages DocAve Agents. To account for this additional load, ensure that your Agent servers meet or exceed the following specifications.

Component Minimum Specification Number of CPU Cores 64-Bit, 4 Cores Physical Memory 4 GB (Available/dedicated for DocAve Agent) Available Disk Space 50 GB or above

16


Supported Software Component Supported Operating System Windows Server 2008

Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Windows 7

SharePoint Versions Microsoft SharePoint Server/Foundation 2010 (up to and including Service Pack 2) Microsoft SharePoint Server/Foundation 2013 (up to and including Service Pack 1) *Note: The Governance Automation App is only supported on Microsoft SharePoint Server/Foundation 2013 (up to and including Service Pack 1).

Web Browsers Internet Explorer 8 (Does not support the Questionnaire feature) Internet Explorer 9 and 10 Google Chrome

Compatible DocAve Products Administrator (required for Governance Automation) Content Manager Deployment Manager Granular Backup and Restore Report Center Scheduled Storage Manager Connector Archiver Vault File Share Navigator

SQL Server Version Microsoft SQL Server 2008 Microsoft SQL Server 2008 R2 Microsoft SQL Server 2012 Microsoft SQL Server 2014*

.Net Framework Version .NET Framework 4.5 or above PowerShell Version PowerShell 2.0 or above

*SQL Server 2014 is fully supported on Governance Automation SP5 and DocAve 6 SP4 CU1 and later versions. However, DocAve 6 SP4 support for SQL Server is limited. Please refer to the DocAve 6 SP4 Installation Guide on http://www.avepoint.com/resources/user-guides/ for details.

17


http://www.avepoint.com/resources/user-guides/

Required Permissions for Governance Automation Service Accounts In most cases, organizations generally use one service account to achieve permissions for Governance Automation services and the application pool. If using one service account for all Governance Automation services and the application pool, permissions for this account should be as follows:

• The database role of DB_Owner for Governance Automation Configuration Database and Governance Automation Audit Database.

• The Full Control permission to the private key of DocAve. For instructions on how to grant these permissions, refer to Allowing Full Control Permission to the DocAve Private Key.

• Permission for the service account to listen to the Governance Automation Workflow Service port. For more information, refer to Enabling the Service Account to Listen to the Governance Automation Workflow Service Port.

• The Read and Write permission to the GovernanceAutomation folder in Governance Automation installation directory …\AvePoint\GovernanceAutomation.

• The database role of DB_DataReader and DB_DataWriter for DocAve Archiver Database (if manual archiving will be used).

Below is a breakdown of permissions for each Governance Automation service and the application pool:

• Service account for Governance Automation Workflow Service:

o The database role of DB_Owner for Governance Automation Configuration Database and Governance Automation Audit Database.

o The Full Control permission to the private key of DocAve. For instructions on how to grant these permissions, refer to Allowing Full Control Permission to the DocAve Private Key.

o Permission for the service account to listen to the Governance Automation Workflow Service port. For more information, refer to Enabling the Service Account to Listen to the Governance Automation Workflow Service Port.

o The Read and Write permission to the GovernanceAutomation folder in Governance Automation installation directory …\AvePoint\GovernanceAutomation.

o The database role of DB_DataReader and DB_DataWriter for DocAve Archiver Database (if manual archiving will be used).

• Service account for Governance Automation Timer Service:


18



o The database role of DB_DataReader and DB_DataWriter for DocAve Archiver Database (if manual archiving will be used).

• Service account for Application Pool:



Required Services on DocAve 6/Governance Automation Server .Net Framework Features The Windows features, including WCF Activation,

HTTP Activation, and Non-HTTP Activation must be installed.

Net.Tcp Port Sharing Service Net.Tcp Port Sharing Service is started. Windows Process Activation Service • Windows Process Activation Service is

started.

• Process Model, .NET Environment, and Configuration APIs are installed.

World Wide Web Publishing Service World Wide Web Publishing Service is started. Web Server(IIS) Role Windows features installed:

• Web Server

• Common HTTP Features (Static Content, Default Document)

• Application Development (ASP.NET, .NET Extensibility, ISAPI Extensions and ISAPI Filters)

• Management Tools (IIS Management Console, IIS 6 Management Compatibility and IIS 6 Metabase Compatibility)

19


Ports Used by Governance Automation Refer to the table below for the ports that are used by Governance Automation:

Port Usage Enabled By 15000 Web site Port – Used to access

Governance Automation Web site. Governance Automation Web site.

6008 Workflow Service Port – Used to host Governance Automation Workflow Service.

Windows Communication Foundation Service hosted by Governance Automation Workflow Service.

*Note: Port 15000 requires HTTPS.

20


Installation of Governance Automation Now that you have determined how you will configure Governance Automation in your environment, you are ready to install the application. Follow each step below in the order provided.

1. Updating Your DocAve Version

2. Installing DocAve Update for Governance Automation

3. Installing Governance Automation via the Installation Wizard

Updating Your DocAve Version At a minimum, DocAve 6 Service Pack 4 is required to work with Governance Automation Service Pack 5. If necessary, update your DocAve instance to DocAve 6 Service Pack 4 or later before proceeding with your Governance Automation update. For details on how to update your DocAve instance, refer to the DocAve 6 Control Panel Reference Guide.

For a compatibility matrix of Governance Automation and DocAve, refer to the AvePoint KB article Governance Automation, DocAve, and SnapManager for SharePoint Support Matrix.

After updating DocAve to the minimum required version, you can proceed with your Governance Automation installation.

Installing Governance Automation Before installing Governance Automation, ensure that your version of DocAve is compatible with Governance Automation. See Updating Your DocAve Version for more information. After this is complete, proceed with the instructions in the sections below.

*Note: You can automate your Governance Automation deployment using the unattended installation feature of Governance Automation. For instructions on how to perform an unattended installation, refer to Unattended Installation.

Installing DocAve Update for Governance Automation To ensure proper communication between DocAve and Governance Automation, a DocAve update specific to Governance Automation must be manually installed.

In the Governance Automation installation package ZIP file, you will see the DocAve_Update_for_Governance_Automation_1.5.zip file. Follow the instructions below to install the DocAve update:

1. Log into the DocAve 6 Manager and navigate to Control Panel > Update Manager.

21


http://www.avepoint.com/assets/pdf/sharepoint_user_guides/Control_Panel_Reference_Guide.pdf


2. On the Manage Updates interface, click Browse. Find and load the DocAve_Update_for_Governance_Automation_1.5.zip file into DocAve Manager.

3. Click Install in the Status column. In the Server Selection pop-up window, all available Manager services are shown in the Manager tab and all available farms are shown in the Agent tab.

4. On the Manager tab, select the Install the update for all the managers below checkbox. The update will be installed on all of the Manager services.

5. On the Agent tab, select the farms whose Agent services you want to update by selecting the corresponding checkboxes. The update will be installed on the selected Agents.

6. Click Install. The progress displays in the Status column. After the installation completes, a message appears indicating that the installation was successful.

7. Click Finish.

8. To verify that the update was successful, navigate to Control Panel > Update Manager > View History and check the Version column of the newly installed update.

Installing Governance Automation via the Installation Wizard After installing the DocAve update, complete the following steps to configure Governance Automation Installation Wizard:

1. Locate the DocAve Governance Automation directory. Double-click the Setup.exe file.

2. A window appears to remind you to install the DocAve update. This update can be installed before or after your Governance Automation installation. For more information on installing the update, refer to Installing DocAve Update for Governance Automation. Click OK to proceed with the installation.

3. In the Welcome screen, choose to install DocAve Governance Automation in English, Japanese or French by selecting the language pack from the drop-down menu, then click Next.

4. Enter your Name and Organization into the provided field. Click Next.

5. Carefully review the Governance Automation License Agreement. After you have read the agreement, check the I accept the terms in the license agreement checkbox, and click Next.

6. By default, Governance Automation will be installed in C:\Program Files\AvePoint. To change this location, click Browse. Click Next.

7. Set up the Service Configuration:

a. DocAve Control Service Address ‒ Configure the DocAve Control Service Host and the DocAve Control Service Port.

• DocAve Control Service Host ‒ Enter the hostname or IP address of the machine where DocAve Control Service is installed.

• DocAve Control Service Port ‒ Enter the DocAve Control Service port number used to communicate with DocAve Control Service. The default port number is 14000.

22


b. Governance Automation Host – Enter the hostname or IP address of the machine where Governance Automation will be installed.

c. IIS Web Site Settings ‒ Configure the IIS Web site settings for the Governance Automation. You can select to use an existing IIS Web site or create a new IIS Web site. The IIS Web site is used to access Governance Automation.

• Use an existing IIS web site ‒ Select an existing IIS Web site from the drop-down list, and if necessary, you can adjust the Web Site Port used to access the Governance Automation.

• Create a new IIS web site ‒ Enter the Web site name for creating a new IIS Web site for Governance Automation. The default Web Site Port number used to access Governance Automation is 15000, you do not need to change it unless a known port conflict exists.

• Web Site Port ‒ Enter the port number for Governance Automation communication. The default port number is 15000.

d. Application Pool Settings ‒ Configure the IIS application pool that will collect and manage requests that are sent to the Web site configured in the step above. You can select an existing application pool or create a new application pool.

• Use an existing application pool ‒ Select an existing application pool from the drop-down list. If you choose to use an existing application pool, the Application Pool Account settings are greyed out and cannot be changed.

• Create a new application pool ‒ Enter the application pool name and application pool account settings to create a new IIS application pool for the corresponding Web site. In the Application Pool Account field, enter the username and password for the account.

*Note: For the required permissions of the application pool account, refer to Required Permissions for Governance Automation Service Accounts.

e. Governance Automation Workflow Service – The Governance Automation Workflow service is a local service that needs to be manually started before Governance Automation can be used. Configure the Workflow Service Port and Service Account.

• Workflow Service Port – Enter the Workflow Service port number used to communicate with Workflow Service. The default port number is 6008.

• Service Account – Enter the username and password for the account that the Governance Automation Workflow service can use to log on.

*Note: For required permissions of the service account, refer to Required Permissions for Governance Automation Service Accounts.

f. Governance Automation Timer Service – The Governance Automation Timer service is a local service that needs to be manually started before Governance Automation can be used. Configure the Service Account for Timer Service.

• Service Account – Enter the username and corresponding password for the account that the Governance Automation Timer service can use to log on.

23


*Note: For required permissions of the service account, refer to Required Permissions for Governance Automation Service Accounts.

8. Click Next to continue to configure the authentications for Governance Automation.

9. Set up the Authentication Configuration:

• Authentication ‒ Enter the DocAve Manager Passphrase to ensure the communication with DocAve. If you forget the passphrase, you can view it by navigating to DocAve > Control Panel > General System Settings > System Options > Security Settings.

• DocAve Administration Account Settings ‒ Enter the DocAve Manager account by which the DocAve activities are performed. The user accounts entered here must be local users with full control permissions of DocAve.

*Note: To change the DocAve account information after Governance Automation installation is complete, use the Governance Automation Configuration Tool.

10. Click Next.

11. Governance Automation will perform a brief pre-scan of the environment to ensure that all hardware and configurations meet the requirements. The status for each rule will be listed under the Status column heading. Click the hyperlink in the Status column, the detailed information about the scan result will be listed in the popup window.

12. Click Detail and you can view the detailed requirements for all of the rules.

13. Click Next to start the configurations of databases for Governance Automation.

14. Set up the Configuration Database Settings:

a. Database Settings ‒ Select a Configuration Database for Governance Automation to store its settings and configurations.

• Database Server ‒ Enter the server name or IP address of the database server you wish to connect to.

• Governance Automation Database Name ‒ Enter a name for Governance Automation Configuration Database. If the database does not exist, it will be automatically created in the entered database server.

b. Database Credentials ‒ Select Windows Authentication or SQL Authentication for the Governance Automation Configuration Database is to be used when connecting to the SQL server.

• Windows Authentication ‒ Use this method when you want the user identity to be confirmed by Windows.

• SQL Authentication ‒ SQL server will confirm the user identity itself according to the entered account and password.

c. Advanced Database Settings ‒ Enter a failover database server name to set it as a hot standby database server for Governance Automation Configuration Database to maximize the database availability and minimize the downtime. You must set up database mirroring in SQL server before configuring the Advanced Database Settings to ensure the availability of the failover database server.

24


15. Click Next.

16. Set up the Audit Database Settings to configure an Audit Database for Governance Automation to store the auditing information, data and reports.

a. To use the same database settings including Database Server, Database Credentials, and Advanced Database Settings as Governance Automation Configuration Database’s by selecting the Use the previous database settings checkbox, and enter a name for the Audit Database for Governance Automation. If the database does not exist, it will be automatically created in the entered database server.

b. To set up a separate database as an Audit Database for Governance Automation by deselecting the Use the previous database settings checkbox, and entering the following information.


• Audit Database Name ‒ Enter a name for Governance Automation Audit Database. If the database does not exist, it will be automatically created in the entered database server.

• Database Credentials ‒ Select Windows Authentication or SQL Authentication for the Governance Automation Audit Database is to be used when connecting to the SQL server.

o Windows Authentication ‒ Use this method when you want the user identity to be confirmed by Windows.

o SQL Authentication ‒ SQL server will confirm the user identity itself according to the entered account and password.

• Advanced Database Settings ‒ Enter a failover database server name to set it as a hot standby database server for Governance Automation Audit Database to maximize the database availability and minimize the downtime. You must set up database mirroring in SQL server before configuring the Advanced Database Settings to ensure the availability of the failover database server.

17. Click Next.

18. Set up the Advanced Configuration to select a Secure Socket Layer (SSL) certificate that is used for the communication between Governance Automation and DocAve.

• Built-in Certificate ‒ Use the certificate provided by Governance Automation. No additional configuration is necessary.

• User-defined Certificate ‒ Governance Automation accepts user-defined certificates, but AvePoint cannot guarantee full Governance Automation functionality if a user-defined certificate is used. AvePoint strongly recommends you use the provided built-in certificate.

*Note: If selecting a user-defined certificate, you must manually copy two configuration files to Governance Automation directories after the installation completes. For more information, refer to Applying User-Defined Certificates.

25


19. In the Ready to Install DocAve Governance Automation page, all of the information configured in the previous steps is listed. Click Install to begin the installation. Click Back to return to the previous interface. Click Cancel to exit the installation wizard without saving any of the configurations.

20. Once Governance Automation is successfully installed, you have the option to Register Governance Automation to Customer Experience Improvement Program to enhance technical support in the Installation completed interface. Then, click Finish to exit the installation wizard.

Unattended Installation Governance Automation can be installed using the unattended installation method. Unattended installation installs Governance Automation using the UnattendedInstallation.dll file, a generated answer file, and unattended installation commands. The answer file is a script that provides answers to questions or options presented during a Governance Automation installation. The answer file will be used when executing the unattended installation commands.

Generating the Answer File Before performing an unattended installation, an answer file must be generated by Governance Automation Setup Manager. The answer file provides the configuration information required for the unattended installation.

1. In the Governance Automation package, double-click the UnattendedInstall folder.

2. Double-click the SetupManager folder to open it.

3. Double-click the GovernanceAutomationSetupManager.exe to execute it. The DocAve Governance Automation Setup Manager window appears.

4. In the Welcome screen, choose to install DocAve Governance Automation in English, Japanese, or French by selecting the language pack from the drop-down menu, then click Next.

5. In the Overview screen, view the instructions about unattended installation and the answer file. Click Next.

6. Select the generation option.

• Create a new answer file – Select this option to create a new answer file.

• Modify an existing answer file – Select this option to reuse an existing answer file. If this option is selected, the path field will be enabled. Click Browse to browse for an answer file.

Click Next.

7. Enter your Name and Organization into the provided field. Click Next.

8. Carefully review the Governance Automation License Agreement. After you have read the agreement, select the I accept the terms in the License Agreement checkbox, and click Next.

9. Select the installation location.

26


• Default directory – Governance Automation will be installed to the default installation location on the destination server, which is …\Program Files\AvePoint\Governance Automation.

• Customized directory – If you select this option, enter a customized path in the Installation Path field where you wish to install Governance Automation on the destination server.

Optionally, you can select the Use the default directory if your customized directory is invalid checkbox. Enable this option to install Governance Automation to the default directory if the custom path you defined is invalid.

Click Next.

10. Configure Service Configuration with the following settings:

a. DocAve Control Service Address ‒ Enter the DocAve Control Service Host and the DocAve Control Service Port.

• DocAve Control Service Host ‒ Enter the hostname or IP address of the machine where DocAve Control service is installed.

• DocAve Control Service Port ‒ Enter the DocAve Control service port number used to communicate with DocAve Control Service. The default port number is 14000.

b. IIS Web Site Settings ‒ Configure the IIS Web site settings for Governance Automation. The IIS Web site is used to access Governance Automation.

• Create a new IIS web site ‒ Enter the Web site name for Governance Automation.

• Web Site Port ‒ Enter the port number for Governance Automation communication. The default Web site port number used to access Governance Automation is 15000; you do not need to change it unless a known port conflict exists.

Optionally, you can select the Use a random port number if the specified one is being used checkbox. Select this option to use a random port number if the entered one is being used.

c. Application Pool Settings ‒ Configure the IIS application pool settings for the corresponding Web site to collect and manage requests sent to corresponding Web site.

• Create a new application pool ‒ Enter the name for the new application pool.

• Application Pool Account ‒ Enter the username and password for the application pool account.

*Note: For required permissions of the entered user, refer to Required Permissions for Governance Automation Service Accounts.

d. Governance Automation Workflow Service Configuration ‒ Configure the settings for Governance Automation Workflow Service.

27


• Workflow Service Port ‒ Enter the port number used to communicate with Governance Automation Workflow Service. The default port number is 6008.

Optionally, you can select the Use a random port number if the specified one is being used checkbox. Select this option to use a random port number if the entered one is used.

• Service Account ‒ Enter the username and password for the account that Governance Automation Workflow Service can use to log on.


e. Governance Automation Timer Service Configuration ‒ Enter the username and corresponding password for the account that Governance Automation Timer Service can use to log on.


Click Next.

11. Set up the Authentication Configuration.

• Passphrase Settings ‒ Enter the DocAve Manager Passphrase to ensure the communication with DocAve. If you forget the passphrase, you can view it by navigating to DocAve > Control Panel > General System Settings > System Options > Security Settings.

• DocAve Administration Account ‒ Enter the DocAve Manager account by which the DocAve activities are performed. The user account entered here must be local users with full control permissions of DocAve.

Click Next.

12. Set up the Configuration Database Settings.

a. Database Settings ‒ Select a Configuration Database for Governance Automation to store settings and configurations.


• Configuration Database Name ‒ Enter a name for Governance Automation Configuration Database. If the database does not exist, it will be automatically created in the entered database server.

b. Database Credentials ‒ Select Windows Authentication or SQL Authentication for the Governance Automation Configuration Database is to be used when connecting to the SQL server.

• Windows Authentication ‒ Use this method when you want the user identity to be confirmed by Windows.

• SQL Authentication ‒ SQL server will confirm the user identity itself according to the entered username and password.

28


c. Advanced Database Settings ‒ Enter a failover database server name to set it as a hot standby database server for Governance Automation Configuration Database to maximize the database availability and minimize the downtime. You must set up database mirroring in SQL server before configuring the Advanced Database Settings to ensure the availability of the failover database server.

Click Next.

13. Set up the Audit Database Settings to configure an Audit Database for Governance Automation to store the auditing information, data and reports.

• To use the same database settings including Database Server, Database Credentials, and Advanced Database Settings as Governance Automation Configuration Database’s, select the Use the previous database settings checkbox and enter a name for the Governance Automation Audit Database. If the database does not exist, it will be automatically created in the entered database server.

• To set up a separate database as a Governance Automation Audit Database, deselect the Use the previous database settings checkbox and enter the following information.

o Database Server ‒ Enter the server name or IP address of the database server you wish to connect to.

o Audit Database Name ‒ Enter a name for Governance Automation Audit Database. If the database does not exist, it will be automatically created in the entered database server.

o Database Credentials ‒ Select Windows Authentication or SQL Authentication for the Governance Automation Audit Database is to be used when connecting to the SQL server.

Windows Authentication ‒ Use this method when you want the user identity to be confirmed by Windows.

SQL Authentication ‒ SQL server will confirm the user identity itself according to the entered account and password.

o Advanced Database Settings ‒ Enter a failover database server name to set it as a hot standby database server for Governance Automation Audit Database to maximize the database availability and minimize the downtime. You must set up database mirroring in SQL server before configuring the Advanced Database Settings to ensure the availability of the failover database server.

Click Next.

14. The Installation Summary interface displays the installation information you have configured. Read the Installation summary carefully, and choose the following options to continue your configuration.

• Click Generate an Answer File to generate an answer file for Governance Automation unattended installation and save it to your desired location. You can also modify the file name before saving it.

• Click Back to go back to the previous configuration interface.

29


• Click Cancel to exit the Setup Manager without saving any of the configurations.

Importing the UnattendedInstallation.dll File Next, the UnattendedInstallation.dll file must be imported into Windows PowerShell on the server where you want to run the unattended installation command. The server can be any server in the farm as long as the server can access the answer file path.

Use either of the two methods below to import the UnattendedInstallation.dll file.

• To manually import the UnattendedInstallation.dll file, complete the following steps:

a. On the server where Governance Automation package resides, navigate to Start > Windows PowerShell. Right-click Windows PowerShell and select Run as administrator.

b. Enter the directory …UnattendedInstall\PowerShellModules. It is the directory of the PowerShellModules folder that resides in Governance Automation package.

c. Enter the following command:

Import-Module …\UnattendedInstall\PowerShellModules\UnattendedInstallation.dll

d. Press Enter to import the UnattendedInstallation.dll file.

• To automatically import the UnattendedInstallation.dll file, complete the following steps:

a. Navigate to the directory …UnattendedInstall\PowerShellModules.

b. Right-click the UnattendedInstallationLauncher.bat file and select Run as administrator.

Installation Commands The Governance Automation Unattended Installation command for installing Governance Automation remotely is Install- GovernanceAutomation. For example:

Install- GovernanceAutomation -TargetName 10.0.0.1 -Username AvePoint\GovernanceAutomation -Password “Ave” -PackageFilesFolder "C:\Governance _Automation" –AnswerFilePath "C:\AnswerFile.xml" -RemoteTempPath “C:\TempFolder”

The following table lists the detailed information for each parameters:

Parameter Type Description -TargetName Required The hostname or IP address of the destination

machine where you want to install Governance Automation.

30


Parameter Type Description *Note: The localhost or the loopback address 127.0.0.1 cannot be input as the value of TargetName. If the hostname is used, ensure that the entered computer name can be resolved through the local Hosts file, by using Domain Name System (DNS) queries, or through NetBIOS name resolution techniques.

-Username Required The username of the user used to access the destination machine where you want to install Governance Automation. The format of the username is: domain\username. The permissions of the user are as follows:

• If the user is the local administrator of the destination machine, it can be used directly. Enter .\administrator for the Username parameter.

• If the user is from the domain to which the destination machine belongs, the domain user must be added to the Administrators group on the destination machine.

The user must have the Full Control permission to the path used in RemoteTempPath parameter.

-Password Required The password of the user above. Quote the password if it contains any special character or space.

-PackageFilesFolder Required The local path on the machine where you run the command. The path stores the extracted DocAve Governance Automation unattended installation package. The format of the path is: C:\package. Quote the path if it contains any special character or space.

-AnswerFilePath Required The local path where you saved the answer file. The path must be detailed to the name of the answer file. For example, C:\AnswerFile.xml.

-RemoteTempPath Required A local path on the destination machine that the DocAve Governance Automation unattended installation package is installed to. The format of the path is: C:\temp.

31


Parameter Type Description The path will be used to store the temporary files generated during the DocAve Governance Automation unattended installation. The temporary files will be deleted as soon as the unattended installation finishes.

-Log Optional This is an optional parameter. If used, the logs of the unattended installation will be saved to the .txt file in the entered path. The path entered in this parameter must be detailed to the name of the log file. For example, C:\Log.txt. If the entered log file does not exist, it will be generated automatically.

-UseIPv6forCommunication Optional This is an optional parameter used to specify the communication method between the machine where the command is run and the destination machine that the DocAve Governance Automation is installed. If an IPv6 address is entered in TargetName parameter, this parameter must be entered. *Note: When using this parameter, both the destination machine and the machine where you run this command must support IPv6.

32


Optional Governance Automation Installations After installing the Governance Automation platform, you can install several additional Governance Automation components. These components are not required, but are recommended in order to enhance your Governance Automation experience.

Installing the DocAve Governance Automation Web Part The DocAve Governance Automation Web part embeds the business user interface within a SharePoint site. This provides SharePoint users with easier access without having to leave their SharePoint environment.

*Note: Make sure the intended users have the correct permissions to access the sites where this Web part is installed.

To use the Governance Automation Web part properly, the certificate that is used to host Governance Automation Web site must be fully trusted by your machines. For more information, refer to Changing the Certificate in IIS Manager.

Deploying the DocAve Governance Automation Web Part Solution You can add the Governance Automation Web Part to SharePoint through either the Command Prompt or Windows PowerShell. See the section below applicable to your deployment method.

Deployment through Command Prompt Complete the steps below to deploy Governance Automation Web Part solution through Command Prompt:

1. Go to Start > Run > enter cmd in the Open text box and click OK.

2. Enter the following command:

cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

Figure 1: Deploying the DocAve Governance Automation Web Part Solution through CMD (1).

3. Press Enter and continue the command in the following format:

stsadm.exe -o addsolution -filename C:\GAWebPart.wsp

*Note: C:\GAWebPart.wsp should be replaced with the path where the solution is stored.

33


Figure 2: Deploying the DocAve Governance Automation Web Part Solution through CMD (2).

4. Press Enter. You will see the message Operation completed successfully when the solution has been added to the solution store.

5. Navigate to SharePoint 2010 Central Administration > System Settings > Farm Management, and then click Manage farm solutions in which GAWebPart.wsp is displayed.

6. Click gawebpart.wsp, and then click Deploy Solution to deploy it.

Deployment through Windows PowerShell Complete the steps below to deploy Governance Automation Web Part solution through Windows PowerShell:

1. On the server where SharePoint Central Administration resides, click Start and search for Windows PowerShell.

2. Right-click Windows PowerShell and click Run as administrator.

3. If Windows PowerShell Snap-in is not installed, enter the following command:

Add-PSSnapin Microsoft.SharePoint.PowerShell -EA 0

Figure 3: Deploying the DocAve Governance Automation Web Part Solution through Windows PowerShell (1).

4. Press Enter and continue the command:

Add-SPSolution


34


5. Press Enter and Windows PowerShell prompts you to enter the solution file path.

6. In the LiteralPath field, enter the path of the solution file.


*Note: C:\GAWebPart.wsp should be replaced with the path where the solution is stored. By default, the .wsp file resides in the directory …\AvePoint\GovernanceAutomation\Sharepoint Solutions on the server where Governance Automation is installed.

7. Press Enter and the solution name, solution ID, and deployed status are displayed. Now the solution has been added to the solution store.


8. Navigate to SharePoint 2010 Central Administration > System Settings > Farm Management, and then click Manage farm solutions in which GAWebPart.wsp is displayed.

9. Click gawebpart.wsp, and then click Deploy Solution to deploy it.

Inserting the Web Part into a SharePoint Site To add the Web part to a page in a SharePoint site collection, go to the site collection you want to add the Web part to and follow the instructions below:

1. Navigate to Site Actions > Site Settings > Site collection features.

2. Find DocAve Governance Automation Web Part Feature and click Activate.

3. In the page where you want to add the Web part, click Edit Page > Insert > Web Part.

4. Select DocAve Governance Automation then select the Web part and click Add.

35


5. Once the Web part has been added, click on down arrow in the upper right-hand corner and select Edit Web Part from the drop-down menu.

6. Under Appearance, set the size for the Web part. For most, it is recommended to use height of 768 and width of 1024

7. Configure the Governance Automation Settings section:

• Governance Automation URL (Required) – Set the URL in the following format:

https://servername:port

*Note: do not add another / after the URL.

• Hide the Governance Automation menu bar (Optional) – Select the checkbox to hide the Governance Automation menu bar in the interface of your Governance Automation Web Part.

8. Click Apply to apply your changes, then click OK to save your configurations.

36


Installing DocAve Governance Automation Site Directory Web Part The DocAve Governance Automation Site Directory Web part displays detailed site information and allows business users to search for URL, Title, Primary Site Contact, Secondary Site Contact, or metadata added in Governance Automation.

For the Governance Automation Site Directory Web part to display properly, the certificate that is used to host Governance Automation Web site must be fully trusted by your machines. For more information, refer to Changing the Certificate in IIS Manager.

Deploying the DocAve Governance Automation Site Directory Web Part Solution Follow the instructions below to add Governance Automation Site Directory Web Part to SharePoint through Command Prompt or Windows PowerShell:

Deployment through Command Prompt Complete the steps below to deploy Governance Automation Site Directory Web Part solution through Command Prompt:

1. Go to Start > Run > enter cmd in the Open text box and click OK.



Figure 7: Deploying the DocAve Governance Automation Site Directory Web Part Solution (1).


stsadm.exe -o addsolution -filename C:\GASubSiteDirectory.wsp

Figure 8: Deploying the DocAve Governance Automation Site Directory Web Part Solution (2).

37


*Note: C:\GASubSiteDirectory.wsp should be replaced with the path where the solution is stored.


5. Navigate to SharePoint 2010 Central Administration > System Settings > Farm Management, and then click Manage farm solutions in which GASubSiteDirectory.wsp is displayed.

6. Click gasubsitedirectorywebpart.wsp, and then click Deploy Solution to deploy it.

Deployment through Windows PowerShell Complete the steps below to deploy Governance Automation Site Directory Web Part solution through Windows PowerShell:

1. On the server where SharePoint Central Administration resides, click Start and search for Windows PowerShell.

2. Right-click Windows PowerShell and click Run as administrator.

3. If Windows PowerShell Snap-in is not installed, enter the following command:

Add-PSSnapin Microsoft.SharePoint.PowerShell -EA 0

Figure 9: Deploying the DocAve Governance Automation Site Directory Web Part Solution through Windows PowerShell (1).

4. Press Enter and continue the command:

Add-SPSolution


5. Press Enter and Windows PowerShell prompts you to enter the solution file path.

6. In the LiteralPath field, enter the path of the solution file.

38



*Note: C:\GASubSiteDirectory.wsp should be replaced with the path where the solution is stored. By default, the .wsp file resides in the directory …\AvePoint\GovernanceAutomation\Sharepoint Solutions on the server where Governance Automation is installed.

7. Press Enter and the solution name, solution ID, and deployed status are displayed. Now the solution has been added to the solution store.


8. Navigate to SharePoint 2010 Central Administration > System Settings > Farm Management, and then click Manage farm solutions in which GASubSiteDirectory.wsp is displayed.

9. Click gasubsitedirectorywebpart.wsp, and then click Deploy Solution to deploy it.

Inserting the Web Part into a SharePoint Site To add the Web part to a page in a SharePoint site collection, go to the site collection you want to add the Web part to and follow the instructions below:

1. Navigate to Site Actions > Site Settings > Site collection features.

2. Find DocAve Governance Automation Site Directory Web Part Feature and click Activate.

3. In the page where you want to add the Web part, click Edit Page > Insert > Web Part.

4. Select DocAve Governance Automation then select the Web part and click Add.

5. Once the Web part has been added, click on down arrow in the upper right-hand corner and select Edit Web Part from the drop-down menu.

39


6. You can select how many pieces of site information to be displayed in one page by entering your desired number in the Rows to display text box.

*Note: The minimum width is 787 pixels.

7. Click OK to save. You will be prompted to confirm that you want to display the content; click Yes.

40


Installing the Governance Automation App Governance Automation App, an app for SharePoint 2013, provides SharePoint end-users with easier access to Governance Automation, without having to leave their SharePoint environment. With the Governance Automation App configured, several app parts are available for SharePoint sites.

Governance Automation App Pre-Installation Checklist Ensure that the following are in place before configuring Governance Automation App:

• Governance Automation is installed.

• SharePoint 2013 on-premises is installed on the server that will run this app.

• The SharePoint site that will have Governance Automation App added is created.

Preparing the Environment to Host Apps Before installing Governance Automation App on a SharePoint on-premises environment, the environment must be configured to host apps. Refer to the instructions in the following sections on how to prepare your environment to host Governance Automation App.

Configuring the Domain Name in DNS You must configure a new name in Domain Name Services (DNS) to host the Governance Automation App. For more information on how to configure the domain name, refer to the instructions provided here: http://technet.microsoft.com/en-us/library/fp161236.aspx (the heading Configure the domain names in DNS (all hosting options)).

Starting SharePoint Service Applications and Instances If you have already used apps in your SharePoint 2013 on-premises environment, you can skip this section.

The user who will be performing these steps must be an Active Directory domain user, a member of local Administrators group, a member of the SharePoint Farm Administrators group, must have Full Control permission to the Web front-end server, and must have access to the site collection where you are deploying the app.

First, perform the following steps to verify that the appropriate services are running:

1. Navigate to Start > All Programs > Microsoft SharePoint 2013 Products > SharePoint 2013 Central Administration.

2. Click Manage service applications under the Application Management heading.

3. In the Manage Service Applications page, verify that the following two service applications are created.

• App Management Service Application

41


http://technet.microsoft.com/en-us/library/fp161236.aspx

• Subscription Settings Service Application

4. Click System Settings on the left pane.

5. Click Manage services on server under the Servers heading.

6. In the Services on Server page, verify that the following two service instances are Started. If they are not, click Start to get them running.

• App Management Service Application

• Subscription Settings Service Application

7. If these two service applications do not exist, create a Subscription Settings service application and create an App Management service application. For detailed information on how to create the service applications, refer to the instructions provided here: http://technet.microsoft.com/en-us/library/fp161236.aspx (the chapter Configure the Subscription Settings and App Management service applications).

Configuring the App URL Before adding the Governance Automation App, the app URL must be configured. Complete the following steps to configure the app URL:

1. On the SharePoint server, navigate to Start > All Programs > Microsoft SharePoint 2013 Products > SharePoint 2013 Central Administration.

2. Click Apps on the left pane.

3. Click Configure App URLs under the App Management heading. The Configure App URLs interface appears.

4. In the App domain text box, enter the domain name that has been configured in Configuring the Domain Name in DNS.

5. In the App prefix text box, enter a name as the URL prefix for the app.

6. Click OK to save your configurations.

For more information on how to configure the app URL, refer to the instructions provided here: http://technet.microsoft.com/en-us/library/fp161236.aspx (the chapter Configure the app URLs to use).

Setting up an App Catalog An app catalog site collection stores apps. These apps can be added to any site under the Web application where the app catalog site collection resides. Only the members of the Farm Administrators group can view and operate the app catalog site collection.

Follow the steps below to configure SharePoint 2013 app catalog:

1. On the SharePoint server, navigate to Start > All Programs > Microsoft SharePoint 2013 Products > SharePoint 2013 Central Administration.

2. Click Manage App Catalog under the Apps heading.

42




3. In the Manage App Catalog page, select the Web application where you are about to create the app catalog site collection.

4. Select Create a new app catalog site. Then, click OK. The Create App Catalog page appears.

5. Configure the necessary settings for creating a new app catalog site collection.

a. Enter a title for the app catalog site collection in the Title text box.

b. In the Description text box, enter the description for the site collection.

c. In the URL text box, enter the URL to use for the site collection.

d. In the User Name text box of the Primary Site Collection Administrator section, enter the user who will manage the catalog.

*Note: Only one username can be entered. Security groups are not allowed.

e. In the Users/Groups text box of the End Users section, enter the names of the users or groups that can browse the catalog.

*Note: Added users or groups have read access to the app catalog site collection. You can add multiple usernames and security groups. Users must be added as End Users to be able to browse the app catalog from their site collections. However, if users want to add the app to their sites, these users must be farm administrators by default.

f. In the Select a quota template drop-down list, select the quota template to use for the site.

g. Click OK to create the app catalog site collection.

*Note: Each Web application needs an app catalog site collection. If you wish to add Governance Automation App to other Web application, the Web application must have its own app catalog site collection.

Registering the Governance Automation App Open the created app catalog site collection in your web browser and replace the character after layouts/ with 15/appregnew.aspx. For example,

App catalog site collection URL: http://server/_layouts/15/start.aspx#/

Modified URL: http://server/_layouts/15/appregnew.aspx

Access the modified URL and a new page appears. Then, configure the following app information in the page:

1. App Id – Enter EC72749B-68C8-411A-B535-D4490AD6201F in the text box.

2. App Secret – Enter TcdbE+84c3X1ne3AhH9NYra2r7RN2NILJeKyTYsdWQk= in the text box.

3. Title – Enter Governance Automation.

4. App Domain – Enter the hostname of the Governance Automation server.

5. Redirect URL – Enter the URL in the following format:

43


https://GAHost:GAPort/App/home/Index.

• GAHost – The hostname of your Governance Automation server.

• GAPort – The port number of your Governance Automation Web site.

6. Click Create to register the app.

Modifying App File Complete the following steps to modify .app file:

1. On the Governance Automation server, navigate to …\AvePoint\GovernanceAutomation\SharePoint Solutions.

2. Find the AppPart.app file and copy the file to your desired location on the server.

3. Navigate to the location where the AppPart.app file resides. Right-click the file and select Rename.

4. Modify the file extension name .app to .zip.

5. Extract the AppPart.zip file.

6. In the extracted folder, right-click the AppManifest.xml file and select Edit.

7. Find the attribute <StartPage> and modify https://ga.thake.com to your Governance Automation Web site URL.

Figure 13: Modifying the AppManifest.xml file.

8. Save and close the AppManifest.xml file.

9. Edit all of the files whose file name starts with elements. In each file, find https://ga.thake.com and modify it to your Governance Automation Web site URL.

Figure 14: Modifying the elements file.

10. Save and close each file.

11. After all of the files are modified, select all of the folder and files within the AppPart folder, right-click them and select Send to > Compressed (zipped) folder. Enter your desired name for the ZIP file.

44


12. Rename the ZIP file. Modify the file extension name .zip to .app.

Uploading Governance Automation App to App Catalog Before adding Governance Automation App to any SharePoint site, you must upload Governance Automation App to the app catalog site collection.

Complete the following steps to upload Governance Automation App to the app catalog site collection:

1. Navigate to the app catalog site collection that is created in Setting up an App Catalog.

2. Click Apps for SharePoint on the left pane.

3. In the Apps for SharePoint interface, click new app.

4. In the Add a document window, click Browse… and select the .app file that is configured in Modifying App File.

5. Click OK to upload the .app file.

Configuring Governance Automation Web Site Authentication The SharePoint user who accesses Governance Automation App must has the permission to access Governance Automation Web site. Within SharePoint, Governance Automation App cannot retrieve the information of the SharePoint user when the user accesses the app.

To verify whether the user has the permission to access the app, you must configure Governance Automation Web site authentication in IIS Manager. Governance Automation will retrieve the user information of the local machine via Windows Authentication and then check whether the user has the permission to access Governance Automation.

Complete the following steps to configure Governance Automation Web site authentication in IIS Manager:

1. On the Governance Automation server, navigate to Start > Administrative Tools > Internet Information Services (IIS) Manager.

2. Double-click the local hostname on the left pane.

3. Expand the Sites node and click Governance Automation.

4. Double-click Authentication in the middle.

5. Make sure the status of Windows Authentication is Enabled. If not, right-click Windows Authentication and select Enable.

6. Make sure the status of Anonymous Authentication is Disabled. If not, right-click Anonymous Authentication and select Disable.

*Note: With the above Governance Automation Web site authentication configured, a Windows authentication pop-up window will appear when you log into Governance Automation Web site for the first time. After entering the correct username and password, a pop-up windows appears to remind that

45


your account does not exist. The issue is caused by the difference between the authentication configured in IIS and the authentication configured in DocAve, even if they are both Windows authentication. Click OK in the pop-up window, then enter the correct account information, select the authentication method, and click Login. You will log into Governance Automation successfully.

Adding Governance Automation App to a SharePoint Site The user who adds Governance Automation App to a SharePoint site must have the following permissions:

*Note: System accounts cannot add Governance Automation App to a SharePoint site.

• A member of Farm Administrators group or local Administrators group.

• Has Full Control permission to the site that you are about to add Governance Automation App to.

• Has at least Read permission to the app catalog site collection.

Complete the following steps to add Governance Automation App from the app catalog site collection to any SharePoint site under the same Web application where the app catalog site collection resides.

1. Navigate to the SharePoint site where you want to add Governance Automation App.

2. Click the Settings ( ) button on the top-right corner of the site, and then click Add an app. The Your Apps page appears.

3. On the left Quick Launch, click From Your Organization to add Governance Automation App from app catalog.

4. Enter Governance Automation in the Find an app search text box, and then press Enter.

5. Click Governance Automation.

6. Click Add it to add Governance Automation App on the site.

7. When asked if you want to trust Governance Automation, click Trust It.

Governance Automation App is added to the site successfully and a Governance Automation link is added on the Quick Launch. Click the Governance Automation link and you are brought to a new page. By default, the following tiles are displayed in the page:

• Start a Request

• View My Requests

• View My Tasks

• Public Site Collection Directory

• My Sites

*Note: The tile Morning and Reporting is unsupported in Governance Automation App.

46


You can choose to hide the tiles from the page by deselecting the tiles in Governance Automation > Settings > Business User Features Activation or Deactivation. For more information, refer to Hiding or Revealing Sections to Business Users .

Inserting Governance Automation App Part Governance Automation App provides several app parts that can be inserted to SharePoint sites.

To insert Governance Automation app parts to a site, complete the following steps:

1. Go to the homepage of this site and click the PAGE tab on the ribbon.

2. In the PAGE tab, click Edit.

3. Click the INSERT tab and click App Part.

4. The following app parts of Governance Automation App are displayed in the Parts section:

• My Requests – Displays the login user’s saved requests and submitted requests.

• My Site Collections – Displays the site collections that the login user is responsible for managing.

• My Sites – Displays the sites that the login user is responsible for managing.

• My Tasks – Displays the tasks that are assigned to the login user.

• Public Site Collections – Displays all site collections tagged for public sharing that are managed by Governance Automation.

• Site Directory – Displays sites managed by Governance Automation within this site collection.

• Site Information Card – Displays key information about the site, such as ownership, classification, policy, and available service requests.

*Note: This app part can be inserted to a top-level site of a site collection, or be inserted to a site. In a top-level site, the app part displays site collection information. In a site, the app part displays site information.

• Start a Request – It is used to start a Governance Automation service request.

5. Select your desired app part and click Add to add it to the site.

6. Click Save on the ribbon to save your configurations.

47


Deploying the Governance Automation Policy Bar Solution To use the site policy bar feature in a site collection policy, you must deploy the Governance Automation Policy Bar solution.

The solution GAPolicyBar.wsp resides in the directory …\AvePoint\GovernanceAutomation\SharePoint Solutions on Governance Automation server. To deploy the solution on a SharePoint Web-front end server, copy the GAPolicyBar.wsp to the SharePoint Web-front end server first.

Complete the following steps to deploy the solution:

1. On the SharePoint server, navigate to SharePoint 2013 Management Shell. Right-click it and select Run as administrator.


stsadm –o addsolution –filename “C:\Program Files\AvePoint\GovernanceAutomation\SharePoint Solutions\GAPolicyBar.wsp

*Note: C:\Program Files\AvePoint\GovernanceAutomation\SharePoint Solutions\ should be replaced with the exact path where the solution GAPolicyBar.wsp resides.



5. Click gapolicybar.wsp and then click Deploy Solution to deploy it.

6. Go to the site collection where you are about to add the site policy bar.

7. Navigate to Settings > Site settings > Site Collection Administration > Site collection features.

8. Find Governance Automation Policy Bar and click Activate.

48


Post-installation Procedures Upon initial installation, Governance Automation requires additional modifications and configurations in order for it to communicate properly with DocAve and within your farm. Review each section below carefully and follow the instructions provided.

Allowing Full Control Permission to the DocAve Private Key For Governance Automation to communicate with the DocAve Control service, the service account(s) for the Governance Automation Workflow Service, Governance Automation Timer Service, and Application Pool must have the Full Control permission to the DocAve private key. To allow the service account(s) Full Control to the DocAve private key, complete the following steps:

1. Navigate to the server where Governance Automation is installed.

2. Navigate to Start > Run, enter mmc in the Open text box, and click OK.

3. In the pop-up window, click File > Add/Remove Snap-in….

4. Select Certificates on the left pane and click Add>.

5. Select Computer account for the local machine, click Next, and then click Finish.

6. Click OK and the Add or Remove Snap-ins window is closed.

7. On the left pane, expand the Certificates (Local Computer) node, and then expand the Personal node.

8. Click the Certificates node.

9. Right-click the certificate DocAve on the right pane, then select All Tasks > Manage Private Keys.

10. In the pop-up window, respectively select the service account for Governance Automation Workflow Service, Governance Automation Timer Service, and Application Pool, then select the Allow checkbox for Full control.

11. Click Apply to apply the configurations.

12. Click OK to save the application.

Enabling the Service Account to Listen to the Governance Automation Workflow Service Port When a request is submitted through the Governance Automation interface, the Governance Automation Web site sends the request to the Governance Automation Workflow Service. To receive requests, the service account for Governance Automation Timer Service must have permission to listen to the port that hosts the Governance Automation Workflow Service. To enable the service account to listen to the Workflow Service Port:

49


1. Navigate to the server where Governance Automation is installed.

2. Navigate to Start > Command Prompt.

3. In the Command Prompt window, enter the command in the following format:

netsh http add urlacl url=http://+:workflowport/Uri/ user=domain\username

a. workflowport – Replace with the Governance Automation Workflow Service port.

b. Uri – Be replaced by the Uri value for each service type. To get the Uri value, follow the steps below:

i. Navigate to …\AvePoint\GovernanceAutomation\Config.

ii. Find the WorkflowService file and open the file with Notepad.

iii. Click Edit > Find, enter Uri in the text box, and click Find Next. The value of the Uri attribute is the one that will be used in the command.

iv. Repeat the step above to get the Uri value for each service type that will be used in Service Catalogue.

c. domain\username – Replace with the service account for Governance Automation Workflow Service.

4. Press Enter to execute the command.

*Note: The command must be executed for each service type that will be used in Service Catalogue.

5. Navigate to Start > Administrative Tools > Services, and restart Governance Automation Workflow Service.

Changing the Certificate in IIS Manager When attempting to access the Governance Automation login screen via a browser, a certificate error may appear. To prevent the certificate error, access IIS manager and change the certificate that is used to host the Governance Automation Web site to a fully trusted certificate. This will allow uninterrupted communication between DocAve and Governance Automation. This certificate must be fully trusted by all of the end-user computers in your environment. To change the certificate, complete the following steps:

1. On the server where Governance Automation is installed, navigate to Start > Administrative Tools > Internet Information Services (IIS) Manager.

2. Expand the connection and expand Sites.

3. Right-click Governance Automation and click Edit Bindings…. The Site Bindings window appears.

4. Click the binding and click Edit…. The Edit Site Binding window appears.

50


5. In the SSL certificate drop-down list, select the certificate that is fully trusted by all of the client machines in your organization.


7. Click Close to close the Site Bindings window.

8. After the certificate is successfully changed in IIS Manager, you must manually copy two configuration files to Governance Automation directories to complete the process. For these instructions, proceed to step 1 of Applying User-Defined Certificates.

Applying User-Defined Certificates If a user-defined certificate was applied when installing DocAve Agent and Governance Automation, or if you changed the built-in certificate to a user-defined certificate in the DocAve 6 Agent Configuration Tool and Governance Automation Configuration Tool, the AgentCommonWCFBehaviors.config file in …\AvePoint\DocAve6\Agent\bin and the GAControlWCFBehaviors.config file in …\AvePoint\GovernanceAutomation\Config were automatically updated to reflect the certificate change.

However, the AgentCommonWCFBehaviors.config file in …\AvePoint\DocAve6\Agent\bin\GovernanceAutomation and the GAControlWCFBehaviors.config file in …\AvePoint\GovernanceAutomation\bin\Config must be manually updated.

To manually update the .config files, complete the following steps:

1. On the server where DocAve Agent resides, navigate to …\AvePoint\DocAve6\Agent\bin.

2. Find the AgentCommonWCFBehaviors.config file, right-click the file, and select Copy.

3. Navigate to …\AvePoint\DocAve6\Agent\bin\GovernanceAutomation and paste the copied .config file into this directory.

4. The Confirm File Replace window appears. Click Yes to proceed.

5. On the server where Governance Automation is installed, navigate to …\AvePoint\GovernanceAutomation\Config.

6. Find the GAControlWCFBehaviors.config file, right-click the file, and select Copy.

7. Navigate to …\AvePoint\GovernanceAutomation\bin\Config and paste the copied .config file into this directory.

8. The Confirm File Replace window appears. Click Yes to proceed.

51


Applying a Governance Automation License The Governance Automation license is applied through DocAve using Control Panel’s License Manager. To apply your new Governance Automation license:

1. Log into DocAve and navigate to Control Panel > License Manager.

2. Click Import, and browse to where you extracted the content of the ZIP file to.

3. Select the license and click Open.

4. Click Apply on the ribbon to apply the license.

Once the license has been applied, Governance Automation will automatically be enabled and ready to use.

Logging into Governance Automation for the First Time In Governance Automation, different administrator and business user accounts may be configured in the Account Manager. However, when logging into Governance Automation for the first time, you must use the built-in administrator account:

Login ID: admin

Password: admin

Login on to: Local System

Configuring Authentication Types See the sections below for instructions on configuring AD and Windows Authentication.

Configuring AD Authentication To grant your users access to Governance Automation using their Active Directory (AD) account, the AD must be configured and enabled in DocAve. For information on configuring AD authentication in DocAve, refer to the Authentication Manager section of the DocAve 6 Control Panel Reference Guide.

Setting Windows Authentication as the Default Login Method Governance Automation supports setting Windows Authentication as the default method so that your Windows account will be used to automatically log into Governance Automation.

To set Windows Authentication as the default method to log into Governance Automation, complete the following steps:

52



1. Install the Windows Authentication role service on the server where DocAve Control service is installed. (If the role has already been installed, skip this step)

a. Navigate to Start > Administrative Tools > Server Manager.

b. Click Roles.

c. Click Add Role Services on the right pane. The Add Role Services window appears.

d. Select the Windows Authentication checkbox.

e. Click Next to confirm your selection.

f. Click Install to install the Windows Authentication role service.

2. Enable Windows Authentication on the server where DocAve Control service is installed.

a. Navigate to Start > Internet Information Services (IIS) Manager.

b. Click your connection and then double-click Authentication.

c. Right-click Windows Authentication and click Enable.

3. Configure Windows Authentication in DocAve Manager.

a. Navigate to Control Panel > Authentication Manager.

b. Click Windows Authentication on the ribbon.

c. Select NTLM as the authentication type.

d. Click OK to save your configuration and go back to the homepage of Authentication Manager.

e. In the field of Windows Authentication, click Set as default.

4. Configure User Authentication in your Web browser.

a. In Internet Explorer, navigate to Internet Options > Security.

b. In the Internet zone, click Custom level….

c. In the User Authentication section, select Automatic logon with current user name and password.

d. Click OK to save the Internet zone configuration.

e. Click Apply to apply your changes.

f. Click OK to save your security configuration.

Windows Authentication is set as the default login method to log into DocAve and Governance Automation.

When you access Governance Automation, Governance Automation automatically uses your Windows account to log and you are brought to the homepage directly.

53


Configuring E-mail Notification Settings Governance Automation e-mail notifications leverages SMTP settings configured in DocAve. For Governance Automation to send out e-mail notifications, you must first configure the Send E-Mail Settings in DocAve. For information on configuring the Send E-Mail Settings in DocAve, refer to the User Notification Settings section of the DocAve 6 Control Panel Reference Guide.

Registering SharePoint Online Admin Centers/Site Collections To use Governance Automation to manage content in a SharePoint Online standard instance or SharePoint Online dedicated instance, you must first register in DocAve the SharePoint Online standard instance admin centers or SharePoint Online standard/dedicated instance site collections. Refer to the following steps to register SharePoint Online standard instance admin centers and SharePoint Online standard/dedicated instance site collections:

1. In DocAve Manager, navigate to Control Panel > SharePoint Sites.

2. Select the Default_SharePoint Sites_Group or a newly created SharePoint Sites group.

3. Click Manage Site Collection on the ribbon.

4. Click Add on the ribbon.

5. Enter the Site collection URL, Username, and Password in the corresponding text boxes.

*Note: To register a SharePoint Online standard instance admin center, enter the admin center URL in the Site collection URL text box.


*Note: To properly retrieve data, AvePoint strongly recommends that a SharePoint Sites group contains only those site collections that are in the same SharePoint Online Admin Center or the same Central Administration.

For more information about managing SharePoint Sites in DocAve Control Panel, refer to the DocAve Control Panel Reference Guide.

Configuring Language, Time Zone, Date/Time Format, and Office 365 Account Settings When you first log into DocAve Governance Automation, the Configure Personal Settings window appears. Follow the instructions below to configure your personal settings.

1. Language – Select a display Language from the drop-down menu.

2. Time Zone and Date/Time Format – Select the display time zone, date format, and time format for the Governance Automation interface.

54




3. Office 365 Account – Enter the Office 365 account that will be mapped to the currently logged-in user. This enables the current user to manage content in SharePoint Online through Governance Automation.

*Note: The entered Office 365 account must be in the format of [email protected].

4. Click Save on the ribbon; a window appears.

5. Enter the password for the Office 365 account in the text box and click OK to save your configuration; the display language and display time zone will change automatically. Click Cancel to close the window without saving any configurations.

6. If desired, select the Do not show again when I login next time checkbox to log into Governance Automation without displaying the Configure Personal Settings window.

*Note: Personal settings can be configured at any time by clicking your account name in the top-right corner of the Governance Automation interface.

55


Getting Started with Governance Automation The sections below detail what you must configure in order to use Governance Automation (Account Manager, Departments, Approval Processes, Policies, and Services). These instructions should be followed in order, from Configuring Account Manager through Configuring Services. Additional optional configurations are described in Additional Governance Automation Configurations.

Configuring Account Manager *Note: In order to use your Active Directory to create user accounts and groups in Governance Automation, Active Directory authentication must be configured in DocAve. For more information on how to configure Active Directory authentication in DocAve, see the Authentication Manager section of the DocAve 6 Control Panel Reference Guide.

Account Manager allows you to manage user accounts and groups for Governance Automation. There are two default groups used to manage user accounts for Governance Automation:

• Administrator Group – Users in this group are able to access both the administrator and business user interface of Governance Automation, giving them the ability to configure system settings, monitor requests and tasks, and maintain services, as well as submit and approve requests for services.

• Business User Group – Users in this group are only able to access the business user interface of Governance Automation, allowing them to submit and approve requests for allowed services. Custom Business User Groups may be created allowing designated users to also view Governance Automation reports for monitoring processes and ownership of site collections.

Additional custom user groups can be created to allow certain users to view reports and monitor all requests and tasks.

To configure Account Manager for Governance Automation, click Account Manager in the Settings page. Click Close on the ribbon to close the Account Manager interface.

Managing Governance Automation Groups In Account Manager, you can change the number of groups displayed per page by selecting the desired number from the Show rows drop-down menu in the top right-hand corner. To sort the groups, click the sort ( ) button in a column heading such as Group Name, and Description.

You can perform the following actions in the Account Manager interface:

• Add Group ‒ Create groups of user accounts for Governance Automation. For information about creating groups of Governance Automation, see Creating New User Groups.

• Edit Group ‒ Modify user group information or reassign group permissions. For information about editing groups of Governance Automation, see Creating New User Groups.

56



• View User(s) ‒ View the user accounts within a selected group. Within the groups, you can add or remove user accounts. For information about adding users or removing user accounts, see Adding or Removing Users.

• Delete Group ‒ Remove a group from Governance Automation. A confirmation window will pop up when you click Delete Group. Click OK to delete the selected group, or click Cancel to return to the Account Manager interface without deleting the selected group. Note that the Administrator Group and Business User Groups cannot be deleted.

Managing Administrator Accounts To view and manage the administrators for Governance Automation, in the Account Manager interface, select the Administrator Group checkbox and click View User(s) on the ribbon. Click Back on the ribbon to return to the Account Manager interface. All previously configured administrators will be listed in the Administrator Group interface.

In this interface, you can change the number of administrator accounts displayed per page by selecting the desired number from the Show rows drop-down menu in the top right-hand corner. To sort the user accounts, click the sort ( ) button in a column heading such as Username, and Permission. Then choose Ascending or Descending. You can also filter Permission by clicking the filter ( ) button.

You can perform the following actions in the Administrator Group interface.

• Add User ‒To add a user to the Administrator Group, click Add User on the ribbon. You will be brought to the Add User interface.

a. Add User(s) ‒ Enter the username of the users/groups you wish to add into the text box. Then press Enter to check that the names are valid.

b. Permissions ‒ Select the permission level for this administrator by checking the corresponding radio buttons. Full Control to all farms gives the user control over all farms using Governance Automation, while Integrate with SharePoint Permissions gives the user control to only farms that they are a SharePoint administrator of.

c. Click Save on the ribbon to save the configurations, or click Cancel to return to the Administrator Group interface without saving any configurations.

• Edit ‒To change the permission level of an administrator, select the user by clicking the username, then click Edit on the ribbon. You will be brought to the Edit User interface. Select the permission level for this administrator by checking the corresponding radio buttons. Full Control to all farms gives the user control over all farms using Governance Automation, while Integrate with SharePoint Permissions gives the user control to only farms that they are a SharePoint administrator of.

Click Save on the ribbon to save the modifications, or click Cancel to return to the Administrator Group interface without modifying the settings of the selected user.

• Remove User from Group ‒ To remove an administrator from Governance Automation, select the user by clicking the username, then click Remove User from Group on the ribbon. A

57


confirmation window will pop up. Click OK to delete the selected user, or click Cancel to return to the Administrator Group interface without deleting the selected user.

Managing Business Users To view and manage the business users for Governance Automation, in the Account Manager interface, select the Business User Group checkbox and click View User(s) on the ribbon. Click Back on the ribbon to return to the Account Manager interface. All previously configured business users will be listed in the Business User Group interface and you can perform the following actions.

• Add User ‒ To add a user to the Business User Group, click Add User on the ribbon. You will be brought to the Add User interface. Enter the name of the users/groups you wish to add in the text box. Then press Enter to check that the names are valid.

Click Save on the ribbon to save the configurations, or click Cancel to return to the Business User Group interface without saving any configurations.

• Remove User from Group‒ To remove a business user from Governance Automation, select the user by clicking before the username, then click Remove User from Group on the ribbon. A confirmation window will pop up. Click OK to delete the selected user, or click Cancel to return to the Business User Group interface without deleting the selected user.

Creating New User Groups To create a new user group for Governance Automation, in the Account Manager interface, click Create Group on the ribbon. To modify a previously configured group, select the desired group, and click Edit Group on the ribbon. These groups are aimed to give the business users’ permissions to view the reports, activities, requests, and tasks.

In the Create Group or Edit Group interface, configure the following settings:

1. Group Information ‒ Enter a Group Name in the provided text box. Then enter an optional Group Description for group for future reference

2. Permissions ‒ Assign the permissions to the group by selecting corresponding checkbox.

3. Click Save to save the configurations, or click Cancel to return the Account Manager interface without creating the group.

Adding or Removing Users To add a user into a group, refer to the instructions below:

1. In the Account Manager interface, select a group by clicking the group name, and then click View User(s) on the ribbon.

2. Within the group, click Add User on the ribbon. You will be brought to the Add User interface.

3. Enter the name of the users/groups you wish to add in the text box. Then press Enter to check that the names are valid.

58


4. Click Save on the ribbon to save the configurations, or click Cancel to return to the group interface without adding any users.

To remove a user from a group, refer to the instructions below:

1. In the Account Manager interface, select a group by clicking the group name, and then click View User(s) on the ribbon.

2. Within the group, select the desired user by clicking the Username, and click Remove User from Group on the ribbon. Then a confirmation window will pop up.

3. Click OK to delete the selected user, or click Cancel to return to group interface without deleting the selected user.

Enabling a User Profile Service The User Profile Service application in Microsoft SharePoint Server 2010/2013 stores user information in a central location. The User Profile Service automatically retrieves department information from SharePoint user profiles so that it is not necessary for the IT Admin to select a department in a service, or for a requester to select a department when filling out a service request.

If you are using a custom database to store user information, refer to Retrieving User Information from a Custom Database for instructions on synchronizing with DocAve Governance Automation.

To enable a User Profile Service for Governance Automation, navigate to the Governance Automation homepage, click Settings, and then click User Profile Service.

Follow the instructions below to enable a User Profile Service:

1. In the User Profile Settings interface, select the Enable User Profile Settings checkbox to have Governance Automation retrieve the department information from SharePoint user profiles.

2. Select the farm from in the Farm Name drop-down menu. This is the farm that will be leveraging the User Profile Service.

3. Select a User Profile Service from the User Profile Service Name drop-down menu.

*Note: User Profile Services that are shared with the selected farm can also be loaded.

4. Click Save on the ribbon to save the configurations, or click Cancel to return to the Settings interface without saving the configurations.

Retrieving User Information from a Custom Database To retrieve user information from a custom database, follow the instructions below:

1. Add the GAContract.dll file that is in …\AvePoint\GovernanceAutomation\bin as a reference.

2. Make a class and inherit the ICustomRoleService interface.

3. Implement interface ICustomRoleService.

59


4. Note that the user data must contain the following information: IdentityName, Department, Manager, and IsDeleted.

5. Build the DLL file and add to …\AvePoint\GovernanceAutomation\bin

6. Navigate to …\AvePoint\GovernanceAutomation and right-click the Global.config file to open with Notepad.

7. Find the LoadCustomRolesConfig node and modify the value to True.

8. Add the assembly information to the highlighted area below:

Figure 15: Modify the Global.config file

9. Save and close the file.

10. Upon completion of the steps above, DocAve Governance Automation will retrieve user metadata from the customized database and synchronize user information.

Configuring Departments Departments with specific responsibilities in an organization can be associated with corresponding services in order to better organize those services. This helps create custom service catalogs that cater to the needs of different users.

You can retrieve the department information from SharePoint User Profile Service or add new departments manually. Both methods are described in the sections below.

Retrieving Department Information from a SharePoint User Profile Service To get department information from an existing SharePoint User Profile Service, follow the instructions below:

1. Navigate to Governance Automation homepage and click Settings. In the Settings page, click Department to configure departments.

2. In the Department interface, select the Use Property in User Profile Service by clicking the radio button next to it.

3. Select Property from the drop-down menu to get the department information. By default, the Department property is selected in the drop-down menu. The properties displayed here are configured in User Profile Service.

60


4. Click Save on the ribbon to save the configurations. Click Cancel to return to the Settings interface without saving any configurations.

Manually Adding New Departments To add new departments in Governance Automation, follow the instructions below:

1. Navigate to Governance Automation homepage and click Settings. In the Settings page, click Department to configure departments.

2. In the Department interface, select the Configure Departments radio button.

3. Click the Add New link under the Configure Departments radio button.

4. Enter a Department name in the text box under the Value column heading.

5. Click the Insert link next to the text box to add the desired department. Click next to the text box to modify the department name, and click the Update link to save the modifications or click the Cancel link to exit the editing mode without saving any modifications. Click next to the Edit link to delete the unnecessary departments.

6. Repeat the steps above to add more departments.

7. Click Save on the ribbon to save all of the configurations. Click Cancel to return to the Settings interface without saving any configurations.

Configuring Approval Process To create or manage approval processes, click Approval Process in the Administrator landing page (use the arrow on the sides to scroll).

A Governance Automation approval process is a defined process to automatically obtain approval for a SharePoint or DocAve management operation. With approval processes properly configured, these operations can be completed efficiently by standardizing the process, without human error.

In Approval Process Management, all of the Governance Automation approval processes you have configured are displayed. You may change the number of approval processes displayed per page, as well the order they are displayed in. To change the number of approval processes displayed per page, select the desired number from the Show rows drop-down menu in the top right-hand corner. To sort the approval processes, click the sort ( ) button in a column heading such as Approval Process, Category, Last Modified Time, and Created By.

You can customize how the approval processes are displayed in a number of different ways:

• Search – Allows you to filter approval processes displayed by the keyword you designate. The Approval Process column and the Created By column support to search for the desired approval process, and only the content in the column displayed in the current view can be searched.

• Manage columns ( ) – You can manage which columns are displayed in the list so that only information you want to see is displayed. Click the manage columns ( ) button, then select the

61


checkbox next to the column name to have that column shown in the list. Click All to select the checkboxes of all columns and have all columns displayed in the list or click None to deselect the checkboxes of all columns and have none columns displayed in the list.

• Filter items ( ) – This allows you to filter which item in the list is displayed. Click the filter items ( ) button of the column you want to filter, and then select the checkbox next to the item name to have that item shown in the list.

You can perform the following actions in Approval Process Management:

• Create – Click Create on the ribbon to go to the Create Approval Process interface where you will find a list of approval process templates. See Creating or Editing Approval Processes for details on creating a new approval process.

• View Details – Click an approval process name for detailed information about the approval process.

• Edit – Select an inactive approval process, and click Edit on the ribbon. See Creating or Editing Approval Processes for details on editing an existing approval process.

• Delete – Select an inactive approval process, and click Delete on the ribbon. A confirmation window will pop up for this deletion. Click OK to delete the selected approval process, or click Cancel to return to the Approval Process Management interface without deleting the selected approval process.

• Activate – Select the approval processes you want to activate, and click Activate on the ribbon. Active approval processes can be used in policies and services.

• Deactivate – Select the approval processes you want to deactivate, and click Deactivate on the ribbon.

Creating or Editing Approval Processes To create a new approval process, click Create on the ribbon in the Approval Process Management interface. You will be brought to the Create Approval Process interface. To modify a previously configured approval process, select the approval process in the Approval Process Management interface, and click Edit on the ribbon.

Follow the instructions below to configure an approval process:

1. Configure the basic settings for an approval process.

2. Approval Process Name – Enter a Name and an optional Description for this approval process in the corresponding text boxes.

3. Approval Process Category – Categories are used to organize your Governance Automation approval processes. Select an existing category from the Use an existing category drop-down menu or create a new category for this approval process by selecting Add a new category then entering a name for this new category.

4. Approval Process Stages – Choose the approval method:

62


• Use approval stages – Select the Use approval stages radio button and select the number of approval stages. Having multiple approval stages provides flexibility based on your governance needs.

• Auto-approve – Select the Auto-approve radio button and services using this approval process will be performed automatically upon request.

• Integrate with external workflow – Select the Integrate with external workflow radio button, then select an external workflow integration profile and an external workflow. The approval process will be executed according to the selected workflow.

5. CC – Specify additional users who you want to be notified when the service request is completed without assigning tasks to them. By default, Governance Automation will notify all of the approvers and the requester upon request completion. Enter the username in the provided text box. Press Enter to check that the names are valid.

You can also enter $ to select the following roles:

• Manager Of Approver – The manager of the approver of the service request will be notified.

• Administrator Contact – The administrator contact defined in the service will be notified.

6. Select a Completion E-mail Template for this notification from the drop-down menu. The Completion E-mail Template can be configured in the Settings of Governance Automation.

7. If you select Auto-approve, skip the following steps and click Save to save all of the configurations and return to the Create Approval Process interface. Click Save and Activate to save all of the configurations and activate this approval process. Click Cancel to return to the Create Approval Process interface without saving any changes.

8. If you chose to use approval stages, continue to the Stage One Configurations. Configure the following for the first stage of approval:

a. Stage Name – Enter a Name for the first level stage. By default, its name is First Stage Approval. Then enter an optional Description for future reference.

b. Approver(s) – Specify the first stage approvers. All approvers will be assigned a task when this approval process starts.

*Note: In order to leverage role based approval, User Profile Service must be configured and enabled in at least one of your SharePoint farms, and be configured in Governance Automation Settings.

• Specify the Role – Specify the approver relevant to the user making the request. This may be preferable to specifying specific users since role based approval can adapt to personnel shifts in your organization.

Enter $ in the Assign To text box and a list of roles appear in the drop-down menu. Select the role of the person designated to be the approver for this approval stage from the drop-down menu. You can enter more than one role, but if more than one role is appointed for a given stage, all approvers of all

63


selected roles for that stage must approve the request in order to proceed to the next approval stage.

The following roles are available, but the roles vary when specifying roles in different types of services.

o Requester – The requester of the service request will be assigned to deal with the task.

When the requester is the only approver, the task will be approved automatically.

If the requester is one of the approvers and the approval order is One at a time (serial), the task generated for the requester is approved automatically and a new task is assigned for the next approver.

When the requester is one of the approvers and the approval order is All at once (parallel), the task generated for the requester is approved automatically. The approval stage will be complete if Allow the approval stage to complete when one approver approves is selected. Otherwise, the approval stage will not be complete until the other approvers approve.

When there are multiple approval stages (the requester is one of the approvers) and the approval order is One at a time (serial), the task generated for the requester will not be approved automatically if the request is modified by other approvers before the task is assigned to the requester.

For tasks that contains a report (including Clone or Transfer User Permissions tasks, Grant Permissions tasks, Remove Permissions tasks, Manual Archive tasks, and Permission Recertification tasks), they will not be approved automatically and the requester must manually approve the task.

o Manager Of Requester – The manager of the requester of the service request will be assigned to deal with the task.

o Primary Site Collection Contact – The Primary Site Collection Contact will be assigned to deal with the task. The Site Collection Contacts are assigned when configuring the services.

o Secondary Site Collection Contact – The Secondary Site Collection Contact will be assigned to deal with the task. The Site Collection Contacts are assigned when configuring the services.

o Primary Site Contact – The Primary Site Contact will be assigned to deal with the task. The Site Contacts are assigned when configuring the services.

o Secondary Site Contact – The Secondary Site Contact will be assigned to deal with the task. The Site Contacts are assigned when configuring the services.

64


o Primary Site Collection Administrator – The Primary Site Collection Administrator will be assigned to deal with the task.

o Secondary Site Collection Administrator – The Secondary Site Collection Administrator will be assigned to deal with the task.

*Note: The Secondary Site Collection Administrator is unsupported for SharePoint Online standard instance and SharePoint Online dedicated instance.

o Farm Administrator – The farm administrator will be assigned to deal with the task.

*Note: Farm administrator is unsupported for SharePoint Online standard instance and SharePoint Online dedicated instance.

o Manager of Previous Stage Approver (this option is only available for second or third stage approval – The manager of the previous stage’s approver will be assigned to deal with the task.

o Source User – The user to clone permissions from.

o Target User – The user to clone permissions to.

o New Site Collection Contact/Administrator – The user that takes over the role of Site Collection Contact/Administrator.

o Primary Site Contact of Source – The Primary Site Contact of the source node will be assigned to deal with the task.

o Secondary Site Contact of Source – The Secondary Site Contact of the source node will be assigned to deal with the task.

o Primary Site Contact of Target – The Primary Site Contact of the target node will be assigned to deal with the task.

o Secondary Site Contact of Target – The Secondary Site Contact of the target node will be assigned to deal with the task.

o New Site Contact – The user that takes over the role of Site Contact.

*Note: If you are editing an approval process that has been applied to existing services or site collection policies, and you add unsupported roles to the existing services or site collection policies, a window will appear to remind you that these roles are unsupported when you click Save or Save and Activate. Hover the mouse over the warning ( ) icon to the left of the roles. The names of the services or site collection policies that do not support the roles will be displayed.

If multiple roles are entered, choose the order in which those tasks are assigned from the Order drop-down menu:

o One at a time (serial) – The users of your selected roles must approve one after another. If an approver of one role rejects the request, the approver of next role will not be asked for approval.

65


o All at once (parallel) – The users of all selected roles will be notified at the same time. If an approver of any role rejects the request, the request will be rejected.

*Note: If this approval method is selected, you can further select Allow the approval stage to complete when one approver approves. If one of the selected users approves it, the request will be complete.

• Specify the User – Enter the names of the users you wish to designate as approvers for this stage of the approval process. Press Enter to verify that the names are valid.

If multiple users are entered, choose the order in which those tasks are assigned from the Order drop-down menu:

o One at a time (serial) – The users you have selected must approve one after another. If an approver rejects the request, the next approver will not be asked for approval.

o All at once (parallel) – All selected users will be notified at the same time. If any approver rejects the request, the request will be rejected.

• Specify the AD Group – Enter the names of the AD groups you wish to designate as approvers for this stage of the approval process. Press Enter to verify that the names are valid. Governance Automation will assign the task to the AD groups. If the login user is a member of the AD groups, the task will be displayed in My Tasks interface. The task will be approved once any single member of the AD group approves it.

If multiple AD groups are entered, choose the order in which those tasks are assigned from the Order drop-down menu:

o One at a time (serial) – The AD groups you have entered must approve one after another. When a user of the first group approves the task, the task is assigned to the next group. If a group user rejects the request, the next group will not be asked for approval.

o All at once (parallel) – The task is assigned to all of the entered AD groups. If any group user rejects the request, the request will be rejected.

You can also choose Allow approvers to reassign tasks to others. If the checkbox is selected, the approver can reassign the task to another user.

c. E-mail Settings – Configure settings for e-mail notifications for this approval process. By default, the Notify the approver when the task is assigned checkbox and the Notify the requester when the request is rejected checkbox are selected. You can notify the requester once the request is approved by selecting the Notify the requester when the request is approved checkbox. Select the e-mail template you wish to use for each notification from the corresponding drop-down menu.

*Note: E-mail templates are configured in The E-Mail Template section in Settings.

66


d. Duration and Escalation – Check the Enable Duration and Escalation checkbox to notify the escalation user that the original task has not been handled within the specified amount of time. A task will be assigned to the escalation user to continue the approval process. Make sure that the user receiving the escalated task has the right permissions to handle the task.

• Duration – Enter a positive integer in the Duration text box for the amount of time allowed before the task is escalated, and select either Day(s), Week(s) as the time unit for the duration.

• Escalation – Choose the action that the escalation will trigger from the drop-down menu.

o Notify – The specified user will be notified when the task is escalated. Enter the username in the text box. This user is the person who you want to notify to be responsible for this case. Press Enter to check that the name is valid. This user will be notified once the amount of time specified as the duration passes.

o Re-assign to – The task will be re-assigned to the specified user when the task is escalated. Enter the username in the text box. This user is the person who you want this task to be re-assigned to. Press Enter to check that the name is valid. The task will be re-assigned to this user once the amount of time specified as the duration passes, and this user will receive an e-mail to be notified that the task is re-assigned to him or her.

*Note: The task can only be re-assigned to one user.

You may also specify the role in the text box when creating Clone or Transfer User Permissions, Grant Permissions, and Remove Permissions approval processes.

The roles available vary depending on the type of approval process you are configuring. The following roles may be available:

o Manager Of Approver

o Manager Of Requester

o Manager of Source User

o Manager of Target User

• Select an E-mail Template for the notification sent when this approval task is escalated from the drop-down menu.

9. If more than one approval stage was selected, follow the instructions for Stage One Configurations for the remaining stages.

10. At any time, click the arrow on the left-hand side to return to the previous step to check or modify your configurations. When you have finished, choose one of the following options:

• Click Save to save all of the configurations and return to the Create Approval Process interface.

67


• Click Save and Activate to save all of the configurations and change the status to Active.

• Click Cancel to return to the Create Approval Process interface without saving any changes.

Building Customized Approval Processes To add customized logic into an approval process before or after approval, follow the instructions below:

1. Build a customized DLL file and add to …\AvePoint\GovernanceAutomation\bin.

2. Navigate to …\AvePoint\GovernanceAutomation\config and right-click the Global.config file to open with Notepad.

3. Find the WorkflowEvents node.

4. If you wish to add customized logic into an approval process before approval, find the child node BeforeApproval.

• Modify the value of CustomMethod Enable to true.

• Add the required information as the screenshot shows below.

o Assembly – The corresponding DLL information.

o Type – The class that the called method resides.

o MethodName – The name of the called method. Note that you can only define one parameter here and the type of the parameter and the returned value must be object.

Figure 16: Build customized approval process (1)

• In the AgentProcess node, define the value of AgentProcess Enabled to choose whether to call the EXE file resides in the Agent server. Modify the value of WaitingForFinishing to choose to return the value when the process is finished.

*Note: The EXE file name must be the same as the name of the service for the corresponding request.

*Note: If there are multiple Agents within a farm, make sure that the EXE file exists in each Agent server.

68


Figure 17: Build customized approval process (2)

5. If you wish to add customized logic into an approval process after approval, find the child node AfterApproval and then define the values as shown in BeforeApproval.

*Note: If you modify the value of Enabled to true in the above node, the custom approval process will take effects for all service type approval process.

Configuring Policies To create or manage policies, click Policy in the Administrator landing page, or click Policy Management in the navigation bar.

A policy is an organization-wide set of rules and standards for governing specific SharePoint and DocAve operations. Policies can be applied to services to enable automatic provisioning of SharePoint objects. This allows for greater efficiency in provisioning SharePoint objects as identical SharePoint and DocAve operations can be carried out and repeated by Governance Automation rather than an administrator. This also helps reduce human error since a correctly set policy will apply the same settings to all services associated with that policy. In Policy Management, all of the Governance Automation policies you have configured are displayed in the Site Collection tab and the Content Database tab. You may change the number of policies displayed per page, as well the order they are displayed in. To change the number of policies displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the policies, click the sort ( ) button in a column heading such as Policy, Category, Last Modified Time, and Created By then select Ascending or Descending.

You can customize how the policies are displayed in a number of different ways:

• Search – Find policies based on the keywords entered. The Policy column and the Created By column support to search for the desired policies, and only the content in the column displayed in the current view can be searched.

• Manage columns ( ) – You can manage which columns are displayed in the list so that only information you want to see is displayed. Click the manage columns ( ) button, then select the checkbox next to the column name to have that column shown in the list.


You can perform the following actions in Policy Management:

69


• Create – Click Create on the ribbon to display the Create Policy interface.

• View Details –Click the policy name to see detailed information.

• Edit – Select an inactive policy, and click Edit on the ribbon.

• Delete – Select an inactive policy, and click Delete on the ribbon. A confirmation window will pop up for this deletion. Click OK to delete the selected policy, or click Cancel to return to the Policy Management interface without deleting the selected policy.

• Copy – Duplicate the existing policy to make minor changes in order to save as a new policy. Select a desired policy by selecting corresponding checkbox. Click Copy on the ribbon, and make the desired modifications.

When you have finished making changes, choose one of the following options:

o Click Save to save all of the settings.

o Click Save and Activate to save all of the configurations and activate the policy which means this policy might be used in the service.

o Click Cancel to return to the Policy Management interface without saving any configurations.

• Activate – Select inactive policies, and click Activate on the ribbon to activate them.

• Deactivate – Select active policies, and click Deactivate on the ribbon to deactivate them. Make sure to deactivate all services that use the policies you want to deactivate.

Creating or Editing Site Collection Policies To create a new policy, click Create on the ribbon in the Policy Management interface. You will be brought to the Create Policy interface.

Site Collection policy allows you to customize rules to automatically manage your site collection and integrate DocAve features with the site collection once it is created successfully. Site Collection policies can be used in the Create Site Collection service. Site Collection policies work in conjunction with Site Collection Lifecycle Management services to not only automatically govern site collections associated with each policy, but also empowers business users to easily manage the lifecycle of the site collections they own.

To create a Site Collection policy, click Create on the ribbon in the Site Collection tab. To modify a previously configured policy, select the inactive policy in the Site Collection tab, and click Edit on the ribbon.

*Note: When you click Edit on the ribbon, a pop-up window appears to inform you that changes made to this policy will not take effect on the previously created site collection in which this policy is applied, except for the change to the Enable Site Collection Policy Change option. Click OK to go to the Edit Policy interface, or click Cancel to close the pop-up window.

70


The Create Site Collection policy interface or Edit Policy interface varies for SharePoint on-premises farm and SharePoint Online sites.

• If you select a specific farm in the Farm section to configure Site Collection policies for SharePoint on-premises, refer to Creating or Editing Site Collection Policies for SharePoint On-Premises.

• If you select My Registered Sites in the Farm section to configure Site Collection policies for SharePoint Online sites, refer to Creating or Editing Site Collection Policies for SharePoint Online.

Creating or Editing Site Collection Policies for SharePoint On-Premises In the Create Site Collection policy interface or Edit Policy interface, configure the following settings:

1. Configuring the following basic information for the policy:

• Policy Name and Description – Enter a Name for the new policy. Then enter an optional Description for future reference in the Description text box.

• Policy Category – Categories are used to organize Governance Automation policies. Select an existing category from the drop-down menu or create a new category for this policy by clicking Create New then configuring the new category in the Create Category interface.

• Farm – Select the farm you want this policy to cover from the drop-down menu. The farms displayed here are the ones that are managed by DocAve.

Click the arrow on the right-hand side to continue, or click Cancel to return to the Create Policy interface without saving any configurations.

2. Configure the following SharePoint related settings for the site collections.

• Content Database – Select a database for the policy to store the site collection. Select one of the following options:

o Use default content database – Use the Web application’s default content database to store the newly created site collection. This option will also allow you to select any other existing databases.

*Note: If there are host-named site collections in the selected farm, the host headers of the host-named site collections are displayed in the Host Header column. Select the content database for each host header. When using the host header to create host-named site collections based on this site collection policy, the host-named site collections will be created in the selected content database.

o Generate database automatically – Generate a new database for the site collection automatically each time when creating a new site collection.

o Create a new database – Use an existing database or create a new database depending on the dynamic name rules. Enter the name rule in the Database Name text box.

The name rule as follows:

71


$WebAppSubDomain – Represents the sub domain of the web application.

$WebAppPort – Represents the port of the web application.

$ManagedPath – Represents the managed path of the site collection URL.

$SiteUrl – Represents the relative URL of the site collection.

For example, the URL of the site collection you want to create is http://sp.avepoint.net:8080/sites/dev. Enter SPDB_$WebAppSubDomain_$SiteUrl in the text box. The content database name will be SPDB_sp_dev.

*Note: All site collections created with services associated with this policy will all be using this content database.

o Use content database policy – Select a content database policy and apply the rules in the content database policy to create the content database. Select a previously created content database policy from the drop-down list or click Create New to create a new one in the pop-up window. For more information, refer to Creating or Editing Content Database Policies.

• Site Collection Quota Template – Select a predefined Quota Template for the site collection to limit the amount of storage available on the site collection from the drop-down menu. Quota templates are configured in the SharePoint.

• SharePoint Designer Configuration – Select the Enable SharePoint Designer checkbox to allow Site Owners and Designers to edit the sites in this site collection using SharePoint Designer. Site Collection Administrators will always be able to edit sites regardless of this configuration.

• Site Maximum Depth Limit – Site Depth limits the layers of sites that can be created under a site collection. Select Maximum depth and then enter a positive number which is less than 12 in the provided text box.

• Site Policy Bar (only for SharePoint 2013) – Choose to display the site policy bar on the chrome bar within SharePoint 2013 sites.

*Note: To use this feature, the Governance Automation Policy Bar solution must be deployed to SharePoint. For more information about how to deploy the solution, refer to Deploying the Governance Automation Policy Bar Solution.

After the solution is deployed, select the Display site policy bar within SharePoint sites checkbox and then configure the following settings:

o Policy icon image – Select the image for the policy icon. Click Browse and then select the image file. The following image formats are supported: .gif, .jpg, .png, .bmp, and .tiff.

o Bar background color – Select the background color for the site policy bar.

o Policy details reference URL – Enter the reference URL where users can view details of the policy. Click Validation Test to open the reference URL in a new tab and check whether the URL is valid.

72


*Note: The URL must begin with http://, https://, mailto:, new:, ftp://, file://, /, # or \\.

Click the arrow on the right-hand side to continue. Click the arrow on the left-hand side to go to previous step to check and modify your configurations, or click Cancel to return to the Create Policy interface without saving any configurations.

3. Configure this policy to utilize DocAve products:

• Enable Granular Backup – Select this checkbox to include the site collection in a Granular Backup plan to provide data protection for site collections associated with this policy.

*Note: If this option is enabled, do not activate this policy until you have configured the appropriate filter policy and added it to the selected Granular Backup plan. For more information on how to configure filter policies for DocAve Granular Backup and Restore to provide data protection for site collections created by Governance Automation that are associated with this policy, refer to Configuring Filter Policy to Use DocAve Granular Backup and Restore.

• Activate Connector Content Library Feature – Select this checkbox to have DocAve Content Library enabled so that DocAve Connector can provide users with access to their documents outside of SharePoint. Note that the Connector solution needs to be deployed to the farm covered by this policy.

• Activate Connector Media Library Feature – Select this checkbox to have DocAve Content Library enabled so that DocAve Connector can provide users with access to their multimedia files outside of SharePoint. Note that the Connector solution needs to be deployed to the farm covered by this policy.

• Activate File Share Navigator Feature – Select this checkbox to enables Governance Automation managed site collections to host links to file share content, thereby empowering organizations to leverage SharePoint as the presentation layer for its file shares without using valuable space on SQL Servers.

• Enable site collection content archival using DocAve Archiver – Select this checkbox to allow site collection content to be archived by DocAve Archiver for site collections associated with this policy. You must then select an Archiver Profile. Content will be archived based on the Archiver rule automatically.

If you want the site collection content to be archived after manual approval, rather than being archived automatically based on the Archiver rule, select the Enable manual approval process checkbox and select an approval process to define the approval stage and assignee for manual approval. When there is site collection content that meets the Archiver rule, a manual archive task (which contains a report of all of the content that meets the archive rules) will be generated. The task will be assigned to the approver with a report, allowing the approver to select on the report which content to archive. When the modified report is uploaded and the manual archive task is approved, the selected content will be archived. For more information about the manual archive task, refer to User Permission and Manual Archive Tasks.

For more information on how to configure DocAve Archiver to help reduce storage cost by scheduling site collections created by Governance Automation that are associated

73


with a policy which has this setting enabled to be extracted from SharePoint and stored in more economical storage devices, refer to Appendix B: Configuring DocAve Archiver Profiles.

• Enable Scheduled Storage Manager – Select this checkbox to externalize BLOBs from SQL server database to file-based storage for content in site collections associated with this policy using DocAve Scheduled Storage Manager. Select a Storage Manager Profile for site collections associated with this policy.

*Note: RBS must be enabled as the BLOB provider for the farm selected in this policy, and if you chose not to use the default content database when configuring Content Database for this policy, the Include New Content Database option must be enabled for the BLOB Provider. Since BLOBs are externalized on a schedule, the new database will not be affected until the next time the Storage Manager job is scheduled to run. For details on how to configure Scheduled Storage Manager Profiles and BLOB provider, see the DocAve Storage Manager User Guide.

• Enable Auditing – Select this checkbox to include the site collection into an Audit Controller plan in DocAve Report Center to record all events of site collections associated with this policy.

*Note: If this option is enabled, do not activate this policy until you have configured the appropriate filter policy and added it to the selected Audit Controller plan. For more information on how to configure filter policy, refer to Configuring Filter Policy to Use Audit Controller in DocAve Report Center.

• Enable Policy Enforcer – Select this checkbox to have DocAve Policy Enforcer rules applied to the site collections. Policy Enforcer ensures that all actions and changes to the site collections fall within your previously configured rules by continuously monitoring and taking action on the site collections. Select a Policy Enforcer profile from the drop-down list. For details on how to configure Policy Enforcer profiles, refer to Appendix D: Configuring a Policy Enforcer Profile.

• Enable Dead Account Cleaning – Select this checkbox to include the site collection into a Dead Account Cleaner plan so that the deactivated and non-existent AD accounts can be removed from your site collection and their permissions can be transferred to available users.

*Note: If this option is enabled, do not activate this policy until you have configured the appropriate filter policy and added it to the selected Dead Account Cleaner plan. For more information on how to configure filter policies for DocAve Administrator’s Dead Account Cleaner plans for site collections created by Governance Automation that are associated with this policy, refer to Configuring Filter Policy to Use Dead Account Cleaner in DocAve Administrator.

• Enable Vault for Site Collection Content – Select this checkbox to allow you to export the SharePoint content in this site collection to an external storage system for further management by Autonomy or Concordance platforms.

• Enable Deployment Manager – Select this checkbox to include the site collection into a Deployment Manager plan so that the site collection can be deployed effectively. Select a plan from the drop-down menu.

74


http://www.avepoint.com/assets/pdf/sharepoint_user_guides/Storage_Manager_User_Guide.pdf

*Note: If this option is enabled, do not activate this policy until you have configured the appropriate filter policy and added it to the selected Deployment Manager plan. For more information on how to configure the filter policy and the Deployment Manager plan, refer to Configuring Filter Policy to Use DocAve Deployment Manager and Appendix C: Configuring DocAve Deployment Manager Plans


4. Site Collection Lifecycle Management Request Types – Choose to enable request types for the Site Collection Lifecycle Management service. The request types that you selected in this section will be available for business users in the following situations:

• If the conditions in the Manage Site Collection Lifecycle section are met, the assignee will be able to request for the actions to take effect according to the configurations.

• Business users can submit Site Collection Lifecycle Management service requests for the corresponding site collections based on the enabled request types.

Enable the following request types by selecting the corresponding checkboxes. For each request type, you can choose to Use the default approval process, select a previously created approval process from the drop-down list, or click Create New to create a new approval process.

• Enable site collection content archival using DocAve Archiver – Allows the entire site collection to be moved from SharePoint to an external storage based on the DocAve Archiver profile associated with this policy. Select an Archiver profile from the Profile drop-down list.

For more information on how to configure DocAve Archiver to help reduce storage costs, refer to Appendix B: Configuring DocAve Archiver Profiles.

• Enable deletion of entire site collection – Allows the entire site collection to be deleted upon request.

• Enable extension of site collection lease – Allows the lease of the site collection to be extended upon request.

• Enable site collection policy change – Allows business users to request a different policy for site collections created with this policy.

• Enable site collection unlocking – Allows business users to request for unlocking a locked site collection.

• Enable site collection quota change – Allows business users to request for changing the site collection quota. If enabled, choose one of the following options:

o Allow quota change to all available quota templates –Allows business users to select any one of the available quota template as the new quota template.

o Allow a single level quota upgrade or downgrade – Only the quota template that is larger than the currently used quota template and the quota template that is smaller than the currently used quota template are loaded and available to select in the request.

75


5. Manage Site Collection Lifecycle –Site collection lifecycle management helps reduce the number of unused or expired site collections in your SharePoint environment. Configure the following lifecycle management settings:

• Enable site collection inactivity threshold – Select this checkbox to enable the inactivity threshold for the site collection. If the site collection is not accessed within the amount of time entered here, a task will be assigned to the business user defined in the selected approval process. The business user can choose to extend the site collection lease period, archive the site collection, delete the site collection, or change the site collection policy. Enter a positive integer in the text box and select Day(s), Week(s), Month(s), or Year(s) as a time unit.

Optionally, select Enable automated locking and deletion to lock the site collection after it has passed the inactivity threshold and delete the site collection after it has been locked for the configured locking period.

o Automatically lock the site collection after it has passed inactivity threshold for – After the site collection has passed the inactivity threshold in the amount of time defined here, the site collection will be locked automatically. Enter a positive integer in the text box and select Day(s), Week(s), Month(s), or Year(s) as a time unit.

o Lock status for the site collection – Choose the lock status for the site collection, Adding content prevented, Read-only (blocks additions, updates, and deletions), or No access.

Optionally, you can Notify the primary site collection contact and the secondary site collection contact when the site collection is locked.

o Automatically delete the site collection after it has been locked for – When the site collection has been locked for the specified locking period, the site collection will be deleted automatically. Enter a positive integer in the text box and select Day(s), Week(s), Month(s), or Year(s) as a time unit.

Optionally, you can Notify the primary site collection contact and the secondary site collection contact when the site collection is deleted.

• Enable site collection lease period – Select this checkbox to enable a lease period for the site collection. A site collection lease period is the amount of time a site collection is available for use. When the lease period of the site collection expires, a task will be assigned to the business user defined in the selected approval process. The business user can choose to extend the site collection lease period, archive the site collection, delete the site collection, or change the site collection policy. Configure the site collection lease period by entering a positive integer in the text box and then selecting Day(s), Week(s), Month(s), or Year(s) as a time unit.

Optionally, select Enable automated locking and deletion to lock and delete the site collections according to the specified expiration period and specified locking period.

o Automatically lock the site collection after its lease has expired for – After the site collection’s lease has been expired for the specified time, the site collection will be locked automatically. Enter a positive integer in the text box and select Day(s), Week(s), Month(s), or Year(s) as a time unit.

76




Select an Approval Process from the drop-down menu or click Create New to create a new one. This approval process will be triggered when either of these criteria is met.

• Enable site collection quota threshold – Select this checkbox to enable a quota threshold for the site collection. A site collection quota threshold is the maximum storage space that the site collection can use. If a site collection’s storage reaches the entered percentage of the configured quota, a task will be assigned to the business user defined in the selected approval process. The business user can then change the site collection quota or ignore the quota threshold. Enter your desired value in the text box.

6. Permission Recertification – Choose to enable permission recertification to search site collections’ users and groups on schedule. To run the permission recertification, a report path must be configured. Click the Report Path link provided in the description on the left pane. In the Permission Recertification Report Path window, configure the settings. For more information about how to configure the report path, refer to Creating or Editing Report Export Locations. After the report path configuration is finished, select the Enable permissions recertification checkbox. If permission recertification is enabled, a permission recertification task will be generated, which contains the searched permissions of users and groups. Approvers can then modify the permissions in Governance Automation and the permission changes will be updated to SharePoint.

• Include Active Directory group members or Form-based Authentication role members – Choose to search Active Directory group members or Form-based Authentication role members.

• Configure the schedule to search for permissions: Daily, Weekly, or Monthly.

• Select an Approval Process from the drop-down menu or click Create New to create a new one.

*Note: Permission recertification is not supported for My Site.

*Note: If permission recertification is enabled but the site collection does not have an administrator contact, you must configure an alternate administrator contact in Settings > Administrator Notification. Otherwise, no error task and permission recertification task will be generated if any errors occur while searching users and groups of the site collection.

*Note: AvePoint recommends that you back up your permission recertification report path for disaster recovery purposes.

7. When you have finished configuring this policy, choose one of the following options:

• Click the arrow on the left-hand side to go to the previous step to check and modify your configurations.

77


• Click Save to save all of the configurations and return to the Create Policy interface.

• Click Save and Activate to save all of the configurations and activate the policy, which allows this policy to be used in services.

• Click Cancel to return to the Create Policy interface without saving any changes.

Creating or Editing Site Collection Policies for SharePoint Online In the Create Site Collection policy interface or Edit Policy interface, configure the following settings:

1. Policy Name and Description – Enter a Name for the new policy. Then enter an optional Description for future reference in the Description text box.

2. Policy Category – Categories are used to organize Governance Automation policies. Select an existing category from the Use an existing category drop-down menu or create a new category for this policy by selecting Add a new category then entering a name for this new category.

3. Farm – Select My Registered Sites from the drop-down menu.

4. Select SharePoint Online standard instance or SharePoint Online dedicated instance.

5. Click the arrow on the right-hand side to continue, or click Cancel to return to the Create Policy interface without saving any configurations.

6. Quota (for SharePoint Online standard instance) – Enter the storage quota and server resource quota for the site collection.

7. Site Collection Quota Template (for SharePoint Online dedicated instance) – Select a previously defined quota template for the site collection from the drop-down menu to limit the amount of storage available on the site collection.

8. SharePoint Designer Configuration – Select the Enable SharePoint Designer checkbox to allow Site Owners and Designers to edit the sites in this site collection using SharePoint Designer. Site Collection Administrators will always be able to edit sites regardless of this configuration.

9. Site Maximum Depth Limit – Site Depth limits the layers of sites that can be created under a site collection. Select Maximum depth and then enter a positive number which is less than 12 in the provided text box.

10. DocAve Configurations Configure this policy to utilize DocAve 6 product:

• Enable Granular Backup – Select this checkbox to include the site collection in a Granular Backup plan to provide data protection for site collections associated with this policy.

*Note: If this option is enabled, do not activate this policy until you have configured the appropriate filter policy and added it to the selected Granular Backup plan. For more information on how to configure filter policies for DocAve Granular Backup and Restore to provide data protection for site collections created by Governance Automation that are associated with this policy, refer to Configuring Filter Policy to Use DocAve Granular Backup and Restore.

78



8. Site Collection Lifecycle Management Request Types – Choose to enable request types for the Site Collection Lifecycle Management service. The request types that you select in this section will be available for business users in the following situations:

• When the conditions in the Manage Site Collection Lifecycle section are met, the assignee will be able to request for the actions to take effect according to the configurations.

• Business users can submit Site Collection Lifecycle Management service requests for the corresponding site collections based on the enabled request types.

Enable the following request types by selecting the corresponding checkboxes. For each request type, you can choose to Use the default approval process, select a previously created approval process from the drop-down list, or click Create New to create a new approval process.

• Enable deletion of entire site collection – Allows the entire site collection to be deleted upon request.

• Enable extension of site collection lease – Allows the lease of the site collection to be extended upon request.

• Enable site collection policy change – Allows business users to request a different policy for site collections created with this policy.

• Enable site collection quota change – Allows business users to request for changing the site collection quota.

If you select SharePoint Online dedicated instance in step 4, choose one of the following options:

o Allow quota change to all available quota templates –Allows business users to select any one of the available quota template as the new quota template.

o Allow a single level quota upgrade or downgrade – Only the quota template that is larger than the currently used quota template and the quota template that is smaller than the currently used quota template are loaded and available to select in the request.

If you select SharePoint Online standard instance in step 4, you can set the maximum quota size that can be requested. Enter your desired quota size in the text box. The unit of the quota size is MB.

9. Manage Site Collection Lifecycle –Site collection lifecycle management help reduce the number of unused or expired site collections in your SharePoint environment. Configure the following lifecycle management settings:

• Enable site collection inactivity threshold – Select this checkbox to enable the inactivity threshold for the site collection. If the site collection is not accessed within the amount of time entered here, a task will be assigned to the business user defined in the selected approval process. The business user can choose to extend the site collection lease

79


period, archive the site collection, delete the site collection, or change the site collection policy. Enter a positive integer in the text box and select Day(s), Week(s), Month(s), or Year(s) as a time unit.

Optionally, select Enable automated locking and deletion to lock and delete the site collections according to the specified period beyond inactivity threshold and specified locking period.

o Automatically lock the site collection after it has passed inactivity threshold for – After the site collection has passed the inactivity threshold in the amount of time specified here, the site collection will be locked automatically. Enter a positive integer in the text box and select Day(s), Week(s), Month(s), or Year(s) as a time unit.


Optionally, you can Notify the primary site collection contact and the secondary site collection contact when the site collection is locked.


Optionally, you can Notify the primary site collection contact and the secondary site collection contact when the site collection is deleted.

• Enable site collection lease period – Select this checkbox to enable a lease period for the site collection. A site collection lease period is the amount of time a site collection is available for use. When the lease period of the site collection expires, a task will be assigned to the business user defined in the selected approval process. The business user can choose to extend the site collection lease period, archive the site collection, delete the site collection, or change the site collection policy. Configure the site collection lease period by entering a positive integer in the text box and then selecting Day(s), Week(s), Month(s), or Year(s) as a time unit.

Optionally, select Enable automated locking and deletion to lock and delete the site collections according to the specified expiration period and specified locking period.

o Automatically lock the site collection after its lease has expired for – After the site collection’s lease has been expired for the specified time, the site collection will be locked automatically. Enter a positive integer in the text box and select Day(s), Week(s), Month(s), or Year(s) as a time unit.


o Automatically delete the site collection after it has been locked for – When the site collection has been locked for the specified locking period, the site

80


collection will be deleted automatically. Enter a positive integer in the text box and select Day(s), Week(s), Month(s), or Year(s) as a time unit.

Select an Approval Process from the drop-down menu or click Create New to create a new one. This approval process will be triggered when either of these criteria is met.

• Enable site collection quota threshold – Select this checkbox to enable a quota threshold for the site collection. A site collection quota threshold is the maximum resources that the site collection can use. If a site collection’s storage reaches the entered percentage of the configured quota, a task will be assigned to the business user defined in the selected approval process. The business user can then change the site collection quota. Enter your desired value in the text box.

11. When you have finished configuring this policy, choose one of the following options:

• Click the arrow on the left-hand side to go to the previous step to check and modify your configurations.

• Click Save to save all of the configurations and return to the Create Policy interface.

• Click Save and Activate to save all of the configurations and activate the policy, which allows this policy to be used in services.

• Click Cancel to return to the Create Policy interface without saving any changes.

Creating or Editing Content Database Policies Content database policies allow you to configure rules to automatically govern your content databases. The maximum database size and the maximum number of site collections that can exist in a content database are set in content database rules. You can also define the new content database naming format to decide how to generate new content databases if the maximum database size or site collection count will be exceeded. Content database policies can be used in site collection policies.

To create a content database policy, click Create on the ribbon in the Content Database tab. To modify a previously configured policy, select the policy in the Content Database tab, and click Edit on the ribbon.

In the Create or Edit Content Database Policy interface, configure the following settings:

1. Policy Name and Description – Enter a Name for the new policy and an optional Description for future reference.

2. Policy Category – Categories are used to organize Governance Automation policies. Select an existing category from the drop-down menu or create a new category for this policy by clicking Create New then configuring the new category in the Create Category interface.

3. Content Database Rules – Configure the rules to manage your content databases. A new content database will be created if the maximum database size or the maximum number of site collections will be exceeded.

a. Maximum database size – Select this checkbox and enter a positive number that will be set as the maximum database size. The unit is GB.

81


b. Maximum number of site collections – Select this checkbox and enter a positive integer as the maximum number of site collections that are allowed to exist in a content database.

c. New content database naming format – Define the naming format for the new content database. Enter a prefix in the textbox. The prefix must contain the role of $webappname. The role of $webappport is supported but optional. Note that the role name is not case sensitive. The new content database will be created with a suffix of 0001, 0002, 0003…

4. Database Contact – Enter a user to be the content database contact. The user should be a database administrator who will be responsible for managing the content database according to the content database policy. Then, select an e-mail template that will be used to notify the database contact when a task is assigned. By default, Built-in Content Database Policy Threshold Warning E-mail Template is selected. You can choose Notify the requester when the request is rejected and select an e-mail template for the notification. By default, Built-in Request Denied E-mail Template is selected.

5. Click Save on the ribbon to save your configurations, or click Cancel to go back to the Content Database tab without saving any configurations.

Configuring Services A service is a set of configured settings for a management operation in SharePoint that can be leveraged by business users when submitting a service request. For example, a Create Site Collection service provides the site collection template, security settings, lifecycle management, and other settings for the site collections that will be created by this service. Administrators can limit what options are available to Business Users based on the standards of practice of the organization.

To create or manage services, click Service in the Administrator landing page, or click Service Management in the side bar.

In Service Management, all of the Governance Automation services you have configured are displayed. You may change the number of services displayed per page, as well the order they are displayed in. To change the number of services displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the services, click in a column heading such as Service, Service Type, Category, Last Modified Time, and Created By then select Ascending or Descending.

You can customize how the services are displayed in a number of different ways:

• Search – Allows you to filter services displayed by the keyword you designate. The Service column and the Created By column support to search for the desired services, and only the content in the column displayed in the current view can be searched.

• – You can manage which columns are displayed in the list so that only information you want to see is displayed. Click , and then select the checkbox next to the column name to have that column shown in the list.

82


• – This allows you to filter which item in the list is displayed. Click the of the column you want to filter, then select the checkbox next to the item name to have that item shown in the list.

You can perform the following actions in Policy Management:

• Create – Click Create on the ribbon to display the Create Service interface.

• View Details – Click a service name to see the detailed information.

• Edit – Select an inactive service, and click Edit on the ribbon.

• Copy – Duplicate an existing service to make minor changes in order to save as a new service. Select a desired service by selecting corresponding checkbox. Click Copy on the ribbon, and enter the related information required. When completing the configurations, click Save to save all of the settings or click Save and Activate to save all of the configurations and activate this service which makes this service available to be requested. Click Cancel to return to the Service Management interface without saving any configurations.

• Delete – Select an inactive service, and click Delete on the ribbon. A confirmation window will pop up for this deletion. Click OK to delete the selected service, or click Cancel to return to the Service Management interface without deleting the selected service.

• Activate – Select the services you want to activate and click Activate on the ribbon. Active services are available to be requested.

• Deactivate – Select the services you want to deactivate and click Deactivate on the ribbon. Inactive services will not be seen by users and cannot be requested.

To create a new service, click Create Service in the landing page or click Create on the ribbon of the Service Management interface. You will be brought to the Create Service page. Select a service type to create the new service using the corresponding template. To make changes to an existing service, select the service by clicking before a service name in the Service Management interface, and then click Edit on the ribbon.

Instructions on creating and editing each type of service are provided in the sections below.

Create Site Collection Service Configure Create Site Collection services to define the Create Site Collection service request template for business users. You can customize the settings for site collections created by this service as well as configure available options for business users to choose from when requesting this service. Create Site Collection services also allow you to apply data protection and content retention policies on the site collections with full auditing to monitor compliance with your corporate standards.

*Note: With Governance Automation, you can create site collections in SharePoint on-premises and SharePoint Online.

In the Create Site Collection Service interface or Edit Create Site Collection Service interface, configure the following settings:

83


1. Service Name and Description – Enter a Name for the service and an optional Description for future reference.

2. Language – Choose the language for this service. When starting a request, you can filter the services according to their languages.

3. Service Category – Categories are used to organize your Governance Automation services. Select an existing category from the drop-down menu or create a new category for this service by clicking Create New then configuring the new category in the Create Category interface.

4. Department – Departments help organize services as well as provide essential Governance Automation reporting information for sorting and understanding your organization’s SharePoint usage. Select a Department you wish this service to belong to from the drop-down menu or click Create New to create a new one.

Choose to assign a department to this service and site collections created by this service or allow the business user to choose the Department when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Department selected in the preceding drop-down menu will be associated with all site collections created by this service. Select Show as Read-Only to Business User to allow the business users to see the default department in the service request or Hide from Business User to not display the department associated with this service to the business users requesting this service.

• Assign by Business User – Allows business user to choose the department when submitting a service request for this service.

5. Service Permissions – Choose Allow all users to use this service to allow this service to be requested by any user, or specify the users or groups that have permissions to access this service by choosing Select users/groups to use this service and enter the username of the users/groups in the text box. Press Enter to check that the names are valid.

• Select Hide this service from the catalog for authorized users but make available via a questionnaire to hide this service from the service catalog even if the users are listed in the permission above, but to make it available via a questionnaire. The users that have permission to access the questionnaire and that are listed in the permission above can view the service after they finish answering the questionnaire.

• Select Allow all users to access this service through a questionnaire even if the users are not listed above to allow users with permission to the questionnaire to access this service via a questionnaire even if the users are not listed in the permission above.

6. Service Contact – Specify a user to be the Service Contact. This should be a business user who is the owner of the business process for this service. Enter the username in the Service Contact text box. Press Enter to check that the name is valid.

7. Administrator Contact –Specify a user to be the Administrator Contact. This user should be an administrator of Governance Automation and is responsible for service management. Governance Automation will assign a task to the Administrator Contact when an error occurs after the approval process starts. Enter a username in the Administrator Contact text box. Press Enter to check that the name is valid. To also have an e-mail notification be sent to the Administrator Contact when this service encounters an error, configure the Administrator

84


Notification section of Settings. For more information on how to configure the Administrator Notification, see Configuring Administrator Notifications.

8. Click the arrow on the right-hand side to proceed to the next step.

9. Web Applications and Managed Paths – Specify the Web applications and associated managed paths where you wish to create a site collection.

*Note: To create site collections in SharePoint Online standard instance, you must register SharePoint Online admin centers in DocAve first. For details, refer to Registering SharePoint Online Admin Centers/Site Collections.

a. Select the Show host headers checkbox to display the host headers with a farm.

b. Select a farm or My Registered Sites from the drop-down menu. Expand the tree to select the desired Web applications, SharePoint Online admin centers or host headers, and managed paths by selecting the corresponding checkboxes. If host headers are selected, the business users are allowed to create host-named site collections in the requests. Select a default Web application or admin center and managed path for the site collection you wish to create by selecting one from the drop-down menus under the tree. You can select multiple Web applications or admin centers then use the Default Selection drop-down menu to designate the default location for new site collections created by this service.

c. URL format – Select the Automatically generate URL checkbox to have Governance Automation generate the URL, or leave it unchecked to allow the requester to decide the URL.

Choose to assign a the Web application and Managed Paths for this service and site collections created by this service or allow the business user to choose the Web application and Managed Paths when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Web Application and Managed Paths configured here will be made available for business users to select from. Select Show as Read-Only to Business User to allow the business users to see the default Web Application and Managed Path in the service request or Hide from Business User to not display the Web Application and Managed Path associated with this service to the business users requesting this service.

• Assign by Business User – Allows business user to choose the Web Application and Managed Path when submitting a service request for this service.

d. Site collection URL – Choose to use site collection title in URL or use SharePoint context in service request scope.

• Use site collection title in URL – Select this checkbox to have the site collection URL be filled automatically after entering the site collection title in the service request.

• Use SharePoint context to automatically populate the service request scope – Select this checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL

85


will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format: https://servername:port/Request/NewSCRequest?serviceId={serviceID}&parent={parentsiteURL}.

10. Policy – Select the site collection policies to provision the site collections created by this service by selecting the corresponding checkboxes or click Create New to be brought to the Site Collection Policy interface to create a new policy. Configure this section as follows:

a. Select the policies to be made available for business users to choose from by selecting the corresponding checkbox of each policy in the Select Policies configuration area. All policies selected here will be made available to business users if you select Assign by Business User in the Assign by drop-down menu. If no existing policy is appropriate for this service, you may click Create New to create a new one.

*Note: If you select a SharePoint Online standard instance node or SharePoint Online dedicated instance node in the scope, the policies for both instances are loaded. Make sure you select the proper policies; otherwise an error task will be generated after approving the request for this service.

b. Select a default policy in the Default Selection drop-down menu. If Assign by Business User is selected in the Assign by drop-down menu, this policy will be selected in the service request, but the business user will be able to select another policy out of the policies you have selected in the Select the Policies configuration area. If Assign by IT Admin is selected in the Assign by drop-down menu, this will be the only available policy in the service request and the business user will not be able to choose another policy.

Choose to assign a policy to site collections created by this service or allow the business user to choose the policy when submitting a service request for this service from the policies selected in the Select the Policies configuration area. Choose from the following:

• Assign by IT Admin – The policy selected in the Default Selection drop-down menu will be associated with all site collections created by this service. Select Show as Read-Only to Business User to allow the business users to see the default policy in the service request or Hide from Business User to not display the policy associated with this service to the business users requesting this service.

• Assign by Business User – Allows business user to choose from the policies you have selected in the Select the Policies configuration area.

11. Language (This option is only available if you have language packs installed on the Web server) - Specify the language for the site collection. If more than one language is selected, choose a default language from the Default Selection drop-down menu.

• Choose to assign a language to site collections created by this service or allow the business user to choose the language when submitting a service request for this service from the languages selected in the Select Language configuration area. Choose from the following:

86


o Assign by IT Admin – The language selected in the Default Selection drop-down menu will be associated with all site collections created by this service. Select Show as Read-Only to Business User to allow the business users to see the default language in the service request or Hide from Business User to not display the language to the business users requesting this service.

o Assign by Business User – Allows business user to choose from the languages you have selected in the Select Language configuration area.

12. Experience Version (This option is only available when you select SharePoint 2013 Web applications or SharePoint Online Sites in Web Applications and Managed Paths) – Select the experience version (2010 or 2013) for the site collections that business users will create.

• Choose to assign the experience version to site collections created by this service or allow the business user to choose the experience version when submitting this service request. Choose from the following:

o Assign by IT Admin – Governance Automation will apply the experience version selected here to all site collections created using this service. Select Show as Read-Only to Business User to allow the business users to see the selected experience version in the service request or Hide from Business User to not display the experience version to the business users requesting this service.

o Assign by Business User – Allows business user to select the experience version when submitting a service request for this service.

13. Site Collection Template – Specify the site collection template to use for site collections created by this service. Configure this section as follows:

a. Select the site collection templates to be made available for business users to choose from by selecting the corresponding checkbox of each site collection template in the Select templates configuration area. All site collection templates selected here will be made available to business users if you select Assign by Business User in the Assign by drop-down menu.

b. Select the default site collection template in the drop-down menu. If Assign by Business User is selected in the Assign by drop-down menu, this site collection template will be selected in the service request, but the business user will be able to select another template out of the templates you have selected in the Select the templates configuration area. If Assign by IT Admin is selected in the Assign by drop-down menu, this will be the only available template in the service request and the business user will not be able to choose another template.

Choose to assign a site collection template to site collections created by this service or allow the business user to choose the site collection template when submitting a service request for this service from the templates selected in the Select the templates configuration area. Choose from the following:

• Assign by IT Admin – The site collection template selected in the Default Selection drop-down menu will be associated with all site collections created by this service. Select Show as Read-Only to Business User to allow the business users to see the default site collection template in the service request or Hide from Business User to not

87


display the site collection template associated with this service to the business users requesting this service.

• Assign by Business User – Allows business user to choose from the site collection templates you have selected in the Select the templates configuration area.


15. Security Groups – Customize the permissions for site collections created by this service:

• The Common tab – Configure the common permission settings to assign permissions to specific groups and users. By default, the common groups are displayed. Click the edit ( ) button to edit the settings of a group or click the delete ( ) button to delete a group.

o Create Group – Click Create Group to create a new group and add it into the common permission settings. In the Add a Group window, configure the following settings:

a. Custom Group Name – Enter a name for the group and enter an optional description for future reference. Enter $SiteName to automatically add the site collection tile as the group name prefix in Create Site Collection service request.

b. Assign By – Choose who will assign the group settings, IT Admin or Business User.

c. Select Users – Select your desired users to add into the group. Click Add a User and enter the usernames in the pop-up window. You can also enter $ to select the following roles: $Requester, $ManagerOfRequester, $PrimarySiteCollectionContact, and $SecondarySiteCollectionContact. Then, click OK to save your configurations.

Optionally, select the Enforce Permission checkbox after a username. In the request page, the user cannot be deleted and the user permissions cannot be modified. For the enforced permission user, you can hide the enforced permission user from the request page by selecting the Hide checkbox.

d. Permissions – Configure the permissions for this group. Select your desired permission levels by selecting the corresponding checkboxes.

Optionally, select the Allow Business User to change the permission level of this group checkbox, so that the business users can modify the permission level when creating a request.

e. Click OK to save the group settings.

o Grant Permissions – Click Grant Permissions to grant permissions to specific users. In the Grant User Permissions window, configure the following settings:

a. Select Users – Enter the names of the users that you are about to grant permissions.

88


b. Assign By – Choose who will assign the user permissions, IT Admin or Business User.

c. Permissions – Configure the permissions for the users. Select your desired permission levels by selecting the corresponding checkboxes.

d. Click OK to save your configurations.

• The specific template tab – The template tab depends on the selected site collection template. The default groups of the site collection template are displayed. Click the edit ( ) button to edit the settings of a specific group or click the delete ( ) button to delete a specific group.

o Use common permission settings – Select the checkbox to apply the permission settings in the Common tab. If there are group names that already exist in the Common tab, the group settings will be replaced by those of the Common tab.

o Create Group – Click Create Group to create a new group and add it into the common permission settings. In the Add a Group window, configure the following settings:

a. Custom Group Name – Enter a name for the group and enter an optional description for future reference.







o Grant Permissions – Click Grant Permissions to grant permissions to specific users. In the Grant User Permissions window, configure the following settings:


89





• Reset All – Click Reset All to clear your configurations and reset all configured security groups settings to the initial state.

• Business User action control – choose how to control the business user actions on the security group.

o Allow Business User to grant user permissions directly – Select this checkbox to allow business users to directly grant permissions to specific users in the request.

o Prevent Business User from requesting to grant permissions with the following permission levels – Select this checkbox and select your desired permission levels. The selected permission levels will not be displayed in the request.


17. Primary Site Collection Administrator – Assign a user to be the Primary Site Collection Administrator by entering the username into the text box. Press Enter to check that the name is valid.

Choose to assign the Primary Site Collection Administrator to site collections created by this service or allow the business user to choose the Primary Site Collection Administrator when submitting a service request for this service. By default, it is Assign by IT Admin and Hide from Business User. Choose from the following:

• Assign by IT Admin – The Primary Site Collection Administrator configured here will be associated with all site collections created by this service. Select Show as Read-Only to Business User to allow the business users to see the Primary Site Collection Administrator in the service request or Hide from Business User to not display the Primary Site Collection Administrator associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Primary Site Collection Administrator.

18. Secondary Site Collection Administrator (only for SharePoint on-premises site collections and SharePoint Online dedicated instance site collections) – Assign a user to be the Secondary Site Collection Administrator by entering the username into the text box. Press Enter to check that the name is valid.

Choose to assign the Secondary Site Collection Administrator to site collections created by this service or allow the business user to choose the Secondary Site Collection Administrator when submitting a service request for this service. By default, it is Assign by IT Admin and Hide from Business User. Choose from the following:

90


• Assign by IT Admin – The Secondary Site Collection Administrator configured here will be associated with all site collections created by this service. Select Show as Read-Only to Business User to allow the business users to see the Secondary Site Collection Administrator in the service request or Hide from Business User to not display the Secondary Site Collection Administrator associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Secondary Site Collection Administrator.

19. Primary Site Collection Contact – The Primary Site Collection Contact will be the user designated for managing the lifecycle of the site collection created by this service. Assign a user to be the Primary Site Collection Contact by entering the username into the text box. Press Enter to check that the name is valid

Choose to assign the Primary Site Collection Contact to site collections created by this service or allow the business user to choose the Primary Site Collection Contact when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Primary Site Collection Contact configured here will be associated with all site collections created by this service. Select Show as Read-Only to Business User to allow the business users to see the Primary Site Collection Contact in the service request or Hide from Business User to not display the Primary Site Collection Contact associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Primary Site Collection Contact.

You can also send an e-mail to notify the Primary Site Collection Contact when the site collection is created successfully. Select the Notify the contact upon site collection creation checkbox and select an e-mail template from the drop-down list. By default, Built-in New Object Notification E-mail Template is selected.

20. Secondary Site Collection Contact – The Secondary Site Collection Contact will be the user designated for managing the lifecycle of the site collection created by this service if the Primary Site Collection Contact is unable to respond to a notification. Assign a user to be the Secondary Site Collection Contact by entering the username into the text box. Press Enter to check that the name is valid.

Choose to assign the Secondary Site Collection Contact to site collections created by this service or allow the business user to choose the Secondary Site Collection Contact when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Secondary Site Collection Contact configured here will be associated with all site collections created by this service. Select Show as Read-Only to Business User to allow the business users to see the Secondary Site Collection Contact in the service request or Hide from Business User to not display the Secondary Site Collection Contact associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Secondary Site Collection Contact.

91


You can send an e-mail to notify the Secondary Site Collection Contact when the site collection is created successfully. Select the Notify the contact upon site collection creation checkbox and select an e-mail template from the drop-down list. By default, Built-in New Object Notification E-mail Template is selected.


22. DocAve Deployment Manager Plan – Select a deployment plan from the drop-down menu to add site collections created by this service to a DocAve Deployment Manager plan. A copy of the plan will be created for each new site collection in order to run the job, and will be deleted once the job completes to prevent unnecessary data storage.

*Note: The deployment plan must not have a schedule set up in order for Governance Automation to run the deployment job when the site collection is created.

23. Manage Site Collection Lifecycle – Select the Enable Site Collection Lease Period checkbox to enable a lease period for the site collection. Specify the lease period by entering a positive integer in the provided text box and choose Day(s), Week(s), Month(s), or Year(s) from the drop-down menu

Choose to assign the site collection lease period to site collections created by this service or allow the business user to choose the site collection lease period when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The site collection lease period configured here will be associated with the site collection created by this service. Select Show as Read-Only to Business User to allow the business users to see the site collection lease period in the service request or Hide from Business User to not display the site collection lease period associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the site collection lease period.

When the site collection lease period is enabled, you can choose to enable lease expiration warning to configure when to send the warning e-mail before the site collection reaches expiration by selecting the Enable lease expiration warning checkbox. Then enter a positive integer in the provided text box and choose Day(s), Week(s), Month(s), or Year(s) from the drop-down menu.

Choose to assign the lease expiration warning to site collections created by this service or allow the business user to choose the lease expiration warning when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The lease expiration warning configured here will be associated with the site collection created by this service. Select Show as Read-Only to Business User to allow the business users to see the lease expiration warning in the service request or Hide from Business User to not display the lease expiration warning associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the lease expiration warning.

24. Governance Automation App and App Parts – Choose to automatically enable Governance Automation App during site collection creation. If enabling this feature, first make sure that the

92


Governance Automation App has been properly deployed to your farm. For more information about the environment configuration and deployment, refer to Installing the Governance Automation App. If you choose Automatically enable Governance Automation App, you can also automatically add Governance Automation app part Site Information Card into the homepage of the site collection that will be created by this service. Select the Automatically add Governance Automation app parts into the homepage checkbox and then select the Site Information Card checkbox.

25. Metadata – Select the metadata to be made available to users when submitting a request for this service. Click the Add Metadata hyperlink to display the Add Custom Metadata window. In the Add Metadata popup window:

• Select the desired metadata by clicking before a metadata name. The metadata displayed here is configured in the Metadata interface. You can also click Create on the ribbon to go to the Create Metadata interface. For information on configuring Metadata, see Configuring Metadata.

• Click View Details on the ribbon to see the detailed information of the selected metadata.

• Click OK to save all of the configurations and return to the service creation page. Click Cancel to return to the service creation page without saving any changes.


27. Approval Process– Select an approval process from the drop-down menu or click Create New to create a new approval process. This will bring you to the Approval Process Settings interface without saving any of the configurations you have made for this service. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.

Optionally, select the Allow all approvers to edit this service request checkbox to allow all of the approvers to edit the service request for this service when viewing the service request. You can Notify the requester when the service request is edited by selecting the checkbox and then selecting an E-mail template.

If the selected approval process integrates with an external workflow, you can also choose to Synchronize service request information from SharePoint list item after the approval. With this checkbox selected, the service request information that is updated in SharePoint list item will be synchronized to Governance Automation after the approval is completed.

28. Custom Action – Allows you to modify the approval process. Choose the desired custom action Before approval, After approval, and After execution by using an executable file, PowerShell script file, or assembly. Select the corresponding checkboxes and enter the required information.

• Executable file (.exe) – Enter the executable file name in the text box.

• PowerShell script file (.ps1) – Enter the PowerShell script file name in the text box.

93


• Assembly (.dll) – Enter Assembly name, Namespace.class, and Method in the corresponding text boxes.

*Note: If the selected scope is in a SharePoint on-premises farm, make sure that the executable file and PowerShell script file exist in the DocAve Agent Directory …\Agent\bin\GovernanceAutomation and the assembly file exists in the Governance Automation Directory …\AvePoint\GovernanceAutomation\bin. If the selected scope is in SharePoint Online standard instance or SharePoint Online dedicated instance, make sure that the executable file, the PowerShell script file, and the assembly file exist in the Governance Automation Directory …\AvePoint\GovernanceAutomation\bin.

29. Execution Schedule – Select Enable service request execution schedule to define when Governance Automation executes the service request. Then, choose a previously configured execution schedule from the drop-down menu or click Create New to create a new one.

30. Schedule Date – Select Enable requesters to schedule the request execution date to allow business users to configure a schedule date to execute the service request for this service.

• Allow business users to override IT Admin’s execution schedule (This section only appears when Enable service request execution schedule is selected) – If Enable service request execution schedule is selected in the Execution Schedule section, you can allow business users to override the execution schedule selected by the IT Admin and define their own scheduled request execution time.

• Notify the approvers about upcoming scheduled request in advance by – Choose to send an e-mail to notify the approvers in advance when it reaches a specified time. If Notify the approvers about upcoming scheduled request in advance by is selected, enter a positive integer in the text box and select Day(s) or Week(s) from the drop-down list. Then, select an E-mail Template for the notification sent to the approvers.

31. When you have finished configuring settings for this service, choose one of the following options:

• Click the arrow on the left-hand side to go to the previous steps to review and modify your configurations.

• Click Save to save all of the configurations and return to the Create Service interface.

• Click Save and Activate to save all of the configurations and activate this service, which allows users to submit requests for this service.

• Click Cancel to return to the Create Service interface without saving any configurations.

Create Site Service Configure Create Site services to define the Create Site service request template for business users. You can customize the settings for sites created by this service as well as configure available options for business users to choose from when requesting this service. Sites created by Governance Automation inherit data protection and content retention policies from the site collection they live in. Sites created by Governance Automation use the same DocAve Granular Backup and Recovery, DocAve Connector, DocAve Archiver and lifecycle management settings as the site collections they are created in.

94


In the Create Site Service interface or Edit Create Site Service interface, configure the following settings:





Choose to assign a department to this service and sites created by this service or allow the business user to choose the department when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – Thedepartment selected in the preceding drop-down menu will be associated with all sites created by this service. Select Show as Read-Only to Business User to allow the business users to see the default department in the service request or Hide from Business User to not display the department associated with this service to the business users requesting this service.


5. Service Permissions – Choose Allow all users to use this service to allow this service to be requested by any user, or specify the users or groups that have permissions to access this service by choosing Select users/groups to use this service and enter the names of the users/groups in the text box. Press Enter to check that the names are valid.


• Select Allow all users to access this service through a questionnaire even if the users are not listed above to allow users with permission to the questionnaire to access this service via a questionnaire even if the users are not listed in the permission above.


7. Administrator Contact – Specify a user to be the Administrator Contact. This user should be an administrator of Governance Automation and is responsible for service management. Governance Automation will assign a task to the Administrator Contact when an error occurs after the approval process starts. Enter a username in the Administrator Contact text box. Press

95


Enter to check that the name is valid. To also have an e-mail notification be sent to the Administrator Contact when this service encounters an error, configure the Administrator Notification section of Settings. For more information on how to configure the Administrator Notification, see Configuring Administrator Notifications.


9. Scope – Choose the site collections you wish to be made available in this service. Business users will be able to choose which site collection to create the new site under.

a. Select a farm or My Registered Sites from the drop-down menu.

b. Choose one of the following methods to configure the scope:

• Manually input URL - Select this radio button and click the Add Your Own URL link to enter the URL of the site collection in the URL text box. To add more site collections click Add Your Own URL after entering a URL.

• Select scope from tree – Select this radio button and then select the site collections from the data tree.

Optionally, select Enable security trimming in the tree of the request for this service to only allow requesters to view the node that they have permissions to access in the scope tree.

*Note: Selecting this option may increase the time it takes to load the tree in the request.

c. Site URL – Choose to use site title in URL or use SharePoint context in service request scope.

• Use site title in URL – Select this checkbox to have the site URL be filled automatically after entering the site title in the service request.

• Use SharePoint context to automatically populate the service request scope – Select this checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format: https://servername:port/ProvSSRequest/NewRequest?serviceId={serviceID}&parent={parentsiteURL}.

10. Language (This option is only available if you have language packs installed on the Web server) – Specify the language for the sites. If more than one language is selected, choose a default language from the Default Selection drop-down menu.

Choose to assign a language to sites created by this service or allow the business user to choose the language when submitting a service request for this service from the languages selected in the Select Language configuration area. Choose from the following:

96


• Assign by IT Admin – The language selected in the Default Selection drop-down menu will be associated with all site collections created by this service. Select Show as Read-Only to Business User to allow the business users to see the default language in the service request or Hide from Business User to not display the language to the business users requesting this service.

• Assign by Business User – Allows business user to choose from the languages you have selected in the Select Language configuration area.

11. Site Template – Specify the templates which can be used to create the site. In the Template store text box, enter the site collection URL where all of your site templates are centrally stored. Then click Retrieve to retrieve the available templates and select the desired templates by selecting corresponding checkboxes. Select a template as the default template from the drop-down menu in the Default Selection section.

You can choose this entry is predefined by an administrator for the service request or is assigned by a business user while submitting a service request from the drop-down menu.

• Assign by IT Admin – An administrator determines which templates can be used for the site. Select whether the template information is visible to the business users. Show as Read-Only to Business User means business users can only see the template configured in the Default Selection when submitting a service request but they cannot change it. Hide from Business User means business users cannot see which template is used for creating the site in the service request.

• Assign by Business User – Allows the business user to determine which templates can be used to create a site. The selected template in the Default Selection will be displayed as a default value of this entry in the service request and the business user can change it to other template when submitting a service request.


13. Security Groups – Select to inherit permissions from parent site or use the unique permissions.

• Use same permissions as parent site – Select the Use same permissions as parent site to inherit the parent site’s permissions settings. Assign by IT Admin will be the default selection for the Assign by drop-down menu. Choose to Show as Read-Only to Business User or Hide from Business User.

• Use unique permissions – Select the Use unique permissions checkbox and customize the site permissions for sites created by this service:

o The Common tab – Configure the common permission settings to assign permissions to specific groups and users. By default, the common groups are displayed. Click the edit ( ) button to edit the settings of a specific group or click the delete ( ) button to delete a specific group.

Create Group – Click Create Group to create a new group and add it into the common permission settings. In the Add a Group window, configure the following settings:

a. Custom Group Name – Enter a name for the group and enter an optional description for future reference. Enter $SiteName to

97


automatically add the site title as the group name prefix in Create Site service request.


c. Select Users – Select your desired users to add into the group. Click Add a User and enter the usernames in the pop-up window. You can also enter $ to select the following roles: $Requester, $ManagerOfRequester, $PrimarySiteCollectionContact, $SecondarySiteCollectionContact, $PrimarySiteContact, and $SecondarySiteContact. Then, click OK to save your configurations.





Grant Permissions – Click Grant Permissions to grant permissions to specific users. In the Grant User Permissions window, configure the following settings:





o The specific template tab – The template tab depends on the selected site collection template. The default groups of the site collection template are displayed. Click the edit ( ) button to edit the settings of a specific group or click the delete ( ) button to delete a specific group.

Use common permission settings – Select the checkbox to apply the permission settings in the Common tab. If there are group names that

98


already exist in the Common tab, the group settings will be replaced by those of the Common tab.

Create Group – Click Create Group to create a new group and add it into the common permission settings. In the Add a Group window, configure the following settings:

a. Custom Group Name – Enter a name for the group and enter an optional description for future reference.







Grant Permissions – Click Grant Permissions to grant permissions to specific users. In the Grant User Permissions window, configure the following settings:





o Business User action control – choose how to control the business user actions on the security group.

99


Allow Business User to grant user permissions directly – Select this checkbox to allow business users to directly grant permissions to specific users in the request.

Prevent Business User from requesting to grant permissions with the following permission levels – Select this checkbox and select your desired permission levels. The selected permission levels will not be displayed in the request.

14. Navigation – Configure navigation options for sites created using this service:

• Choose whether or not to Display this site on the Quick Launch of the parent site.

• Choose whether or not to Display this site on the ribbon link bar of the parent site.

Choose to apply this option to sites created by this service or allow the business user to choose the option when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The navigation options configured here will be associated with all site created by this service. Select Show as Read-Only to Business User to allow the business users to see the navigation options in the service request or Hide from Business User to not display the navigation options in this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the navigation options.

15. Navigation Inheritance – Choose whether or not to have sites created by this service Use the top link bar from the parent site by choosing the corresponding radio button.

Choose to apply the option to sites created by this service or allow the business user to choose the option when submitting a service request for this service. Choose from the following:

• Assign by Business User – Allows business user to choose the option when submitting a service request for this service.

• Assign by IT Admin – The selected option will be applied for this service. Select Show as Read-Only to Business User to allow the business users to see the default option in the service request or Hide from Business User to not display the option associated with this service to the business users requesting this service.


17. Primary Site Contact – The Primary Site Contact will be the user designated for managing the site created by this service. Assign a user to be the Primary Site Contact by entering the username into the text box. Press Enter to check that the name is valid.

Choose to assign the Primary Site Contact to sites created by this service or allow the business user to designate one when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Primary Site Contact configured here will be associated with all site created by this service. Select Show as Read-Only to Business User to allow the business users to see the Primary Site Collection Contact in the service request or Hide from Business User.

100


• Assign by Business User – Allows the business user to configure the Primary Site Contact.

You can send an e-mail to notify the Primary Site Contact when the site is created successfully. Select the Notify the contact upon site creation checkbox and select an e-mail template from the drop-down list. By default, Built-in New Object Notification E-mail Template is selected.

18. Secondary Site Contact – The Secondary Site Contact will be the user designated for managing sites created by this service in case the Primary Site Contact is unable to respond to a notification. Assign a user to be the Secondary Site Contact by entering the username into the text box. Press Enter to check that the name is valid.

Choose to assign the Secondary Site Contact to sites created by this service or allow the business user to designate one when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Secondary Site Contact configured here will be associated with all sites created by this service. Select Show as Read-Only to Business User to allow the business users to see the Secondary Site Contact in the service request or Hide from Business User to not display the Secondary Site Contact associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Secondary Site Contact.

You can send an e-mail to notify the Secondary Site Contact when the site is created successfully. Select the Notify the contact upon site creation checkbox and select an e-mail template from the drop-down list. By default, Built-in New Object Notification E-mail Template is selected.

19. Governance Automation App and App Parts – Choose to automatically enable Governance Automation App during site creation. If enabling this feature, first make sure that the Governance Automation App has been properly deployed to your farm. For more information about the environment configuration and deployment, refer to Installing the Governance Automation App. If you choose Automatically enable Governance Automation App, you can also choose to automatically add Governance Automation app part Site Information Card into the homepage of the site that will be created by this service. Select the Automatically add Governance Automation app parts into the homepage checkbox and then select the Site Information Card checkbox.

20. Metadata – Select the metadata to be made available to users when submitting a request for this service. Click the Add Metadata hyperlink to display the Add Custom Metadata window. In the Add Metadata popup window:

• Select the desired metadata by selecting the corresponding checkboxes. The metadata displayed here is configured in the Metadata interface. You can also click Create on the ribbon to go to the Create Metadata interface. For information on configuring Metadata, see Creating or Editing Metadata.


101



Optionally, you can select the Inherit parent site metadata value checkbox. With this option selected, the newly created site, which is based on this service, will inherit its parent site’s metadata value.










24. Execution Schedule – Select Enable service request execution schedule to define when Governance Automation executes the service request. Then choose a previously configured execution schedule from the drop-down menu or click Create New to create a new one.

102



• Allow business users to override IT Admin’s execution schedule (This section only appears when Enable service request execution schedule is selected) – If Enable service request execution schedule is selected in the Execution Schedule section, you can choose to allow business users to override the execution schedule selected by IT Admin and define their own scheduled request execution time.





• Click Save and Activate to save all of the configurations and activate this service which allows users to submit requests for this service.


Create My Site Service Configure Create My Site services to define the Create My Site service request template for business users. You can customize the settings for My Sites created by this service as well as configure available options for business users to choose from when requesting this service. My Sites created by Governance Automation inherit data protection and content retention policies from the site collection they live in. My Sites created by Governance Automation use the same DocAve Granular Backup and Recovery, DocAve Connector, DocAve Archiver and lifecycle management settings as the site collections they are created in.

In the Create My Site Service interface or Edit Create My Site Service interface, configure the following settings:




103




• Assign by IT Admin – The department selected in the preceding drop-down menu will be associated with all My Sites created by this service. Select Show as Read-Only to Business User to allow the business users to see the default department in the service request or Hide from Business User to not display the department associated with this service to the business users requesting this service.


5. Service Permissions – Choose Allow all users to use this service to allow this service be requested by any user, or specify the users or groups that have permissions to access this service by choosing Select users/groups to use this service and enter the names of the users/groups in the text box. Press Enter to check that the names are valid.


• Select Allow all users to access this service through a questionnaire even if the users are not listed above to allow users with the permission to the questionnaire to access this service via a questionnaire even if the users are not listed in the permission above.


7. Administrator Contact – Specify a user to be the Administrator Contact. This user should be an administrator of Governance Automation and is responsible for service management. Governance Automation will assign a task to the Administrator Contact when an error occurs after the approval process starts. Enter a username in the Administrator Contact text box. Press Enter to check that the name is valid. To also have an e-mail notification be sent to the Administrator Contact when this service encounters an error, configure the Administrator Notification section of Settings. For more information on how to configure the Administrator Notification, see Configuring Administrator Notifications.


9. Farm – Select the farm in which you allow business users to create My Site.

10. User Profile – Select your desired user profile that will be used for My Sites.

104


11. Bulk Mode – Choose to enable bulk mode. Select the Enable bulk creation of My Sites to allow creating multiple My Sites for different users in one service request.

12. Policy – Select the site collection policies that you wish to apply to My Site by selecting the corresponding checkboxes or click Create New to be brought to the Site Collection Policy interface to create a new policy. Configure this section as follows:

• Select the policies to be made available for business users to choose from by selecting the corresponding checkbox of each policy in the Select Policies configuration area. All policies selected here will be made available to business users if you select Assign by Business User in the Assign by drop-down menu.

• Select a default policy in the Default Selection drop-down menu. If Assign by Business User is selected in the service request, but the business user will be able to select another policy out of the policies you have selected in the Select Policies configuration area. If Assign by IT Admin is selected in the Assign by drop-down menu, this will be the only available policy in the service request and the business user will not be able to choose another policy

Choose to assign a policy to My Sites created by this service or allow business user to choose the policy when submitting a service request for this service from the policies selected in the Select Policies configuration area. Choose from following:

• Assign by IT Admin – The policy selected in the Default Selection drop-down menu will be associated with all My Sites created by this service. Select Show as Read-Only to Business Users to allow the business user to see the default policy in the service request or Hide from Business User to not display the policy associated with this service to the business users requesting this service.

• Assign by Business User – Allows business user to choose from the policies you have selected in the Select Policies configuration area.

13. Language (This option is only available if you have language packs installed on the Web server) - Specify the language for the My Site. If more than one language is selected, choose a default language from the Default Selection drop-down menu.

• Choose to assign a language to My Sites created by this service or allow the business user to choose the language when submitting a service request for this service from the languages selected in the Language configuration area. Choose from the following:

o Assign by IT Admin – The language selected in the Default Selection drop-down menu will be associated with all My Sites created by this service. Select Show as Read-Only to Business User to allow the business users to see the default language in the service request or Hide from Business User to not display the language to the business users requesting this service.

o Assign by Business User – Allows business user to choose from the languages you have selected in the Language configuration area.

*Note: If Always use regional settings defined by site administrators is selected in the User Profile in SharePoint 2013, the language selected in Governance Automation will not take effect. The My Site language depends on the locale selected in regional settings.

105


14. Secondary My Site Administrator – Assign a user to be the Secondary My Site Administrator by entering the username into the text box. Press Enter to check that the name is valid.

Choose to assign the Secondary My Site Administrator to My Sites created by this service or allow the business user to choose the Secondary My Site Administrator when submitting a service request for this service. By default, it is Assign by IT Admin and Hide from Business User. Choose from the following:

• Assign by IT Admin – The Secondary My Site Administrator configured here will be associated with all My Sites created by this service. Select Show as Read-Only to Business User to allow the business users to see the Secondary My Site Administrator in the service request or Hide from Business User to not display the Secondary My Site Administrator associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Secondary My Site Administrator.

15. Secondary My Site Contact – The Secondary My Site Contact will be the user designated for managing the My Sites created by this service if the Primary My Site Contact is unable to respond to a notification. Assign a user to be the Secondary My Site Contact by entering the username into the text box. Press Enter to check that the name is valid.

Choose to assign the Secondary My Site Contact to site collections created by this service or allow the business user to choose the Secondary My Site Contact when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Secondary My Site Contact configured here will be associated with all My Sites created by this service. Select Show as Read-Only to Business User to allow the business users to see the Secondary My Site Contact in the service request or Hide from Business User to not display the Secondary My Site Contact associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Secondary My Site Contact.

You can send an e-mail to notify the Secondary My Site Contact when the My Site is created successfully. Select the Notify the contact upon My Site creation checkbox and select an e-mail template from the drop-down list. By default, Built-in New Object Notification E-mail Template is selected.

16. Governance Automation App and App Parts – Choose to automatically enable Governance Automation App during My Site creation. If enabling this feature, first make sure that the Governance Automation App has been properly deployed to your farm. For more information about the environment configuration and deployment, refer to Installing the Governance Automation App. If you choose Automatically enable Governance Automation App, you can also choose to automatically add Governance Automation app parts into the homepage of the My Site that will be created by this service. Select the Automatically add Governance Automation app parts into the homepage checkbox and then select your desired app parts by selecting the corresponding checkboxes.


106


18. Metadata – Select the metadata to be made available to users when submitting a request for this service. Click the Add Metadata hyperlink to display the Add Metadata window. In the Add Metadata popup window:

• Select the desired metadata by clicking before a metadata name. The metadata displayed here is configured in the Metadata interface. You can also click Create on the ribbon to go to the Create Metadata interface. For information on configuring Metadata, see Creating or Editing Metadata.










*Note: If the selected scope is in a SharePoint on-premises farm, make sure that the executable file and PowerShell script file exist in the DocAve Agent Directory …\Agent\bin\GovernanceAutomation and the assembly file exists in the Governance Automation Directory …\AvePoint\GovernanceAutomation\bin. If the selected scope is in SharePoint Online standard instance or SharePoint Online dedicated instance, make sure

107


that the executable file, the PowerShell script file, and the assembly file exist in the Governance Automation Directory …\AvePoint\GovernanceAutomation\bin.










Create Library/List Service Configure Create Library/List services to define the Create Library/List service request templates for business users. You can predefine the settings for libraries or lists created by this service as well as configure available options for business users to choose from when requesting this service. Libraries or lists created by Governance Automation are included in the data protection plan and content retention rules of the site collection they live in.

In the Create Library/List Service interface or Edit Create Library/List Service interface, configure the following settings:



108


3. Service Category – Categories are used to organize your Governance Automation services. Select an existing category from the drop-down menu or create a new category for this service by clicking Create New then configuring new category in the Create Category interface.



• Assign by IT Admin – The department selected in the preceding drop-down menu will be associated with all sites created by this service. Select Show as Read-Only to Business User to allow the business users to see the default department in the service request or Hide from Business User to not display the department associated with this service to the business users requesting this service.


5. Service Permissions – Choose Allow all users to use this service to allow this service be requested by any user, or specify the users or groups that have permissions to access this service by choosing Select users/groups to use this service and enter the username of the users/groups in the text box. Press Enter to check that the names are valid.






109


9. Bulk Mode – Choose to enable bulk mode. Select the Enable bulk creation of libraries/lists to allow users to request the creation of multiple libraries and lists in one service request.

10. Scope – Choose the site you wish to be made available in this service. Business users will be able to choose which site to create the new library or list under.

a. Select a farm or My Registered Sites from the drop-down menu.

b. Choose one of the following methods to configure the scope:

• Manually input URL – Select this radio button and click the Add Your Own URL link to enter the URL of the site in the URL text box. To add more sites click Add Your Own URL after entering a URL.

• Select scope from tree – Select this radio button and then expand the tree to select the sites.



c. Library/List URL – Choose to use library/list name in URL or use SharePoint context in service request scope.

• Use library/list name in URL – Select this checkbox to have the library/list URL be filled automatically after entering the library/list name in the service request.

• Use SharePoint context to automatically populate the service request scope – Select this checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format: https://servername:port/Request/NewListCreationRequest?serviceId={serviceID}&parent={parentsiteURL}.

11. Navigation – Choose to display this library or list in the Quick Launch of its parent site.

Choose to assign the navigation option to the library or list created by this service or allow the business user to choose this option when submitting a service request for this service in the Navigation configuration area. Choose from the following:

• Assign by IT Admin – The option selected here will be associated with all libraries or lists created by this service. Select Show as Read-Only to Business User to allow the business user to see the selected option in the service request or Hide from Business User to not display the selected option to the business users requesting this service.

110


• Assign by Business User – Allows business user to choose the option in the Navigation configuration area.

12. Type – Select the type of the object that you allow to be create, Library or List.

Choose to assign the type to the library or list created by this service or allow the business user to choose the type when submitting a service request for this service in the Type configuration area. Choose from the following:

• Assign by IT Admin – The type selected here will be associated with all service requests created by this service. Select Show as Read-Only to Business User to allow the business user to see the selected type in the service request or Hide from Business User to not display the selected type to the business users requesting this service.

• Assign by Business User – Allows business user to choose the type in the Type configuration area.


14. Library/List Template – Enter the site collection URL in which all of the library or list templates are centrally stored in the Template store text box, then and click Retrieve to retrieve the templates. Select the available templates that your business users may use to create a new library or list. You can select multiple templates. Use the Default template drop-down list to designate the default template for the new library or list created by this service.

Choose to assign the template to the library or list created by this service or allow the business user to choose the template when submitting a service request for this service in the Library/List Template configuration area. Choose from the following:

• Assign by IT Admin – The template selected here will be associated with all service requests created by this service. Select Show as Read-Only to Business User to allow the business user to see the selected template in the service request or Hide from Business User to not display the selected template to the business users requesting this service.

• Assign by Business User – Allows business user to choose the template in the Library/List Template configuration area.

15. Document Version History (This section appears when you select Library as the Type.)– Specify whether a version is created each time you edit a file in this library.

• Require content approval for submitted files? – Specify whether new files or changes to existing files should remain in a draft state until they have been approved.

• Create a version each time you edit a file in this library?

o No versioning – Do not create a version when a file in this library is edited.

o Create major versions – Create a major version each time a file in this library is edited.

o Create major and minor (draft) versions – Create major and minor versions each time a file in this library is edited.

111


• Optionally limit the number of versions to retain – Allows you to limit the number of versions that you wish to retain. To limit the number of major versions, select the checkbox before Keep the following number of major versions and enter a positive integer in the provided text box. You can also keep drafts for major versions by selecting the checkbox before Keep drafts for the following number of major versions and enter a positive integer in the provided text box.

Choose to assign the configured settings to the library created by this service or allow the business user to configure these settings when submitting a service request for this service in the Document Version History configuration area. Choose from the following:

• Assign by IT Admin – The settings configured here will be associated with all libraries created by this service. Select Show as Read-Only to Business User to allow the business user to see the configured settings in the service request or Hide from Business User to not display the configured settings to the business user requesting this service.

• Assign by Business User – Allows business user to configure the settings in the Document Version History configuration area.

16. Item Version History (This section appears when you select List as the Type.) – Specify whether a version is created each time you edit an item in this list.

• Require content approval for submitted items? – Specify whether new items or changes to existing items should remain in a draft state until they have been approved.

• Create a version each time you edit an item in this list?

o No versioning – Do not create a version when an item in this list is edited.

o Create major versions – Create a major version each time an item in this list is edited.

o Create major and minor (draft) versions – Create major and minor versions each time an item in this list is edited.

• Optionally limit the number of versions to retain – Allows you to limit the number of versions that you wish to retain. To limit the number of major versions, select the checkbox before Keep the following number of major versions and enter a positive integer in the provided text box. You can also keep drafts for major versions by selecting the checkbox before Keep drafts for the following number of major versions and enter a positive integer in the provided text box.

Choose to assign the configured settings to the list created by this service or allow the business user to configure these settings when submitting a service request for this service in the Item Version History configuration area. Choose from the following:

• Assign by IT Admin – The settings configured here will be associated with all lists created by this service. Select Show as Read-Only to Business User to allow the business user to see the configured settings in the service request or Hide from Business User to not display the configured settings to the business user requesting this service.

112


• Assign by Business User – Allows business user to configure the settings in the Item Version History configuration area.


18. Metadata – Select the metadata to be made available to users when submitting a request for this service. Click the Add Metadata hyperlink to display the Add Metadata window. In the Add Metadata window:




19. Approval Process – Select an approval process from the drop-down menu or click Create New to create a new approval process. This will bring you to the Approval Process Settings interface without saving any of the configurations you have made for this service. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.






*Note: If the selected scope is in a SharePoint on-premises farm, make sure that the executable file and PowerShell script file exist in the DocAve Agent Directory …\Agent\bin\GovernanceAutomation and the assembly file exists in the Governance Automation Directory …\AvePoint\GovernanceAutomation\bin. If the selected scope is in SharePoint Online standard instance or SharePoint Online dedicated instance, make sure

113


that the executable file, the PowerShell script file, and the assembly file exist in the Governance Automation Directory …\AvePoint\GovernanceAutomation\bin.










Site Collection Lifecycle Management Service Site Collection Lifecycle Management services provide business users with control over the lifecycle of their site collections created/managed by Governance Automation. You can configure the settings to notify site collection owners of lease expiration and lack of use of their site collections.

In the Create Site Collection Lifecycle Management interface or Edit Site Collection Lifecycle Management interface, configure the following settings:

1. Service Name and Description– Enter a Name for the service and an optional Description for future reference.



114


4. Department – Departments help organize services as well as provide essential Governance Automation reporting information for sorting and understanding your organization’s SharePoint usage. Select a department you wish this service to belong to from the drop-down menu or click Add New to create a new one.


• Assign by IT Admin – The users in the Department selected in the preceding drop-down menu will be the intended requesters of this service. Select Show as Read-Only to Business User to allow the business users to see the default department in the service request or Hide from Business User to not display the department associated with this service to the business users requesting this service.


5. Service Permissions – Choose Allow all users to use this service to allow this service be requested by any user, or specify the users or groups that have permissions to access this service by choosing Select users/groups to use this service. Then enter a username of the users/groups in the text box. Press Enter to check that the names are valid.



• Select Only allow site collection contact/administrator or site contact to submit requests for this service to only allow the site collection contact, site collection administrator, or site contact to submit requests for this service.


7. Administrator Contact –Specify a user to be the Administrator Contact. This user should be an administrator of Governance Automation and is responsible for service management. Governance Automation will assign a task to the Administrator Contact when an error occurs after the approval process starts. Enter a username in the Administrator Contact text box. Press Enter to check that the name is valid. To also have an e-mail notification be sent to the Administrator Contact when this service encounters an error, configure the Administrator Notification section of Settings. For more information on how to configure the Administrator Notification, see Configuring Administrator Notifications.


115


9. Scope – Select the desired Web applications. Select a farm or My Registered Sites from the drop-down menu and expand the tree. Select the desired Web applications by selecting the corresponding checkboxes.

Optionally, configure the following options:

• Enable security trimming in the tree of the request for this service – Select this checkbox to only allow requesters to view the node that they have permissions to access in the scope tree.


• Use SharePoint context to automatically populate the service request scope – Select this checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format: https://servername:port/Request/NewSCLifecycle?serviceId={serviceID}&parent={parentsiteURL}.

10. Lifecycle Management Actions – Select the type of lifecycle management service to create:

• Extend Site Collection – Allows business users to request an extension to the lease of their site collection. Note that an extension to a site collection’s lease will grant the site collection the amount of time indicated in the lease from the day the request is approved and is not in addition to the remaining time of the previous lease.

• Delete Site Collection – Allows business users to request their site collection be deleted.

• Archive Site Collection – Allows business users to request their site collection to be extracted from SharePoint and stored in more economical storage devices.

• Change Site Collection Policy - Allows business users to request a different Governance Automation policy be associated with the site collection they own, or request that a different Governance Automation policy associated with a My Site by specifying the My Site owner.

• Unlock Site Collection – Allows business users to request to unlock a locked site collection.

• Change Site Collection Quota – Allows business users to request a change of the quota template or quota size of site collections.

*Note: Lifecycle management services are available to the users indicated in their service Permissions configuration, however, service request for any of these lifecycle management actions can only be submitted by each site collection’s owner.


116





12. Approval Process – Select Allow all approvers to edit this service request to allow all of the approvers to edit the service request for this service when viewing the service request. You can Notify the requester when the service request is edited by selecting the checkbox and then selecting an E-mail template.










117






• Click Save and Activate to save all of the configurations and activate this service allowing users to submit service requests for this service.


Site Lifecycle Management Service Site Lifecycle Management services provide business users with control over the lifecycle of their sites created/managed by Governance Automation.

In the Create Site Lifecycle Management interface or Edit Site Lifecycle Management interface, configure the following settings:





Choose to assign a department to this service or allow the business user to choose the Department when submitting a service request for this service. Choose from the following:



118


5. Service Permissions – Choose Allow all users to use this service to allow this service be requested by any user, or specify the users or groups that have permissions to access this service by choosing Select users/groups to use this service. Then enter the names of the users/groups in the text box. Press Enter to check that the names are valid.



• Select Only allow site collection contact/administrator or site contact to submit requests for this service to only allow the site collection contact, site collection administrator, or site contact, to submit requests for this service.




9. Scope – Configure the scope for this service. Select a farm or My Registered Sites from the drop-down menu first, then you can choose to input URLs manually or select the scope from the tree.

• Manually input URL – Click Add Your Own URL to add the URL, then enter the URL in the text box. Repeat the step to add multiple URLs.

• Select scope from tree – Click the farm or My Registered Sites to expand the tree and select your desired nodes by selecting the corresponding checkboxes.




119


• Use SharePoint context to automatically populate the service request scope – Select this checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format: https://servername:port/SSLMRequest/New?serviceId={serviceID}&parent={parentsiteURL}.

10. Lifecycle Management Actions – Choose the type of lifecycle management service to create:

• Delete Site – Allows business users to request to delete their sites.

• Archive Site – Allows business users to request for their sites to be extracted from SharePoint and stored in more economical storage devices.

*Note: If you choose Archive Site, you must select an Archiver profile from the drop-down menu. Archiver profiles are configured in DocAve.





12. Approval Process – Select an approval process from the drop-down menu or create a new one by clicking the Create New link to redirect to the Approval Process Settings interface without saving any changes on the current page. This approval process will be triggered when a service request to manage site lifecycle is submitted. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.


120
















121


Clone or Transfer User Permission Service Configure Clone or Transfer User Permission services to request having one person’s permissions be the same as another user. Role changes happen frequently in most organizations. This puts permission control in the hands of business users based on predefined settings set by IT administrators.

In the Clone User Permissions Service interface or Edit Clone User Permission Service interface, configure the following settings:






• Assign by IT Admin – The Department selected in the preceding drop-down menu will be associated with this service. Select Show as Read-Only to Business User to allow the business users to see the default department in the service request or Hide from Business User to not display the department associated with this service to the business users requesting this service.


5. Service Permissions – Choose Allow all users to use this service to allow this service be requested by any user, or specify the users or groups that have permissions to access this service by choosing Select users/groups to use this service. Then enter a username of the users/groups in the text box. Press Enter to check that the names are valid.



122



7. Administrator Contact – Specify a user to be the Administrator Contact. This user should be an administrator of Governance Automation and is responsible for service management. Governance Automation will assign a task to the Administrator Contact when an error occurs after the approval process starts. Enter a username in the Administrator Contact text box. Press Enter to check that the name is valid. To also have an e-mail notification be sent to the Administrator Contact when this service encounters an error, configure the Administrator Notification in Settings. For more information on how to configure the Administrator Notification, see Configuring Administrator Notifications.


9. Scope – Select the nodes from which the requester can request for cloning or transferring user permissions. Select a farm or My Registered Sites and expand the tree to select the desired nodes by selecting the corresponding checkboxes.

Optionally, select the Use SharePoint context to automatically populate the service request scope checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format: https://servername:port/Request/NewCloneUserPermRequest?serviceId={serviceID}&parent={parentsiteURL}.

10. Restrict Source User Selection – Specify the users which can be selected as the source user to clone permissions from. Choose from the following:

• Allow any user – Check this option to allow the business user to select any user of the selected scope as the source user.

• Allow peers and direct or indirect reports – Check this option to allow the business user to select the users managed by the requester and the users of the same title as the requester to be the source user.

• Allow direct or indirect reports – Check this option to allow the business user to select the users managed by the requester to be the source user.

*Note: A User Profile Service must be configured in Governance Automation, or an External Role Source Service must be configured by users. Otherwise this setting will not take effect.

11. Restrict Target User Selection – Specify the users which can be selected as the target user to clone permissions to. Choose from the following:

• Allow any user – Check this option to allow the business user to select any user of the selected scope as the source user.

123




*Note: A User Profile Service must be configured in Governance Automation, or an External Role Source Service must be configured by users. Otherwise this setting will not take effect.


13. Permission Option – Select a method from the drop-down menu to determine how you will assign the source user’s/group’s permission to the target user/group.

• Append – Add the permission of the source user/group to the destination user/group.

• Replace – Replace the permission of the target user with the source user’s permission.

Choose to assign the Permission Option by this service or allow the business user to choose the Permission Option when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Permission Option configured here will be applied on the Clone User Permission service request. Select Show as Read-Only to Business User to allow the business users to see the Permission Option in the service request or Hide from Business User to not display the Permission Option associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Permission Option.

14. User Alert Option – Choose to send the user alerts settings set by the source user to the target users.

Select the Send source user alerts to target user checkbox for selecting this feature by default when submitting a service request.

Choose to assign the User Alert Option directly by this service or allow the business user to choose the User Alert Option when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The User Alert Option configured here will be associated with all of the site collections selected in the scope of the Clone User Permission service request. Select Show as Read-Only to Business User to allow the business users to see the User Alert Option in the service request or Hide from Business User to not display the User Alert Option associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the User Alert Option.

15. Change Metadata – Choose to change the source user metadata to the target user. If you select this option, then click Add Source User Metadata to add the source user metadata you want to change. Enter the metadata you want to allow to be changed for this service.

124


Choose to assign the Change Metadata option directly by this service or allow the business user to configure it when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Change Metadata configured here will be associated with all of the site collections selected in the scope of the Clone User Permission service request. Select Show as Read-Only to Business User to allow the business users to see the Change Metadata option in the service request or Hide from Business User to not display the Change Metadata option associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the option.

16. Additional Option – Choose how to deal with the permissions of the source user that resides in a SharePoint group. Choose from the following:

• Add target user to the same group in destination – Add the target user into the SharePoint group where the source user resides.

• Clone source user’s permission to the target user directly – Copy the permissions of the group where the source user resides to the target user.

Choose to assign the Additional Option directly by this service or allow the business user to choose the Additional Option when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Additional Option configured here will be associated with all of the site collections selected in the scope of the Clone User Permission service request. Select Show as Read-Only to Business User to allow the business users to see the Additional Option in the service request or Hide from Business User to not display the Additional Option associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Additional Option.

17. Options for Transfer – Specify the options to manage the source user/group when transferring permissions. The selected options will be the default selections when submitting a service request. Choose from the following:

• Remove source user’s explicit permission – Remove the source user’s or group’s permission after cloning the permission successfully.

• Remove source user from SharePoint groups – Delete the source user from SharePoint Groups that he resides after cloning the permission successfully.

• Delete source user from site collection – Delete the source user or group from the site collection after cloning the permission successfully.

Choose to assign the Options for Transfer directly by this service or allow the business user to choose the Options for Transfer when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Options for Transfer configured here will be associated with all of the site collections selected in the scope of the Clone User Permission service request. Select Show as Read-Only to Business User to allow the business users to see

125


the Options for Transfer in the service request or Hide from Business User to not display the Options for Transfer associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Options for Transfer.






20. Approval Process – Select an approval process from the drop-down menu, or create a new one by clicking the Create New link to redirect to the Approval Process Settings interface without saving any configurations on the current page. This approval process will be triggered when a service request to clone user permissions is submitted. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.






*Note: If the selected scope is in a SharePoint on-premises farm, make sure that the executable file and PowerShell script file exist in the DocAve Agent Directory

126


…\Agent\bin\GovernanceAutomation and the assembly file exists in the Governance Automation Directory …\AvePoint\GovernanceAutomation\bin. If the selected scope is in SharePoint Online standard instance or SharePoint Online dedicated instance, make sure that the executable file, the PowerShell script file, and the assembly file exist in the Governance Automation Directory …\AvePoint\GovernanceAutomation\bin.










Change Site Collection Contact or Administrator Service Configure Change Site Collection Contact or Administrator services to define the Change Site Collection Contact or Administrator service request for business users. You can change the Site Collection Contact or Administrator when the site collection expires to transfer the responsibilities to another user.

In the Create Change Site Collection Contact or Administrator Service interface or Edit Change Site Collection Contact or Administrator Service interface, configure the following settings:


2. Language – Choose the language for this service. When starting a request, you can filter the services according to their language.

127













9. Scope – Select the nodes where the requester can request for changing the site collection contact or administrator.

128


• For SharePoint on-premises, select a Farm and expand the farm tree to select the desired Web applications by selecting the corresponding checkboxes.

• For SharePoint Online, click My Registered Sites to expand it and select your desired SharePoint Sites groups by selecting the corresponding checkboxes.




• Use SharePoint context to automatically populate the service request scope – Select this checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format: https://servername:port/ChangeSCContactRequest/New?serviceId={serviceID}&parent={parentsiteURL}.

10. Change Contact/Administrator Settings – Choose to allow business users to change primary and secondary site collection contact, or primary and secondary site collection administrator. Optionally, you can define whether to allow business users to change primary My Site contact and primary My Site administrator.

*Note: For SharePoint Online standard instance site collection and SharePoint Online dedicated instance site collection, only the primary site collection administrator can be changed. The secondary site collection administrator cannot be changed. If Primary and secondary site collection administrator is selected in the service, and a SharePoint Online standard instance site collection URL or SharePoint Online dedicated instance site collection URL is entered in the request page, only the Primary administrator text box is available in the request.



• Click View Details on the ribbon to see the detailed information of a selected metadata.


129


12. Approval Process – Select an approval process from the drop-down menu, or create a new one by clicking the Create New link to redirect to the Approval Process Settings interface without saving any configurations on the current page. This approval process will be triggered when a service request to change the site collection contact or administrator is submitted. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.







14. Execution Schedule – Select the Enable service request execution schedule checkbox to define when Governance Automation executes the service request. Then, choose a previously configured execution schedule from the drop-down menu or click Create New to create a new one.



• Notify the approvers about upcoming scheduled request in advance by – Choose to send an e-mail to notify the approvers in advance when it reaches a specified time. If

130


Notify the approvers about upcoming scheduled request in advance by is selected, enter a positive integer in the text box and select Day(s) or Week(s) from the drop-down list. Then, select an E-mail Template for the notification sent to the approvers.






Change Site Contact Service You can change the Site Contact when the corresponding site collection expires to transfer the responsibilities to another user.

In the Create Change Site Contact Service interface or Edit Change Site Contact Service interface, configure the following settings:








131








9. Scope – Define the scope by manually inputting URLs or selecting from the tree.

• Manually input URL – Click Add Your Own URL and then input the URL in the text box. Repeat to add more URLs.

• Select from tree – Expand the farm tree or My Registered Sites to select the desired nodes by selecting the corresponding checkboxes.




• Use SharePoint context to automatically populate the service request scope – Select this checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be

132


used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format: https://servername:port/ChangeSSContactRequest/New?serviceId={serviceID}&parent={parentsiteURL}.





11. Approval Process – Select an approval process from the drop-down menu, or create a new one by clicking the Create New link to redirect to the Approval Process Settings interface without saving any configurations on the current page. This approval process will be triggered when a service request to change site contact is submitted. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.






*Note: If the selected scope is in a SharePoint on-premises farm, make sure that the executable file and PowerShell script file exist in the DocAve Agent Directory …\Agent\bin\GovernanceAutomation and the assembly file exists in the Governance Automation Directory. If the selected scope is in SharePoint Online standard instance or

133


SharePoint Online dedicated instance, make sure that the executable file, the PowerShell script file, and the assembly file exist in the Governance Automation Directory.










Content Move Service Configure Content Move services to define the Content Move service request template for business users. You can configure the settings to copy or move SharePoint contents, so the content and topology of your SharePoint environment can be restructured easily and accurately.

In the Create Content Move interface or Edit Content Move interface, configure the following settings:




134






5. Service Permissions – Choose Allow all users to use this service to allow this service be requested by any user, or specify the users or groups that have permissions to access this service by choosing Select users/groups to use this service. Then enter the names of the users/groups in the text box. Press Enter to check that the names are valid.






9. Scope – Select the source scope and the destination scope and they can be identified as a source or destination in a Content Move request.

• For SharePoint on-premises, select a loaded farm and expand the farm tree. Then, select the desired Web applications by selecting the corresponding checkboxes.

135




• Enable security trimming in the tree of the request for this service – Select this checkbox only allow requesters to view the node that they have permissions to access in the scope tree.


• Use SharePoint context to automatically populate the service request scope – Select this checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format: https://servername:port/ContentManagerRequest/New?serviceId={serviceID}&parent={parentsiteURL}.

10. Method – Select Copy or Move for this service or allow the business user to decide when submitting the request:

• Assign by Business User – Allows business user to choose the method when submitting a service request for this service.

• Assign by IT Admin – The selected method will be applied for this service. Select Show as Read-Only to Business User to allow the business users to see the default method in the service request or Hide from Business User to not display the method associated with this service to the business users requesting this service.

If you select Move, you may also configure the following settings:

• Source Documents/Items Deleted Method – Select Manually to delete the source content yourself once the move job is complete in DocAve (select the move job in Job Monitor, then click Delete on the ribbon and select Delete Content from the drop-down list), or select Automatically to have DocAve delete the source content once the move job is complete.

Choose to assign the method to this service and site collections created by this service or allow the business user to choose the method when submitting a service request for this service. Choose from the following:

o Assign by Business User – Allows business user to choose the method when submitting a service request for this service.

o Assign by IT Admin – The selected method will be applied for this service. Select Show as Read-Only to Business User to allow the business users to see the default method in the service request or Hide from Business User to not display the method associated with this service to the business users requesting this service.

136


• Delete Checked Out Documents From Source – By default, No is selected. Select Yes if you want to have the checked out documents on the source node deleted when the source content is deleted.

Choose to assign this option to this service and site collections created by this service or allow the business user to choose the option when submitting a service request for this service. Choose from the following:

o Assign by Business User – Allows business user to choose the option when submitting a service request for this service.

o Assign by IT Admin – The selected option will be applied for this service. Select Show as Read-Only to Business User to allow the business users to see the default option in the service request or Hide from Business User to not display the option associated with this service to the business users requesting this service.

11. Action – Select Attach to transfer the source node as a child node underneath the destination node, or select Merge to add the content, securities, and configurations of the source node to the destination node.

Choose to assign the action to this service and site collections created by this service or allow the business user to choose the action when submitting a service request for this service. Choose from the following:

o Assign by Business User – Allows business user to choose the action when submitting a service request for this service.

o Assign by IT Admin – The selected action will be applied for this service. Select Show as Read-Only to Business User to allow the business users to see the default action in the service request or Hide from Business User to not display the action associated with this service to the business users requesting this service.


13. Filter Policy – Select a filter policy you previously created in DocAve from the drop-down menu. Filter policies allow you to select specific objects or data within each SharePoint level from the Web application down to the item level.

Choose to apply the option to this service and site collections created by this service or allow the business user to choose the option when submitting a service request for this service. Choose from the following:



14. Configuration – Choose whether to migrate configuration to the destination.

• Select Copy configuration to copy the properties, descriptions, titles, settings, and features from the source node to the destination node.

137


o If you want to keep the look and feel of the source site, including the quick launch, top link bar, tree view, site themes, and master page, select the Keep look and feel checkbox.

*Note: This function will only take effect if the source node is a site, the destination node is a top-level site or a site collection, and if you chose Merge as the action.

• Leave Copy configuration deselected if you don’t want to migrate configuration to the destination. Then, choose from the following options:

o Select Copy the item-dependent columns and content types to maintain item integrity. Then, select a conflict resolution method for these items’ columns and content types from the drop-down menu:

Do not copy/move the columns and content types, or the corresponding items – Ignore the conflicting columns, content types, and the corresponding items, and do nothing on the source and destination node.

Overwrite the columns and content types – Overwrite the destination columns and content types with the source node.

Append the columns and content types to destination – Keep the destination columns and content types when there is a conflict. In addition, copy the source columns and content types to the destination node with a numerical suffix added (for example, ColumnName_1, ColumnName_2, etc.).

o Select Do not copy the item-dependent columns or content types. Report the items if the corresponding column or content type is not found in destination. The corresponding items are not copied to the destination. The job report will show items if the corresponding column or content type is not found in the destination node.

*Note: If a source node is associated with a Managed Metadata column and there is no Managed Metadata column in the destination node, Governance Automation do not copy or move the source Managed Metadata column to the destination.




15. Security – Select the Copy security checkbox to copy the user and/or group permissions from the source node to the destination node, including SharePoint permission level and permission

138


inheritance of SharePoint objects. Select the Exclude user/group without permission checkbox to not copy users and/or groups that have no permissions to the destination.




16. Content – Select the Copy content checkbox to copy content from the source node to the destination node, including files and items. Select the Include list attachment checkbox to also copy attached content in lists from the source node to the destination node.




17. Workflow – Select the Include workflow definition checkbox to copy the definition of existing workflows for the selected content from the source node to the destination node, and/or select the Include workflow instance to copy the state, history and tasks of existing workflows for the selected content from the source node to the destination node.

If you select Include workflow instance, Include completed instances is mandatory and the source completed instances will be copied to the destination. You can also select the Include running instances checkbox to copy the source running instances to the destination.




139


18. Managed Metadata Service Setting – Select the Copy Managed Metadata Service checkbox to copy the related Managed Metadata Services from the source node to the destination node, and then select one of the following options:

• Term – Copy terms that are used in the source, their parent terms, the term sets where the used terms reside, and the names of the groups where the used terms reside to the destination.

• Term set – Copy the whole term sets where the used terms reside in the source (regardless of whether or not the terms in the term sets are used by the source node or not) to the destination.

• Managed Metadata Service – Copy the whole Managed Metadata Services that are related to the source node to the destination.

*Note: Copying the Managed Metadata Service will automatically activate the service in the destination, if the service in the destination is not already activated.

Choose to apply the option to this service or allow the business user to choose the option when submitting a service request for this service. Choose from the following:




20. Preserve the Null Column Values – Select Yes to preserve the null values of item columns even if the columns on the destination have default values configured, or select No to replace null values with default values in the destination node.




21. Data Compression – Select the Compression checkbox if you want to compress the data when it is copied. If you choose to compress the data, use the slider to select the compression rate. Fastest compression rate results in a larger data set. Best compression rate results in a smaller, better quality data set, but the compression takes more time to perform.


140




22. Data Encryption – Select the Encryption checkbox if you want to encrypt the data. Then select the default security profile or a security profile which is previously configured in DocAve from the drop-down menu to protect your backup data using the security keys generated by the specified encryption method.




23. Mappings – Select previously configured profiles for column mapping, content type mapping, user mapping, domain mapping, and language mapping. Mapping profiles are created in DocAve and are optional.

• Column mapping – Allows you to map source columns to destination columns. The destination column name will be replaced by the configured source column name, and you can add value mapping. According to column type, the source column and the destination column can be the same or different.

• Content type mapping – Allows you to map source content types to the specified content types in destination, or change the content type name to another one, according to the condition that you set up.

• User mapping – Allows you to replace an existing source node username with an existing destination node username or a default username in the destination, or add a place holder account to keep user metadata even if the user no longer exists.

• Domain mapping – Allows you to map a source domain to a destination domain. The destination domain name will be replaced by the configured source domain name, and the user in the source domain will be mapped to the destination user which has the same login name.

• Language mapping – Allows you to choose if you want to display destination node in a different language than source node after the plan has been executed.


141




24. Back Up Environment Before Running Plan – Allows you to keep a copy of the source or destination node before copying/moving content.

• Back up the source environment (for Move only) – Create a copy of the source node prior to performing the move.

• Back up the destination environment – Create a copy of the destination node prior to performing the copy (allows you to undo the copy).

*Note: If you choose Back up the source environment and/or Back up the destination environment, you must select a storage policy from the drop-down menu.

Choose to back up the source/destination environment to this service and site collections created by this service or allow the business user to choose the option when submitting a service request for this service. Choose from the following:

o Assign by Business User – Allows business user to choose the option when submitting a service request for this service.

o Assign by IT Admin – The selected option will be applied for this service. Select Show as Read-Only to Business User to allow the business users to see the default option in the service request or Hide from Business User to not display the option associated with this service to the business users requesting this service.

25. Conflict Resolution – If the item name in the source node is the same as that of an existing item in the destination node, a conflict occurs. This setting allows you to handle conflicts at both the container and content level. Container level conflict resolution contains Skip, Merge, and Replace. Skip will keep the destination container as is and you can choose to set content level conflict resolution by clicking the checkbox next to Check lower objects. Merge will add the source container to the destination, but you must set content level conflict resolution. Replace will substitute the container in the destination with the one in source and you cannot set content level conflict resolution. Content level conflict resolution includes Skip, Overwrite, Overwrite by Last Modified Time, and Append.




142







28. Approval Process – Select an approval process from the drop-down menu or create a new one by clicking the Create New link to redirect to the Approval Process Settings interface without saving any changes on the current page. This approval process will be triggered when a service request for content move is submitted. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.







*Note: If the selected scope is in a SharePoint on-premises farm, make sure that the executable file and PowerShell script file exist in the DocAve Agent Directory …\Agent\bin\GovernanceAutomation and the assembly file exists in the Governance

143


Automation Directory …\AvePoint\GovernanceAutomation\bin. If the selected scope is in SharePoint Online standard instance or SharePoint Online dedicated instance, make sure that the executable file, the PowerShell script file, and the assembly file exist in the Governance Automation Directory …\AvePoint\GovernanceAutomation\bin.










Change Site Collection Settings Service Configure Change Site Collection Settings services to define the Change Site Collection Settings service request template for business users. You can change the title, description, and metadata of site collections.

In the Change Site Collection Settings interface or Edit Change Site Collection Settings interface, configure the following settings:



144










• Select Only allow site collection contacts or site collection administrators to submit requests for this service to only allow the site collection contacts or site collection administrators to submit requests for this service.



145



9. Scope – Specify the Web applications where you wish to change the Site Collection Settings

• For SharePoint on-premises, click a farm to expand the farm tree. Then, select the desired Web applications by selecting the corresponding checkboxes.




10. Changed Site Collection Settings – Choose to allow business users to change the title, description, and metadata of site collections by selecting the corresponding checkboxes. If you select the Metadata checkbox, click Add Metadata to add metadata to the site collection that can be edited by business users in the pop-up window. Select the Enable adding or deleting metadata checkbox to allow business users to add or delete metadata when submitting request for this service.





12. Approval Process – Select an approval process from the drop-down menu, or create a new one by clicking the Create New link to redirect to the Approval Process Settings interface without saving any configurations on the current page. When business users submit a service request to change site collection settings, this approval process is triggered when a service request to change site collection settings is submitted. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.

Optionally, select the Allow all approvers to edit this service request checkbox to allow all of the approvers to edit the service request for this service when viewing the service request. You

146


can Notify the requester when the service request is edited by selecting the checkbox and then selecting an E-mail template.















147


Change Site Metadata Service Configure Change Site Metadata services to define the Change Site Metadata service request template for business users. You can change the site metadata when you want to update the site information.

In the Change Site Metadata interface or Edit Change Site Metadata interface, configure the following settings:








5. Service Permissions – Choose Allow all users to use this service to allow this service be requested by any user, or specify the users or groups that have permissions to access this service by choosing Select users/groups to use this service. Then enter the names of the users/groups in the text box. Press Enter to check that the names are valid. Separate multiple users with semicolons.



148


• Select Only allow site collection contact/administrator or site contact to submit requests for this service to only allow the site collection contact or site contact to submit requests for this service.




9. Scope – Specify the scope by manually inputting URLs or selecting from the tree.


• Select scope from tree – Select a farm or My Registered Sites from the drop-down menu and expand the tree to select the desired nodes by selecting the corresponding checkboxes.




11. Change Metadata – Click Add Metadata to add metadata to the site that can be edited by business users in the pop-up window. Select the Enable adding or deleting metadata checkbox to allow business users to add or delete metadata when submitting request for this service.





149


13. Approval Process – Select an approval process from the drop-down menu, or create a new one by clicking the Create New link to redirect to the Approval Process Settings interface without saving any configurations on the current page. This approval process will be triggered when a service request to change site metadata is submitted. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.










• Notify the approvers about upcoming scheduled request in advance by – Choose to send an e-mail to notify the approvers in advance when it reaches a specified time. If Notify the approvers about upcoming scheduled request in advance by is selected,

150


enter a positive integer in the text box and select Day(s) or Week(s) from the drop-down list. Then, select an E-mail Template for the notification sent to the approvers.






Change Library/List Settings Service Configure Change Library/List Settings services to define the Change Library/List Settings service request templates for business users. You can choose the library/list settings that are available for business users to choose from when requesting this service. Library/list settings include name, description, navigation, and versioning settings.

In the Change Library/List Settings Service interface or Edit Change Library/List Settings Service interface, configure the following settings:






• Assign by IT Admin – The Department selected in the preceding drop-down menu will be associated with this service. Select Show as Read-Only to Business User to allow the business users to see the default department in the service request or Hide from Business User to not display the department associated with this service to the business users requesting this service.


151


5. Service Permissions – Choose Allow all users to use this service to allow this service be requested by any user, or specify the users or groups that have permissions to access this service by choosing Select users/groups to use this service and enter the names of the users/groups in the text box. Press Enter to check that the names are valid. Separate multiple users with semicolons.






9. Scope – Specify the scope by manually inputting URLs or selecting from the tree.


• Select scope from tree – Select a farm or My Registered Sites from the drop-down menu and then expand the tree to select the desired nodes by selecting the corresponding checkboxes.



10. Change Library/List Settings – Select the library/list settings that you allow business users to change by selecting the corresponding checkboxes, including Name, Description, Navigation, and Versioning settings.


152














153









Grant Permissions Service Configure Grant Permissions services to define the Grant Permissions service request template for the business users. You can specify users in a specific site or a library who you wish to grant permissions to.

In the Grant Permissions Service interface or Edit Grant Permissions Service interface, configure the following settings:



3. Service Category – Categories are used to organize your Governance Automation services. Select an existing category from the drop-down menu or create a new category for this service by clicking Create New then configuring a new category in the Create Category interface.

4. Department – Departments help organize services as well as provide essential Governance Automation reporting information for sorting and understanding your organization’s SharePoint usage. Select a department you wish this service to belong to from the drop-down menu or click Create New to create a new one.


• Assign by IT Admin – The users in the Department selected in the preceding drop-down menu will be the intended requesters of this service. Select Show as Read-Only to

154


Business User to allow the business users to see the default department in the service request or Hide from Business User to not display the department associated with this service to the business users requesting this service.


5. Service Permissions – Choose Allow all users to use this service to allow this service be requested by any user, or specify the users or groups to have permission to submit requests for this service by choosing Select users/groups to use this service. Then enter the names of the users/groups in the text box. Press Enter to check that the names are valid.






9. Scope – Select the Web applications you wish to enable.

• For SharePoint on-premises Web applications, select a farm and expand the farm tree. Then, select the desired Web applications by selecting the corresponding checkboxes.


Optionally, select the Use SharePoint context to automatically populate the service request scope checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format:

155


https://servername:port/GRPermRequest/New?serviceId={serviceID}&parent={parentsiteURL}.

10. Select Users – Select the users to which you want to grant permissions. Choose from the following:

• Allow domain group permissions assignment only – Check this option to only allow the business user to select the domain group as the source.

• Allow permissions assignment to user/group – Check this option to allow the business user to select the users or groups as the source.

o Allow any user/group – Select this option to allow the business user to select any user of the selected scope as the source user.

o Allow peers and direct or indirect reports – Select this option to allow the business user to select the users managed by the requester and the users of the same title as the requester to be the source user.

o Allow direct or indirect reports – Select this option to allow the business user to select the users managed by the requester to be the source user.

o Set requester as the default user – Select this to add the requester as the default user when starting a Grant Permissions request.

11. Permission Duration – Choose the permission duration for the selected users/groups.

• Permanent permissions – The permissions will be granted to the selected users/groups permanently.

• Temporary permissions – The permissions will be granted to the selected users/groups temporarily.

Choose to assign the Permission Duration option to this service or allow the business user to choose the Permission Duration option when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Permission Duration option configured here will be applied on the Grant Permission service request.

• Assign by Business User – Allows the business user to configure the Permission Duration option.

If Temporary permissions is selected, you can further configure the Temporary permissions settings:

• Specify the default duration – Enter a positive integer in the text box and select Day(s), Month(s), or Year(s) from the drop-down list.

• If Temporary permissions is assigned by IT Admin, you can choose one of the following options:

Allow business users to specify the duration – When submitting the Grant Permissions service request, business users can enter desired permission duration, regardless of the default duration.

156


Business users can only request with default duration – When submitting the Grant Permissions service request, the default duration is mandatory and business users cannot change the permission duration.

• If Temporary permissions is assigned by business user, you can set the maximum permission duration. Select The permission cannot be granted longer than, then enter a positive integer in the text box and select Day(s), Month(s), or Year(s) from the drop-down list.

• Notify the person who was granted the permissions about permission expiration – Select this checkbox and define the specified time that the person will be notified in advance. Enter a positive integer and select Day(s) or Month(s) from the drop-down list. Then, select an E-mail Template for the notification to be sent.

12. Grant Permissions – Specify the permissions to the selected users/groups.

• Add users to a SharePoint group (This option is only available when you select Permanent permissions in Permission Duration) – Specify the group permission to a user by adding the user into this group.

• Grant users permission directly – Assign the explicit permission to a user.

Choose to assign the Grant Permissions option by this service or allow the business user to choose the Grant Permissions option when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Grant Permissions option configured here will be applied on the Grant Permission service request.

• Assign by Business User – Allows the business user to configure the Grant Permissions option.

Optionally, configure the following:

• Permissions above the requester's own permissions cannot be granted to others – Select this checkbox to not allow the requester to grant to others permissions that are higher than the requester’s own permissions.

*Note: If the requester grants permissions to himself, the permissions higher than the requester’s own permissions can be granted.

• Exclude SharePoint groups with specified permission levels from the request page – Select this checkbox and select your desired permission levels by selecting the corresponding checkboxes. The SharePoint groups with the selected permission levels will be excluded from the business user’s request page.

*Note: The displayed permission levels are retrieved from Governance Automation Database. To select your desired permission levels, add the permission levels in Settings > SharePoint Permission Level Management first.

13. Send E-mail – Choose to send an e-mail to the new users for notifying his new permission. Select the Send welcome e-mail to the new users checkbox, enter the subject and the body of the e-mail to be a template.

157


Choose to assign the Send E-mail option by this service or allow the business user to choose the Send E-mail option when submitting a service request for this service. Choose from the following:

• Assign by IT Admin – The Send E-mail option configured here will be applied on the Grant Permission service request. Select Show as Read-Only to Business User to allow the business users to see the Send E-mail option in the service request or Hide from Business User to not display the Send E-mail option associated with this service to the business users requesting this service.

• Assign by Business User – Allows the business user to configure the Send E-mail option.






16. Approval Process – Select an approval process from the drop-down menu, or create a new one by clicking the Create New link to redirect to the Approval Process Settings interface without saving any configurations on the current page. This approval process will be triggered when a service request to grant permissions for a specific user is submitted. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.



17. Custom Action – Allows you to modify the approval process. Choose the desired custom action Before approval, After approval, and After execution by using an executable file, PowerShell

158


script file, or assembly. Select the corresponding checkboxes and enter the required information.














159


Remove Permissions Service Configure Remove Permissions services to define the Remove Permissions service request template for the business users. You can specify the users in a certain site collection whose permission you wish to remove.

In the Remove Permissions Services interface or Edit Remove Permissions Services interface, configure the following settings:








5. Service Permissions – Choose Allow all users to user this service to allow this service be requested by any user, or specify the users or groups to have permission to submit requests for this service by choosing Select users/groups to use this service. Then enter the names of the users/groups in the text box. Press Enter to check that the names are valid. Separate multiple users with semicolons.



160





9. Scope – Select the scope you wish to enable:

• For SharePoint on-premises, select a loaded farm and expand the farm tree. Then, select the desired Web applications by selecting the corresponding checkboxes.





• Use SharePoint context to automatically populate the service request scope – Select this checkbox to retrieve and use SharePoint context in service request scope. In Governance Automation Web Part interface, the service request URL will be set to the Web part URL, which will be used as the request scope. The same applies to the Governance Automation App Part interface so that the Site Information Card URL will be used as the request scope. Alternatively, a link can be created within SharePoint to this service request page and the request scope will be set to the parent URL parameter. Make sure that the request URL is in the following format: https://servername:port/GRPermRequest/New?serviceId={serviceID}&parent={parentsiteURL}.


11. Select Users – Specify the users from which you want to delete the permissions. Choose from the following:

• Allow any user/group – Check this option to allow the business user to select any user of the selected scope as the source user.

161




*Note: A User Profile Service must be configured in Governance Automation, or an External Role Source Service must be configured by users


• Select the desired metadata by the selecting corresponding checkboxes. The metadata displayed here is configured in the Metadata interface. You can also click Create on the ribbon to go to the Create Metadata interface. For information on configuring Metadata, see Creating or Editing Metadata.



13. Approval Process – Select an approval process from the drop-down menu, or create a new one by clicking the Create New link to redirect to the Approval Process Settings interface without saving any configurations on the current page. This approval process will be triggered when a service request to remove the permission of a specific user is submitted. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.





162














Custom Service Use the Custom Service to capture required service information as metadata and to execute the desired actions through an executable file, PowerShell script file, or assembly file.

In the Create Custom Service interface or the Edit Custom Service interface, configure the following settings:

163









5. Service Permissions – Choose Allow all users to user this service to allow this service be requested by any user, or specify the users or groups to have permission to submit requests for this service by choosing Select users/groups to use this service. Then enter the names of the users/groups in the text box. Press Enter to check that the names are valid. Separate multiple users with semicolons.




7. Administrator Contact – Specify a user to be the Administrator Contact. This user should be an administrator of Governance Automation and is responsible for service management. Governance Automation will assign a task to the Administrator Contact when an error occurs after the approval process starts. Enter a username in the Administrator Contact text box. Press Enter to check that the name is valid. To also have an e-mail notification be sent to the Administrator Contact when this service encounters an error, configure the Administrator

164


Notification section of Settings. For more information on how to configure the Administrator Notification, see Configuring Administrator Notifications.



• Select the desired metadata by the selecting corresponding checkboxes. The metadata displayed here is configured in the Metadata interface. You can also click Create on the ribbon to go to the Create Metadata interface. For information on configuring Metadata, see Creating or Editing Metadata.



10. Approval Process – Select an approval process from the drop-down menu, or create a new one by clicking the Create New link to redirect to the Approval Process Settings interface without saving any configurations on the current page. This approval process will be triggered when a service request to remove the permission of a specific user is submitted. After selecting the approval process, the approval stage, approver, and approval order are displayed. If the configurations of the selected approval process do not meet your requirement, you can create a new approval process on the basis of the selected approval process. Click Create from This Existing Approval Process and the Approval Process Settings window appears. Configure the settings, and then save and activate the approval process. For more information on configuring the approval process, refer to Creating or Editing Approval Processes.


11. Custom Action – Choose the desired custom action Before approval and/or After approval by using an executable file, PowerShell script file, or assembly. Select the corresponding checkboxes and enter the required information.






165









166


Additional Governance Automation Configurations The following sections detail additional configurations you can make to Governance Automation.

Importing Existing Site Collections and Sites This feature allows you to use Governance Automation to manage existing SharePoint site collections and sites that were not created by Governance Automation.

First, you will configure an export plan to scan for site collections or sites that were not created through Governance Automation. A scan result file that contains the list of site collections and sites is sent to the selected export location. Next, you will go to the export location to modify the scan result file and then import the modified scan result file into Governance Automation.

Click Import Existing Site Collections and Sites in the Settings page to access Import Existing Site Collections and Sites.

Creating an Export Plan To create a new export plan, click Create on the ribbon in the Export Mode tab.

In the Create Export Plan interface, configure the following settings:

1. Plan Name and Description – Enter the name of the plan that you are about to create. Enter an optional description for future reference.

2. Farm Name – Select the farm or My Registered Sites containing the site collections or sites you want to manage. The farms displayed here are based on the logged in user’s permission set in the Account Manager of Governance Automation.

3. Level – Select the Site Collection radio button to generate a configuration template to import site collections to be managed by Governance Automation, or select the Site radio button to generate a configuration template to import sites.

4. Scope – Expand the farm tree or My Registered Sites to select the node that you wish to manage by Governance Automation.

• If Site Collection is selected in the Level section, only the Web application level can be selected from the farm tree.

• If Site is selected in the Level section, the site collection level and the site level can be selected from the farm tree, the Site Collection will not be included in the template file while the Site will be included in the template file.

5. E-mail Notification – Choose the e-mail recipient who will receive the e-mail notification when there is new scan result. Enter the username in the E-mail recipient text box and press Enter to check that the name is valid. Then, select an E-mail template. By default, the Built-in Scan Existing Site Collections or Sites E-mail Template is selected.

167


6. Schedule – Choose whether to execute the export plan on a schedule.

• No schedule – The export plan will be executed when you click Save and Export.

• Configure the schedule – Configure the schedule to execute the export plan.

o Start time – Select the time to start executing the schedule.

o Interval – Define the interval to execute the schedule by entering the value of the interval in the text box then selecting Hour(s), Day(s), Week(s), or Month(s).

7. Export Location – Select a previously configured export location from the drop-down list to store the scan result, or click Add New Location to create a new export location in the New Report Export Location interface. If No schedule is selected in the Schedule section, you can also choose Export the scan result to a local path.

8. When you have finished configuring settings for this export plan, choose one of the following options:

• Click Save to save all of the configurations and return to the Export Mode interface.

• Click Save and Export to save all of the configurations and export the scan result.

• Click Cancel to return to the Export Mode interface without saving any configurations.

Modifying the Scan Result File There are two types of scan result files: the scan site collection result file and the scan site result file.

*Note: Result files are case-sensitive.

Modifying the Scan Site Collection Result File To modify a scan site collection result file, follow the instructions below:

1. Navigate to the location on your local drive where the exported scan result file is saved or the export location where the scan result file is exported.

2. Open the scan result file to view and configure the following field settings:

*Note: All information must be entered exactly, including spaces and capitalization.

• URL – Displays the full URL of the scanned site collection. You can also manually enter the full URLs of other existing site collections.

• Department – Enter the department the site collection belongs to. The department entered here must already be configured in the Governance Automation Settings > Department. For more information about how to configure a department, refer to Manually Adding New Departments.

• Policy Name – Enter the Policy Name of the site collection policy to use to provision the site collection.

• Primary Site Collection Contact – Enter a username to assign a user to be the primary site collection contact.

168


• Secondary Site Collection Contact – Enter a username to assign a user to be the secondary site collection contact.

• Custom Metadata – Enter the value for the custom metadata. Any site collection metadata created in Governance Automation Settings > Metadata can be entered here. For more information about how to configure metadata, refer to Creating or Editing Metadata.

3. Save the file when finished. Then, proceed to Importing the Configured Scan Result File to import the import the scan site collection result file into Governance Automation.

Modifying the Scan Site Result File To modify a scan site result file, follow the instructions below:

1. Navigate to the location on your local drive where the exported scan result file is saved or the export location where the scan result file is exported.

2. Open the scan result file to view and configure the following field settings :

*Note: All information must be entered precisely, including spaces and capitalization.

• URL – Displays the full URL of the scanned site. You can also manually enter the full URLs of other existing sites.

• Site Collection ID – Displays the ID of the site collection that the site belongs to. If you manually enter URLs in the URL column, you must enter the IDs of the site collections where the sites reside.

• Site ID – Displays the ID of the site. If you manually enter URLs in the URL column, you must enter the IDs of the sites.

• Department – Enter the department the site belongs to. The department entered here must already be configured in the Governance Automation Settings > Department. For more information about how to configure a department, refer to Manually Adding New Departments.

3. Save the file when finished. Then, proceed to Importing the Configured Scan Result File to import the import the scan site result file into Governance Automation.

Importing the Configured Scan Result File Next, you will import the configured scan result file and apply it to Governance Automation.

In the Update Existing Site Collection and Site page, follow the instructions below to import a configured scan result file:

1. Click Import Mode on the ribbon to access the import mode.

2. Farm Name – Select the farm where the site collections or sites you want to manage exist from the Farm Name drop-down list.

3. Level – Select the Site Collection radio button to import a configured scan site collection result file, or select the Site radio button to import a configured scan site result file.

169


4. Site Collection Administrator (This section only appears when you select My Registered Sites in Farm Name and select Site Collection in Level) – Specify the site collection administrator who is the administrator for all of the site collections that you wish to import. Enter the Username and Password in the corresponding text boxes.

*Note: The entered username must be the login name.

5. Import Location – Click Browse to locate the configured scan result file.

6. Click Apply on the ribbon.

Validating Data after Importing a Scan File When a configured scan result file is imported into Governance Automation, the information is validated in the backend by using the following rules:

URL (Required) • If the format of URL is valid

• If this site collection or site exists in SharePoint

• If the site collection or site was created by Governance Automation

o Yes – Skip this site collection or site and output the reason in the Comment column.

o No – Update the properties and metadata for this site collection or site.

• If the column is blank

o Yes – Skip and report error

o No – Next process

Department (Required) • Check the department settings option:

o System Department Settings: if department name is defined already

o Use Property in User Profile Service: if the department name is defined in UPS




• If the property exists already



Policy Name (Required) • If it is defined in Policy Management for create site collection


170







Primary Site Collection Contact • Check if it is a valid user

• Should be a single user







Secondary Site Collection Contact • Check if it is a valid user

• Should be a single user







Metadata • If it is a valid header

Valid format is Custom metadata([type]:=[metadata name])

• If the type is valid

• If metadata name exists in the metadata definitions

• If type and metadata name matches

• If the input is required. Check the global metadata definition and see if the metadata should be required

171


o If it is required, but blank

Yes – Skip and report error

No – Next process

o If it is not required and blank

Yes – Do not add this metadata on this site collection

No – Next process

• If the input value is valid

o Single line of text/Multiple lines of text: N/A

o Yes/No: Check whether it is yes/no (case insensitive)

If so – Skip and report error

If not – Next process

o Choice (menu to choose from): Check whether the input matches the value list in the metadata definition (case sensitive)

o Person or Group: Check whether the inputted user/group is valid (case insensitive)

Yes – Next process

No – Skip and report the error field

Configuring Metadata In Governance Automation, you can create metadata that will be available in services for users to select when submitting a request to create a new site collection or site. The metadata created by Governance Automation is stored in the property bag of the site collection/site and can be used to maintain information such as purpose of creation, geography, for compliance and records standards purposes, etc.

*Note: Publish to Directory is a pre-defined metadata which will be automatically added into the Create Site Collection service. You can choose whether or not to add this metadata to the site collection created by Governance Automation when submitting a service request. All of the site collections with Publish to Directory metadata can be displayed in the Public Site Collection Directory. For information on Public Site Collection Directory, see Public Site Collection Directory.

To manage metadata created by Governance Automation, in the Settings page, click Metadata.

Searching and Filtering Metadata To change the number of rows displayed, use the Show rows drop-down menu in the upper right-hand corner. To sort the metadata, click the sort ( ) button in a column heading such as Metadata Name,

172


Default Value, Index Metadata, Last Modified Time, and Created By then select Ascending or Descending.

You can customize how the metadata are displayed in a number of different ways:

• Search – Allows you to filter metadata displayed by the keyword you designate. The Metadata Name column and the Created By column support to search for the desired metadata, and only the content in the column displayed in the current view can be searched.

• Manage columns ( ) – You can manage which columns are displayed in the list so that only information you want to see is displayed. Click the manage columns ( ) button, and then select the checkbox next to the column name to have that column shown in the list.


To view details of a metadata, click the metadata name.

Creating or Editing Metadata To create a new metadata, click Create on the ribbon. You can choose to create metadata for Create Site Collection service requests or Create Site service requests by clicking corresponding hyperlinks under the Metadata Type heading.

To modify previously configured metadata, select the metadata, and click Edit on the ribbon.

Configure the following settings when creating or editing metadata:

1. Name and Type – Enter a name for the new metadata into the Metadata Name text box. All metadata created by Governance Automation will have the prefix GA_. Then select the type of information you wish to store in this metadata by clicking the corresponding radio button. Choose from Single line of text, Multiple lines of text, Yes/No (check box), Choice (menu to choose from), Person or Group or Managed Metadata.

2. Additional Column Settings – Configure additional settings for the new metadata. Enter an optional description into the Description text box. Then configure the following settings depending on your selection in The type of information in this metadata is field.

• Single line of text – Enter the desired text into the Default Value text box. Select who assigns this metadata from the drop-down menu. Choose between Assign by Business User and Assign by IT Admin. If Assign by Business User is selected, choose to require input from the business user by selecting the Require Business User Input checkbox.

• Multiple lines of text – Enter the desired text into the Default Value. You may enter multiple lines of text by hitting the Enter key on your keyboard. Select who assigns this metadata from the drop-down menu. Choose between Assign by Business User and Assign by IT Admin. If Assign by Business User is selected, choose to require input from the business user by selecting the Require Business User Input checkbox.

173


• Yes/No (checkbox) – Choose to Enable Terms and Conditions Agreement by selecting the checkbox. If the option is enabled, enter the desired terms and conditions in the text box. Select Yes or No as the Default Value from the drop-down menu. Select who assigns this metadata from the drop-down menu. Choose between Assign by Business User and Assign by IT Admin. If Assign by Business User is selected, choose to require input from the business user by selecting the Require Business User Input checkbox.

• Choice (a selection to choose from) – Enter the choices you wish to provide in the Type each choice on a separate line text box. Choose the type of selections to provide from the following: Drop-down Menu, Radio Buttons or Checkboxes (allow multiple selections). Select who assigns this metadata from the drop-down menu. Choose between Assign by Business User and Assign by IT Admin. If Assign by Business User is selected, choose to require input from the business user by selecting the Require Business User Input checkbox.

• Person or Group – Enter the usernames or group names in the Default Value field. For multiple entries, separate each entry with a semicolon. Select who assigns this metadata from the drop-down menu. Choose between Assign by Business User and Assign by IT Admin. If Assign by Business User is selected, choose to require input from the business user by selecting the Require Business User Input checkbox.

• Managed Metadata – Configure the following settings for Managed Metadata.

o Multiple Value Field – Select the Allow multiple values checkbox if you wish to create multiple terms for the site collection created by Governance Automation.

o Term Set Settings – Select a farm from the Select farm and term set drop-down menu to load the term sets where you can retrieve the terms. Expand the Managed Metadata Service tree to select the term set where to choose the term by clicking the term set name. The selected term set is highlighted in orange.

o Default Value − Enter your desired terms as the default values in the text box or select a default value by selecting the select ( ) button to access the Select Default interface. Expand the term set tree to select the desired term and click the Add button in the lower left-corner of the Select Default interface.

Choose between Assign by Business User and Assign by IT Admin. If Assign by Business User is selected, choose to require input from the business user by selecting the Require Business User Input checkbox.

3. Display Metadata on Reports – Choose whether or not to display this metadata on the Site Collection Report/Site Report of Governance Automation.

• Yes – The metadata will be displayed on Site Collection Report/Site Report, allowing for faster filtering, searching and sorting.

• No – The metadata will not be displayed on Site Collection Report/Site Report, and cannot be filtered, searched, or sorted.

4. Click Save to save the configurations and return to the Create Metadata interface, and click Cancel to return to the Create Metadata interface without saving any configurations.

174


*Note: When you finish editing the metadata that is applied to existing services, click Save and Update to All Applied Services to save and update this metadata for the corresponding services.

Deleting Metadata To delete a metadata, select a previously configured metadata, and then click Delete on the ribbon. A confirmation window will pop up and ask if you are sure you want to proceed with the deletion. Click OK to delete the selected metadata, or click Cancel to return to the Metadata Management interface without deleting the selected property.

Configuring Questionnaires Use Questionnaire Management to configure questionnaires, which guide requesters to appropriate services. In a questionnaire, you can add your desired questions, define the order that the questions appear, customize the logical relationship for the questions, add the answer criterion, and select the services that will be visible to the requesters.

*Note: The Questionnaire Management feature is not fully supported on Internet Explorer 8. To use this feature, AvePoint recommends that you use Google Chrome or Internet Explorer 9 or above to manage questionnaires.

To access Questionnaire Management settings, in the Settings page, click Questionnaire Management.

Displaying and Searching Questionnaires To change the number of questionnaires displayed, use the Show rows drop-down menu in the upper right-hand corner.

To search the displayed questionnaire, enter the keyword in the Search text box and click the search

( ) button.

Creating or Editing Questionnaires To create a new questionnaire, click Create on the ribbon. To modify a previously configured questionnaire, select the desired questionnaire, and click Edit on the ribbon.

In the Create Questionnaire interface or Edit Questionnaire interface, configure the following settings:

1. Name and Description – Enter the name for the questionnaire that you are about to create. Enter an optional description for future reference.

2. Language – Choose the language for this questionnaire. When starting a request, the questionnaires can be filtered according to their languages.

3. Questionnaire Category – Categories are used to organize your questionnaires. Select an existing category from the drop-down menu or create a new category for this questionnaire by clicking Create New then configuring the new category in the Create Category interface.

175


4. Questionnaire Permissions – Choose Allow all users to use this questionnaire to allow this questionnaire be viewed by any user, or select the users or groups that have permissions to access this questionnaire by choosing Select users/groups to use this questionnaire and enter the names of the users/groups in the text box. Press Enter to check that the names are valid.


6. Questions – Define the questions for this questionnaire.

• To create a new question, click Add Question and then configure the following settings in the Add Question interface.

a. Question – Enter your desired question and select the answer type, Drop-down Menu, Radio Buttons, or Managed metadata.

b. Answer Settings – Enter the answers for the question. Enter each answer on a separate line. You can also define a default answer for the question.

c. Click Save to save this question.

• To edit a previously created question, click the edit ( ) button after the question name and then modify the settings in the Edit Question interface.

• To delete a previously created question, click the delete ( ) button after the question name.


8. Follow the steps below to configure the logic diagram.

a. Drag your desired question from the left pane to the Start point of the right pane.

b. Drag another question under the arrow of one answer for the question above to determine the logical relationship.

c. Repeat the step above to add multiple questions.

*Note: You can add the same question to multiple logical flows on the right pane, but a question can only be added into a logical flow once.

d. Drag your desired service to the end point of each logical flow

e. If there are no services that fit the logical flow, click Add End Points Automatically to end all points with No Service.

The previously created questions and the services in the left pane are supported to search. Enter the keyword of the question name or service name in the text box under Questions or Services and click the search ( ) button to search it.

Click the remove ( ) button to remove a question from the logic diagram.

9. When you have finished configuring settings for this questionnaire, choose one of the following options:

• Click the arrow on the left-hand side to go to previous steps to review and modify your configurations.

176


• Click Save to save the questionnaire as a draft and return to the Questionnaire Management interface.

• Click Save and Activate to save all of the configurations and activate this questionnaire.

• Click Cancel to return to the Questionnaire Management interface without saving any configurations.

Activating, Deactivating, and Deleting Questionnaires To activate an inactive questionnaire, select the questionnaire, and then click Activate on the ribbon.

To deactivate an active questionnaire, select the questionnaire, and then click Deactivate on the ribbon.

To delete a questionnaire, select a previously configured questionnaire, and then click Delete on the ribbon. A confirmation window will pop up and ask if you are sure you want to proceed with the deletion. Click OK to delete the selected questionnaire, or click Cancel to return to the Questionnaire Management interface without deleting the selected questionnaire.

Configuring E-mail Templates *Note: For Governance Automation to send notification e-mails, outbound e-mail SMTP must be configured in Send E-Mail Settings in DocAve. For information on configuring the Send E-Mail Settings in DocAve, see the User Notification Settings section of the DocAve Control Panel Reference Guide.

Governance Automation comes with built-in e-mail templates. If desired, you can customize notification e-mails sent by Governance Automation, such as when a request is approved or when a task is assigned. Different e-mail templates are used for different notifications.

To access E-mail Templates settings, in the Settings page, click E-mail Templates.

Searching and Filtering E-mail Templates To change the number of rows displayed, use the Show rows drop-down menu in the upper right-hand corner. To sort the E-mail Templates, click the sort ( ) button in a column heading such as E-mail Template, E-mail Template Type, and Description. You can also filter the E-mail Template Type by clicking the filter ( ) button in the column heading.

To search displayed e-mail template, enter the keyword in the Search text box and then click the search

( ) button.

Creating or Editing E-mail Templates To create a new e-mail template, click Create on the ribbon. To modify a previously configured e-mail template, select the e-mail template, and click Edit on the ribbon.

177



In the Create E-mail Template or Edit E-mail Template interface, configure the following settings:

1. Enter a desired E-mail Template Name for e-mail template. Then enter an optional Description for the e-mail template for future reference.

2. Select an E-mail Template Type from the drop-down menu to designate when the e-mail template can be used in Governance Automation.

3. Subject – Enter a subject name of the e-mail notification for the e-mail template. You can insert reference in the Subject by clicking the Insert Reference hyperlink. A Reference is a parameter that will call up the corresponding bit of information for which it is named specific to each individual service request.

4. Message Body – Customize the message body of the e-mail notification for the e-mail template. You can insert reference in the Message Body by clicking the Insert Reference hyperlink. A Reference is a parameter that will call up the corresponding bit of information for which it is named specific to each individual service request.

5. Click Save to save the configurations and return to the E-mail Templates interface, or click Cancel to return to the E-mail Templates interface without saving any configurations.

Deleting E-mail Templates To delete an e-mail template from Governance Automation, select an e-mail template from the e-mail template list, and then click Delete on the ribbon. A confirmation window will pop up and ask if you are sure you want to proceed with the deletion. Click OK to delete the selected e-mail template, or click Cancel to return to the E-mail Template interface without deleting the selected e-mail template.

Configuring the Execution Schedule Use the Execution schedule feature to define when Governance Automation executes service requests.

To access Execution Schedule settings, in the Settings page, click Execution Schedule.

Displaying and Searching Execution Schedules To change the number of execution schedules displayed, use the Show rows drop-down menu in the upper right-hand corner.

To search the displayed execution schedules, enter the keyword in the Search text box and click the

search ( ) button.

Creating or Editing Execution Schedules To create a new execution schedule, click Create on the ribbon. To modify a previously configured execution schedule, select the desired execution schedule, and click Edit on the ribbon.

178


In the Create Execution Schedule interface or Edit Execution Schedule interface, configure the following settings:

1. Execution Schedule Name and Description – Enter a desired Name for the execution schedule. Then enter an optional Description for the execution schedule for future reference.

2. Define Execution Schedule – Define an execution schedule for a Service by selecting your desired days and hours. Then, click Add to List to add it to the execution schedule list below, or click Clear Settings to reset your execution schedule.

3. Time Zone – Select your time zone for the execution schedule.

4. Click Save to save the configurations and return to the Execution Schedule interface, or click Cancel to return to the Execution Schedule interface without saving any configurations.

Deleting Execution Schedules To delete an execution schedule, select a previously configured execution schedule, and then click Delete on the ribbon. A confirmation window will pop up and ask if you are sure you want to proceed with the deletion. Click OK to delete the selected execution schedule, or click Cancel to return to the Execution Schedule interface without deleting the selected execution schedule.

Configuring Request Access Settings When business users attempt to access SharePoint 2010/SharePoint 2013 site collections or sites that they do not have permission to access, they are brought to the SharePoint Access Denied page. With the Request Access solution deployed and the Request Access Settings configured, SharePoint users are redirected from the SharePoint Access Denied page to the Governance Automation Grant Permissions request interface, where they can then request access to the site collection or site. This enables business users to submit Grant Permissions service requests without having to leave their SharePoint environment.

Preparing SharePoint Before configuring Request Access Settings, you must complete the following preparations in SharePoint:

1. Configuring Outgoing E-mail Settings

2. Configuring Access Request Settings

3. Deploying the Governance Automation Request Access Solution

Configuring Outgoing E-mail Settings You can skip this section if you have completed these steps previously. To configure outgoing e-mail settings, complete the following steps:

179


1. In SharePoint Central Administration, navigate to Application Management > Manage web applications.

2. Select the Web application that you will apply the request access feature to and click General Settings > Outgoing E-mail.

3. In the Web Application Outgoing E-mail Settings interface, enter the Outbound SMTP server, From address, Reply-to address, and select the Character set.


Configuring Access Request Settings After configuring the outgoing e-mail settings, follow the instructions below to configure the access request settings:

1. In the site that you will apply the request access to, click Site Actions on the ribbon and click Site Permissions.

2. Click Manage Access Requests on the ribbon.

3. In the Manage Access Requests interface, configure the following settings:

a. Select the Allow requests for access checkbox.

b. Enter the e-mail address that will receive the requests for access.

c. Click OK to save your configurations.

Deploying the Governance Automation Request Access Solution The solution GARequestAccess.wsp (for SharePoint 2010) and GARequestAccessSP2013.wsp (for SharePoint 2013) reside in the directory …\AvePoint\GovernanceAutomation\SharePoint Solutions on Governance Automation server.

Complete the following steps to deploy this solution:

1. To deploy the solution on a SharePoint Web-front end server, copy the solution file to the SharePoint Web-front end server first.

2. On the SharePoint server, navigate to SharePoint 2010 Management Shell or SharePoint 2013 Management Shell. Right-click it and select Run as administrator.


stsadm –o addsolution –filename “C:\Program Files\AvePoint\GovernanceAutomation\SharePoint Solutions\GARequestAccess.wsp”

Figure 18: Deploying the Governance Automation Request Access Solution.

180


*Note: Replace C:\Program Files\AvePoint\GovernanceAutomation\SharePoint Solutions\GARequestAccess.wsp with the path where the solution is stored.

*Note: For SharePoint 2013 environment, the solution file is GARequestAccessSP2013.wsp.



7. Click garequestaccess.wsp or garequestaccesssp2013.wsp, and then click Deploy Solution to deploy it.

8. If you are using SharePoint 2013, complete the following steps after the solution deployment is finished.

a. Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\GA.

b. Right-click the AccessDenied.aspx file and select Copy.

c. Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS and paste the copied .aspx file into this directory.

Configuring Request Access Settings To access Request Access Settings, in the Settings page, click Request Access Settings. Then, complete the following steps:

1. Select a farm from the drop-down list on the left pane.

2. Expand the farm tree to select your desired Web application or site collection by selecting the corresponding radio button. The title and URL of the selected Web application or site collection are displayed on the right pane.

3. Select a previously configured Grant Permissions service from the drop-down list on the right pane. For information about how to configure a Grant Permissions service, refer to Grant Permissions Service.

*Note: If you select a site collection beneath a Web application that already had a Grant Permissions service applied to it, the name of the Grant Permissions service is displayed. You can also apply a unique Grant Permissions service to the selected site collection by selecting Apply a unique Grant Permissions service to this node checkbox and selecting a previously configured service from the drop-down list.

4. Click Apply on the bottom to apply the settings.

5. If you are configuring the Request Access Settings for a SharePoint 2010 Web application for the first time, proceed to Restarting IIS (for SharePoint 2010 Only).

181


Restarting IIS (for SharePoint 2010 Only) If configuring Request Access Settings for a SharePoint 2010 Web application for the first time, you must manually restart the IIS to apply your configurations on all of your SharePoint servers.

1. Navigate to Start > All Programs > Administrative Tools > Internet Information Services (IIS) Manager.

2. Right-click the Web application in Sites.

3. Click Manage Web Site, and then click Restart.

Exporting and Importing Configuration Data Use Export and Import Configuration Data to manage Governance Automation configuration data between different environments. The configuration data includes global settings, approval process, policies, and services.

*Note: The source environment and the destination environment must be running identical versions of Governance Automation.

Click Export and Import Configuration Data in the Settings page to access Export and Import Configuration Data.

Exporting Configuration Data In the Export and Import Configuration Data page, follow the instructions below to export your desired configuration data:

1. Click Export Mode on the ribbon.

2. Export Location – Choose the path to store the exported file that contains the exported data.

• Select Export to a local path to store the exported file in a local path.

• Select Export to an export location to store the exported data in an export location. Select a previously configured export location from the drop-down menu or click Add New Location to create a new one. This will bring you to the New Report Export Location interface without saving any of the configurations you have made for this service.

3. Scope – Expand Global settings, Approval processes, Policies, and Services to select your desired configuration data by selecting the corresponding checkboxes. Global settings contain User Profile Service settings, Security settings, Departments, Metadata, E-mail templates, and Execution schedules. Approval processes, Policies, and Services contains all of the previously configured approval processes, policies, Create Site Collection services, and Create Site services.

4. Click Export on the ribbon to export the selected configuration data.

182


Importing Configuration Data In the Export and Import Configuration Data page, follow the instructions below to import your desired configuration data:

1. Click Import Mode on the ribbon.

2. Import Location – Click Browse to locate the configuration file that you wish to import.

3. Click Retrieve Data to retrieve the data in the imported configuration file.

4. Mappings – Configure mappings for the environment where the data is exported and the environment where the data will be imported.

• Domain mapping – Enter the domain name of the environment where the data will be imported.

• Farm mapping – Select the farm of the environment where the data will be imported.

• User Profile Service Application mapping – Expand the farm to view the User Profile Service Application of the environment where the data is exported. Then, select the User Profile Service Application of the environment where the data will be imported.

• Web application mapping – Select the Web application in which the data will be imported.

• Content database mapping – Expand the Web application to view the content database of the Web application from which the data is exported. Then, select the content database of the Web application in which the data will be imported.

5. Import Scope – Select the data that you wish to import by selecting the corresponding checkboxes.

6. Click Apply on the ribbon to start importing the data to the selected environment.

Configuring External Workflow Integration Settings Configure External Workflow Integration Management to integrate SharePoint on-premises 2010/2013 Designer Workflow or Nintex Workflow with Governance Automation approval process. Currently, only the following services support integration with SharePoint Designer Workflow or Nintex Workflow:

• Create Site Collection

• Create Site

• Create My Site

• Grant Permissions

• Remove Permissions

• Content Move

183


Starting Microsoft SharePoint Foundation Sandboxed Code Service Before configuring the External Workflow Integration Management settings, you must start Microsoft SharePoint Foundation Sandboxed Code Service.

1. Navigate to SharePoint Central Administration > System Settings > Manage services on server.

2. In the Action column of Microsoft SharePoint Foundation Sandboxed Code Service, click Start.

To access External Workflow Integration Management settings, in the Settings page, click External Workflow Integration Management.

In External Workflow Integration Management, you can create a new external workflow integration profile, edit a previously configured profile, or delete a previously configured profile. For details on creating or editing a profile, refer to Creating or Editing External Workflow Integration Profiles.

Displaying and Searching External Workflow Integration Profiles To change the number of profiles displayed, use the Show rows drop-down menu in the upper-right corner.

To search the displayed profiles, enter the keyword in the Search text box and click the search ( ) button.

Creating or Editing External Workflow Integration Profiles To create a new profile, click Create on the ribbon. To modify a previously configured profile, select the desired profile, and click Edit on the ribbon.

In the Create External Workflow Integration Profile interface or Edit External Workflow Integration Profile interface, configure the following settings:

1. Name and Description – Enter the name and description for the external workflow integration profile.

2. Farm – Select a farm to define the scope of the site collection whose workflow will be integrated with Governance Automation approval process.

3. Site URL – Enter a site URL in the text box. The solution GASPWorkflowIntegration.wsp will be automatically deployed to the site collection of this site. The workflow related lists will be created in this site.

4. Choose one of the options on the ribbon:

• Save – Click Save to save the configurations and deploy the solution later.

• Save and Deploy Solution – Click Save and Deploy Solution to save the configurations and have Governance Automation deploy the solution immediately.

184


• Cancel – Click Cancel to go back to the External Workflow Integration Management interface without saving any configurations.

Deleting External Workflow Integration Profiles To delete a profile, select a previously configured profile, and then click Delete on the ribbon. A confirmation window will pop up and ask if you are sure you want to proceed with the deletion. Click OK to delete the selected profile, or click Cancel to return to the External Workflow Integration Management interface without deleting the selected profile.

Creating External Workflows in SharePoint After configuring the external workflow integration profile, complete the following steps to create the external workflow in SharePoint:

Creating a SharePoint 2013 Designer Workflow To create a SharePoint 2013 Designer Workflow that will be integrated with Governance Automation approval process, complete the following steps:

1. Export Governance Automation IIS certificate. For more information about how to export the certificate, refer to Export Governance Automation IIS certificate.

2. Install Governance Automation IIS certificate on SharePoint Server.

a. Navigate to the SharePoint server. Copy the exported certificate file to this server.

b. Double-click the certificate file and click Install Certificate… in the General tab.

c. In the Welcome to the Certificate Import Wizard interface, click Next.

d. In the Certificate Store window, choose Place all certificates in the following store.

e. Click Browse… and select Trusted Root Certification Authorities in the new window. Then, click OK to go back to the Certificate Store window.

f. Click Next to go to the Completing the Certificate Import Wizard window. Click Finish to finish the certificate installation.

g. A window appears to remind that the import is successful.

3. Navigate to Microsoft SharePoint Designer and open the site whose URL is entered in the configured external workflow integration profile.

4. Click Workflows on the left pane.

5. Click List Workflow on the ribbon and select the Service Requests list.

6. In the Create List Workflow – Service Requests window, enter the name and description for the workflow that you are about to create. Select SharePoint 2013 Workflow as the platform type. Then, Click OK.

7. Click Action on the ribbon and select Call HTTP Web Service from Core Actions.

185


8. Click the this link and the Call HTTP Web Service window appears.

9. Click the ellipsis ( ) button to go to the String Builder window.

10. In the Name field, enter the URL in one of the following formats for approving or rejecting the request:

• Approve – https://GAhost:port /api/ApproveGARequest?workflowinstanceid=

• Reject – https://GAhost:port /api/RejectGARequest?workflowinstanceid=

o GAhost – Be replaced with the hostname of the machine where Governance Automation is installed.

o port – Be replaced with the port used to access Governance Automation Web site.

11. Click Add or Change Lookup to go to the Lookup for String window.

a. In the Data source field, select Workflow Context from the drop-down list.

b. In the Field from source field, select Instance ID from the drop-down list.

c. Click OK to go back to the Lookup for String window.

12. Click OK to save configurations and go back to the Call HTTP Web Service window.

13. Select HTTP GET as the HTTP method, then Click OK to save the action.

14. Configure other workflow settings if desired, then click Save on the ribbon to save the workflow.

15. Click Publish on the ribbon to publish the workflow. The published workflow will be available to select in an approval process.

Creating a SharePoint 2010 Designer Workflow To create a SharePoint 2010 Designer Workflow that will be integrated with Governance Automation approval process, complete the following steps:

1. On the Governance Automation server, navigate to …\AvePoint\GovernanceAutomation\SharePointSolutions\SharePoint Workflow Integration.

2. Find the GASharePointWorkflowActivity.wsp file, right-click the file, and select Copy.

3. Navigate to the server where SharePoint is installed and paste the copied .wsp file into your desired directory.

4. Navigate to Start > Run > enter cmd in the Open text box and click OK.



186


Figure 19: Deploying the solution (1).


stsadm.exe -o addsolution -filename C:\ GASharePointWorkflowActivity.wsp

Figure 20: Deploying the solution (2).

*Note: C:\GASharePointWorkflowActivity.wsp should be replaced with the path where the solution is stored.


12. On the Governance Automation server, navigate to …\AvePoint\GovernanceAutomation\SharePointSolutions\SharePoint Workflow Integration.

13. Find the CallGAWebService.Actions file, right-click the file, and select Copy.

14. Go to the server where SharePoint is installed, navigate to …\Microsoft Shared\Web Server Extensions\14\TEMPLATE\1033\Workflow and paste the copied file into this directory.

15. Navigate to SharePoint Central Administration > System Settings > Manage farm solutions.

16. Click SharePointWorkflowActivity.wsp and click Deploy Solution.

17. In the Deploy Solution interface, choose to deploy the solution to all content Web applications or select a Web application to deploy the solution.

If the solution is deployed to a specific Web application, complete the following steps:

a. Navigate to Administrative Tools > Internet Information Services (IIS) Manager.

b. Expand the tree and find the Web application under the Sites node.

c. Right-click the Web application and select Explore.

d. In the pop-up window, find the web.config file and open it with Notepad.

187


e. Navigate to the server where Governance Automation is installed, navigate to …\AvePoint\GovernanceAutomation\SharePointSolutions\SharePoint Workflow Integration.

f. Find the Config.xml file, open it with Notepad, and copy the content of the file.

g. Go back to the web.config file, find the attribute </authorizedTypes> and paste the copied content to the attribute.

Figure 21: Modifying the web.config file.

h. Save and close the web.config file.

If the solution is deployed to multiple Web applications, repeat the steps above to configure the web.config file for each Web application.

18. Navigate to Start > Command Prompt, right-click Command Prompt and click Run as administrator.

19. In the Command Prompt window, enter iisreset and press Enter.

20. Navigate to Microsoft SharePoint Designer and open the site whose URL is entered in the configured external workflow integration profile.

21. Click Workflows on the left pane.

22. Click List Workflow on the ribbon and select the Service Requests list.

23. In the Create List Workflow – Service Requests window, enter the name and description for the workflow that you are about to create. Then, Click OK.

24. Click Action on the ribbon and select Call Governance Automation Web Service. The action contains two parameters:

• Governance Automation Web Service URL – Click Governance Automation Web Service URL to enter the URL in the format of https://GAhost:port/gawebservice.asmx.

o GAhost – Be replaced with the hostname of the machine where Governance Automation is installed.

o port – Be replaced with the port used to access Governance Automation Web site.

• Approval Result – Click Approval Result to select Approved or Rejected from the drop-down list.

25. Click Save on the ribbon to save the workflow.

26. Click Publish on the ribbon to publish the workflow. The published workflow will be available to select in an approval process.

188


Creating a Nintex Workflow To create a Nintex Workflow that will be integrated with Governance Automation approval process, complete the following steps:

1. Export Governance Automation IIS certificate.

a. On the Governance Automation service, navigate to Start > Internet Information Services (IIS) Manager.

b. On the left pane, click the local host.

c. Double-click Server Certificates in the middle.

d. Find the IIS certificate of your Governance Automation and double-click it. The Certificate window appears.

e. In the Details tab, click Copy to File…. The Certificate Export Wizard window appears.

f. In the Welcome to the Certificate Export Wizard interface, click Next.

g. In the Export Private Key interface, select No, do not export the private key. Click Next.

h. In the Export File Format interface, select DER encoded binary X.509 (.CER). Click Next.

i. In the File to Export interface, click Browse… to select the location where the certificate file will be exported. Click Next.

j. In the Completing the Certificate Export Wizard interface, click Finish.

k. A window appears to remind that the export is successful.

2. Import Governance Automation IIS certificate to SharePoint Server.

a. Navigate to the SharePoint server. Copy the exported certificate file to this server.

b. Navigate to SharePoint Central Administration > Security > General Security > Manage trust. You are brought to the Trust Relationships tab.

c. Click New on the ribbon.

d. In the Establish Trust Relationship window, configure the following settings:

o Name – Enter the name for this trust relationship.

o Root Authority Certificate – Click Browse… and select the Governance Automation IIS certificate that has been copied to this server.

e. Click OK to finish the certificate import.

3. Activate Nintex Workflow.

a. Navigate to SharePoint Central Administration > Nintex Workflow Management > Web Application activation.

b. Select the Web application on which you wish to activate Nintex Workflow. Click Activate.

c. Go to the site whose URL has been entered in the external workflow integration profile.

189


d. Navigate to Site Settings > Site Collection Administration > Site collection features.

e. Find Nintex Workflow 2013 or Nintex Workflow 2010 and click Activate.

f. Navigate to Site Settings > Site Actions > Manage site features.

g. Find Nintex Workflow 2013 or Nintex Workflow 2010 and click Activate.

4. Create a Nintex Workflow in the list Service Requests.

a. Go to the site whose URL has been entered in the external workflow integration profile.

b. Navigate to the list Service Requests.

c. Click the List tab on the ribbon.

d. Click Workflow Settings and select Create a Workflow in Nintex Workflow.

e. Create a custom workflow that is associated with the action Call web service. Configure the action settings:

i. URL – Enter the URL in the format of https://GAHost:GAPort/gawebservice.asmx.

GAHost – The hostname of the Governance Automation server.

GAPort – The port number of Governance Automation Web site.

ii. Web method – Click Refresh and select FinishTask from the drop-down list.

iii. WorkflowInstanceID (guid) – Click the insert reference ( ) button. The Insert Reference window appears. In the Common tab, select Workflow Instance ID. Click OK to insert the selected reference and close the Insert Reference window.

iv. IsApproved (boolean) – Enter True or False. True means that the request will be approved. False means that the request will be rejected.

v. Click Save on the ribbon to save your configurations.

f. Configure other desired actions and click Publish on the ribbon to publish the workflow. The published workflow will be available to select in an approval process.

Hiding or Revealing Sections to Business Users This feature helps you define which sections are visible to business users in the landing page.

Click Business User Features Activation or Deactivation in the Settings page to access Business User Features Activation or Deactivation.

In the Business User Features Activation or Deactivation interface, select the sections that you wish the business users to view by selecting the corresponding checkboxes. Click Save on the ribbon to save your configurations.

190


Configuring the Report Export Location The Report Export Location allows you to select a storage location to export Governance Automation reports. For information on the Governance Automation reports, see Audit Reports.

To access Report Export Location settings for Governance Automation, in the Settings page, click Report Export Location.

Searching Report Export Locations In this interface, you can search your desired Report Export Locations by designated keywords. Enter the

keyword in the Search text box and then click the search ( ) button. The Location Name and Description column support to search for export locations, and only the content in the column displayed in the current view can be searched.

Creating or Editing Report Export Locations To create a new report export location, click Create on the ribbon. To modify a previously configured export location, select the export location, and click Edit on the ribbon.

In the New Report Export Location or Edit Report Export Location interface, configure the following settings:

1. Name and Description ‒ Enter a Name for the report export location. Then enter an optional Description for the export location for future reference.

2. Path ‒ The export location can be a file share, Storage Area Network (SAN), or Network-Attached Storage (NAS). Enter the UNC Path in the following format:

\\admin-PC\c$\data or \\admin-PC\shared folder

*Note: The path you entered must be an existing one.

3. Enter the Username and Password in the corresponding text boxes. Then click Validation Test. DocAve will test the path and user information to make sure they are valid.

4. Click Save to save the configurations and return to the Report Export Location interface, or click Cancel to return back to Report Export Location interface without saving any changes.

Deleting Report Export Locations To delete a report export location from Governance Automation, select an export location from the list of previously configured export locations, and then click Delete on the ribbon. A confirmation window will pop up to ask if you are sure you want to proceed with the deletion. Click OK to delete the selected export location, or click Cancel to return to the Export Location interface without deleting the selected export location.

191


Configuring SharePoint Permission Levels Permission levels allow you to assign a particular set of permissions to users and SharePoint groups so that they can perform specific actions on your site.

To access SharePoint Permission Level Management for Governance Automation, in the Settings page, click SharePoint Permission Level Management.

Displaying and Searching Permission Levels To change the number of rows displayed, use the Show rows drop-down menu in the upper-right corner.

To search the displayed SharePoint Permission Level, enter the keyword in the Search text box and click

the search ( ) button.

Creating or Editing Permission Levels To create a new permission level, click Create on the ribbon. To modify a previously configured permission level, select the desired permission level, and click Edit on the ribbon.

In the Create SharePoint Permission Level interface or Edit SharePoint Permission Level interface, configure the following settings:

1. Name and Description – Enter a desired Name for the permission level. Then enter an optional Description for the permission level for future reference.

2. Permissions – Add permission to the permission level by selecting corresponding checkboxes.

3. Click Save to save the configurations and return to the SharePoint Permission Level Management interface, or click Cancel to return to the SharePoint Permission Level Management interface without saving any configurations.

Deleting Permission Levels To delete a permission level from Governance Automation, select a previously configured permission level, and then click Delete on the ribbon. A confirmation window will pop up and ask if you are sure you want to proceed with the deletion. Click OK to delete the selected permission level, or click Cancel to return to the SharePoint Permission Level Management interface without deleting the selected permission level.

Configuring Administrator Notifications Administrator Notifications inform the Administrator Contact should any service request encounter an error.

192


To access Administrator Notification settings, in the Settings page, click Administrator Notification. Click Cancel on the ribbon to close the Administrator Notification interface.

Follow the instructions below to configure the Administrator Notification settings:

1. Alternate Administrator Contact – Select a user to be an alternate Administrator Contact in case that the Administrator Contact is unavailable. Enter the username in the text box. Press Enter to check that the username is valid.

2. E-mail Settings – Allows you to send an e-mail to the Administrator Contact once a task has been assigned to that Administrator Contact when an error occurs. Select the Notify the service request Administrator Contact when the error task is assigned checkbox, and select an e-mail template from the drop-down menu for this e-mail notification.

3. Duration and Escalation – Select the Enable Duration and Escalation checkbox to notify another administrator contact if a task has not been handled within the specified amount of time. Make sure that the user receiving the escalated tasks has enough permission to handle all tasks.

b. Enter a positive integer into the Duration text box for the deadline, and select either Day(s) or Week(s) as the time unit for the duration.

c. Escalation – Select the action that the escalation will trigger from the drop-down menu.

• Notify – The specified user will be notified when the task is escalated. Enter the username in the text box. Press Enter to check that the username is valid. You can also enter $ in the text box to choose Manager of Approver. The manager of the approver of the task will be notified when the task is escalated.

• Re-assign to – The task will be re-assigned to the specified users when the task is escalated. Enter the username in the text box. Press Enter to check that the username is valid. You can also enter $ in the text box and choose Manager of Approver. The task will be re-assigned to the manager of the approver.

d. E-mail Template – Select an e-mail template from the drop-down menu.

4. Click Save to save the configurations and return to the Settings interface, or click Cancel to return to the System Settings interface without saving any changes.

Configuring the Timer Service The Governance Automation Timer Service runs synchronization and scans on a default schedule. If you are about to set custom schedules to synchronize or scan, use Timer Service Configuration Management to manually configure the Governance Automation Timer Service schedules. After saving the configurations for the Timer Service settings, they take effect immediately, without the need to restart the Governance Automation Timer Service.

To access Timer Service Configuration Management settings, in the Settings page, click Timer Service Configuration Management.

In the Timer Service Configuration Management interface, configure the following settings:

193


1. Site Collection Status Scan Job – Select Enable site collection status scan job to enable this job. The site collection status scan job monitors the status of site collections, including inactivity, lease expiration, locking, and deletion. Configure the interval to perform the job by entering your desired value and selecting Minute(s), Hour(s), Day(s), Week(s), Month(s), or Year(s).

2. Tree Cache Synchronization Job – Select Enable tree cache synchronization job to enable this job. The tree cache synchronization job synchronizes the tree cache information in Governance Automation database. Configure the interval to perform the job by entering your desired value and selecting Minute(s), Hour(s), Day(s), Week(s), Month(s), or Year(s).

3. Archive Site Collection Content Scan Job – Select Enable archive site collection content scan job to enable this job. The archive site collection content scan job checks if there are contents in the site collections need to be archived. Configure the interval to perform the job by entering your desired value and selecting Minute(s), Hour(s), Day(s), Week(s), Month(s), or Year(s).

4. Site Information Synchronization Job – Select Enable site information synchronization job to enable this job. The site information synchronization job synchronizes the related site information in Governance Automation database. Configure the interval to perform the job by entering your desired value and selecting Minute(s), Hour(s), Day(s), Week(s), Month(s), or Year(s).

5. Site Collection Information Synchronization Job – Select Enable site collection information synchronization job to enable this job. The site collection information synchronization job synchronizes the related site collection information in Governance Automation database. Configure the interval to perform the job by entering your desired value and selecting Minute(s), Hour(s), Day(s), Week(s), Month(s), or Year(s).

6. User Profile Service Synchronization Job – Select Enable User Profile Service synchronization job to enable this job. The User Profile Service synchronization job synchronizes the User Profile Service information in the Governance Automation database. Configure the interval to perform the job by entering your desired value and selecting Minute(s), Hour(s), Day(s), Week(s), Month(s), or Year(s).

7. Temporary Permission Scan Job – Select Enable temporary permission scan job to enable this job. The temporary permission scan job checks the period that the permissions have been granted. Configure the interval to perform the job by entering your desired value and selecting Minute(s), Hour(s), Day(s), Week(s), Month(s), or Year(s).

8. Content Database Information Synchronization Job – Select Enable content database information synchronization job to enable this job. The content database information synchronization job synchronizes the information of content databases created by Governance Automation into Content Database Report.

9. External Workflow Integration Scan Job – Select Enable external workflow integration scan job to enable this job. The external workflow integration scan job checks the status of external workflow and synchronizes custom metadata.

10. Click Save to save the configurations and return to the Settings page, or click Cancel to return to the Settings page without saving any configurations.

194


Configuring Session Timeout Settings Use System Security Settings to configure the session timeout Settings.

Click System Security Settings in the Settings page to access System Security Settings.

In the Session Timeout section of the System Security Settings interface, enter a positive integer in the text box and select a unit from the drop-down list, Minutes or Hours.

Configuring Category Management Use Category Management to organize services, approval processes, policies, and questionnaires.

To access Category Management settings, in the Settings page, click Category Management.

Displaying and Searching Categories To change the number of categories displayed, use the Show rows drop-down menu in the upper right-hand corner.

To search the displayed categories, enter the keyword in the Search text box and click the search ( ) button.

Creating or Editing Categories To create a new category, click Create on the ribbon. To modify a previously configured category, select the desired category, and click Edit on the ribbon.

In the Create Category interface or Edit Category interface, configure the following settings:

1. Category Name – Enter the name of the category that you are about to create.

2. Category Name Mapping – This allows the category to be displayed as different names in Governance Automation with different display languages. Enter the category names for different languages in the corresponding text boxes. If you do not wish to configure the category name mapping manually, Governance Automation automatically uses the category name entered in step 1 for the category names of all languages. The text boxes will be filled in with the name entered in Category Name when the cursor is moved away from the category name.

3. Click Save to save the configurations and return to the Category Management interface, or click Cancel to return to the Category Management interface without saving any configurations.

Deleting Categories To delete a category, select a previously configured category, and then click Delete on the ribbon. A confirmation window will pop up and ask if you are sure you want to proceed with the deletion. Click OK

195


to delete the selected category, or click Cancel to return to the Category Management interface without deleting the selected category.

Synchronizing Authentication Configuration Changes to Governance Automation If you make authentication changes in DocAve and you wish to apply these authentication configurations to Governance Automation, you must manually synchronize the changed configurations to Governance Automation.

To perform the synchronization, click your account name in the top-right corner of the Governance Automation interface and then click Synchronize Authentication Method from DocAve.

A new tab appears with the Success message. The changed authentication configurations are synchronized to Governance Automation successfully.

196


Modifying Governance Automation Configuration Settings after Installation To view or edit the installation settings after a successful Governance Automation installation, navigate to Start > Governance Automation and click Governance Automation Configuration Tool on a server where Governance Automation is installed.

In Governance Automation Configuration Tool, the Configuration Database Settings, Audit Database Settings, Service Configuration, Authentication Configuration, and Advanced Configuration can be modified.

*Note: If you are changing the certificate in Advanced Configuration, you must manually copy two configuration files to Governance Automation directories after saving changes in the Governance Automation Configuration Tool. For more information, refer to Applying User-Defined Certificates.

Re-registering Governance Automation after Uninstalling DocAve If you uninstall DocAve and then reinstall DocAve after a Governance Automation installation, you must re-register Governance Automation to DocAve using the Governance Automation Configuration Tool. To re-register Governance Automation to DocAve, you must configure the following settings in the Governance Automation Tool:

• DocAve Control Service Address

• DocAve Manager Passphrase

• DocAve Administration Account Settings

Refer to Installing Governance Automation for detailed information on these settings. After re-registering Governance Automation to DocAve, an update must be manually installed in DocAve to use Governance Automation properly. This update (DocAve_Update_for_Governance_Automation_1.5.zip) resides in the Governance Automation installation package.

197


Monitoring and Reporting Monitoring and Reporting allows administrators to manage all requests and tasks created by and assigned to any user, review Governance Automation processes, and gauge the current state of sites and site collections created by Governance Automation.

To access Monitoring and Reporting, click Monitoring and Reporting in the Administrator landing page.

Monitoring All Requests All Requests centralize all of the submitted service requests created by any users, providing you with one interface to process all of the requests.

To access All Requests, in the Monitoring and Reporting page, click All Requests. Click Back to close the All Requests interface.

You may change the number of requests displayed per page, as well the order they are displayed in. To change the number of requests displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the requests, click in a column heading such as Service Request, Requester, Category, Service Type, Service, Last Modified Time, and Assign To then select Ascending or Descending.

You can customize how the requests are displayed in a number of different ways:

• Search – Allows you to filter service requests displayed by the keyword you designate. The Service Request column, the Service column and the Assign To column support to search for the desired service requests, and only the content in the column displayed in the current view can be searched.

• – You can manage which columns are displayed in the list so that only information you want to see is displayed. Click , then select the checkbox next to the column name to have that column shown in the list.


You can perform the following actions in All Requests:

• View Details ‒ Click a request name to see its configuration.

• Cancel Request ‒ Select a request which you wish to cancel and click Cancel Request on the ribbon.

• Delete ‒ Select a request which you wish to delete and click Delete on the ribbon.

198


Monitoring All Tasks All Tasks centralize all of the tasks assigned to any users, providing you with one interface to process all current tasks or review previous tasks.

To access All Tasks, click All Tasks in the Monitoring and Reporting page. To exit out of All Tasks, click Back.

You can change the number of tasks displayed per page, as well the order they are displayed in. To change the number of tasks displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the tasks, click in a column heading such as Title, Category, Service, Requester, Assigned to, and Last Modified Time then select Ascending or Descending then select Ascending or Descending.

You can customize how the tasks are displayed in a number of different ways:

• Search – Allows you to filter tasks displayed by the keyword you designate. The Requester column and the Assign To column support to search for the desired tasks, and only the content in the column displayed in the current view can be searched.



Create, Archive, Delete, Extend Site Collection, and Create Site Tasks You can perform the following actions on tasks from Create Site Collection, Create Site, Archive Entire Site Collection, Delete Entire Site Collection, and Extend Site Collection services:

• View Task – Click a task title to see detailed information. In the View Details page, you have the following options:

o Approve – Click Approve on the ribbon to finish this task.

o Reject – Click Reject on the ribbon to reject this task.

o Edit Request (This button is only visible to the approvers when Allow all approvers to edit this service request is selected in the corresponding service) – Click Edit Request on the ribbon to edit all of the settings of this request in the Edit Request interface.

o View Request History (This button is only visible to the approvers when Allow all approvers to edit this service request is selected in the corresponding service) – Click View Request History to view the versions of this request in the View Request History interface.

199


• Approve – Select a desired task, and click Approve on the ribbon to approve the task. Enter any comments you may have in the pop-up window. Click OK to finish this task, or click Cancel to return to the All Tasks interface without executing the task.

• Reject – Select a desired task, and click Reject on the ribbon to reject the task. Enter comments you may have in the pop-up window. Click OK to finish this task, or click Cancel to return to the All Tasks interface without executing the task.

Site Collection Lifecycle Management Tasks You can perform the following actions on tasks from Site Collection Lifecycle Management services:

• View Task – Click a task title to see detailed information in the View Details page.

• Continue Access – Select a task, and click Continue Access on the ribbon to execute the Extend Site Collection task. In the pop-up window, click OK to execute the task or Cancel to return to the All Tasks interface.

• Extend – Select a task and click Extend on the ribbon to extend the lease for the site collection in this task. In the pop-up window, configure the following options:

o Terms Agreement – Choose whether to agree to the terms and conditions by selecting the Yes or No radio button. If you choose No, a message will pop up to remind that you must agree to the terms and conditions to submit this request.

o Extend Site Collection Lease Period – Specify the amount of time to extend beyond the site collection lease period by entering a positive integer in the text box and selecting Day(s), Week(s), Month(s), or Year(s) from the drop-down menu. Then click OK to confirm the action or Cancel to return to the All Tasks interface.

• Archive – Select a task, and click Archive on the ribbon to execute the Archive Entire Site Collection task. In the pop-up window, click OK to execute the task, or click Cancel to return to the All Tasks interface.

• Delete – Select a task, and click Delete on the ribbon to execute the Delete Entire Site Collection task. In the pop-up window, click OK to execute the task, or click Cancel to return to the All Tasks interface.

• Change Policy – Select a task and click Change Policy on the ribbon to change the policy for the site collection in this task. In the pop-up window, click OK to confirm the action or Cancel to return to the All Tasks interface.

• Change Quota – Select a task, and click Change Quota on the ribbon to change the site collection’s quota template or quota size. In the pop-up window, select a new quota template or enter your desired quota size. Click OK to save your configuration, or click Cancel to return to the All Tasks interface without executing the task.

Site Lifecycle Management Tasks You can perform the following actions on the tasks from Site Lifecycle Management services:

200







• Approve – Select a task, and click Approve on the ribbon to approve the task. Enter some comments for this task for further reference in the pop-up window. Click OK to finish this task or Cancel to return to the All Tasks interface.

• Reject – Select a task, and click Reject on the ribbon to reject the task. Enter some comments for this task for further reference in the pop-up window. Click OK to finish this task, or click Cancel to return to the All Tasks interface.

User Permission and Manual Archive Tasks You can perform the following actions on the tasks from Clone or Transfer User Permissions, Grant Permissions, Remove Permissions, and Manual Archive services:






o Click Review the Report on the ribbon to review detailed report of this task, then select View on screen or Download report.

View on screen – Open the report directly to view details on screen.

Download report – Download the report and then modify the data that you wish to change. In the pop-up window, click Browse to select the modified file to upload.

201




Change Actions, Content Move, and Create Tasks You can perform the following actions on the tasks from Change Site Collection Contact or Administrator, Change Site Collection Settings, Change Site Contact, Change Site Metadata, Content Move, Create My Site, Create Library/List, Change Library/List Settings services.








Permission Recertification Tasks When permission recertification is enabled in a site collection policy and the site collection policy is applied to a Governance Automation managed site collection, a permission recertification task will be generated. This task contains the searched permissions of users and groups for this site collection. Approvers can then modify the permissions in Governance Automation and the permission changes will be updated to SharePoint.

You can perform the following actions on the permission recertification task:


202


o Filter Records – Select User Based or Object Based from the drop-down list in the top left-hand corner. By default, All Items is selected.

o Submit – Click Submit on the ribbon to submit the task and apply all of your configurations to SharePoint.

o Reset – Click Reset on the ribbon to select Reset My Changes or Reset All Changes.

Reset My Changes – Your changes on the task will be cleared.

Reset All Changes – All users’ changes on the task will be cleared.

o Export Report – Click Export Report on the ribbon to export the permission recertification report. In the Export Report window, choose to export the report to local machine or export the report to an export location. If you choose Export to an export location, select a previously configured export location from the drop-down list, select a report format (CSV or XLS), and then click Export to Datasheet to export the report.

o Delete User – Select a user and click the ellipsis ( ) button to select Delete User. A pop-up window appears which asks you to confirm your deletion. Click OK to delete the selected user.

o Edit User Permissions – Select a user and click the ellipsis ( ) button to select Edit User Permissions. In the Edit Permissions interface, modify the permission levels in the Permissions section. Then, click Save on the ribbon to save your changes and go back to the View Details page. The edited record is highlighted.

o Remove User Permissions – Select a user and click the ellipsis ( ) button to select Remove User Permissions. A pop-up window appears which asks you to confirm your operation. Click OK to remove the user’s permissions.

o Edit Group Permissions – Select a group and click the ellipsis ( ) button to select Edit Group Permissions. In the Edit Permissions interface, modify the permission levels in the Permissions section. Then, click Save to save your changes and go back to the View Details page. The edited record is highlighted.

o Remove Group Permissions – Select a group and click the ellipsis ( ) button to select Remove Group Permissions. A pop-up window appears which asks you to confirm your operation. Click OK to remove the group’s permissions and go back to the View Details page. The edited record is highlighted.

o Delete User – Click the display name of a group and you are brought to a new window. Select one or more group users and click Delete User on the ribbon. A pop-up window appears which asks you to confirm your deletion. Click OK to delete the selected users.

o Remove User From Group – Click the display name of a group and you are brought to a new window. Select one or more group users and click Remove User From Group on the ribbon. A pop-up window appears which asks you to confirm your operation. Click OK to remove the selected users from the group.

o Change Group – Click the display name of a group and you are brought to a new window. Select one or more group users and click Change Group on the ribbon.

203


In the Change Group interface, select the group that you wish to change to and select the method for changing group, Copy or Move. Copy will copy the users to the new group. Move will remove the users from the previous group and then add the users to the new group. Click Save to save your changes and go back to the View Details page. The edited record is highlighted.

• Submit – Select a task and click Submit on the ribbon to approve the task. Enter comments for this task for further reference in the pop-up window. Click OK to finish this task or click Cancel to return to the All Tasks interface.

Quota Threshold Tasks When site collection quota threshold is enabled in a site collection policy and the site collection policy is applied to a Governance Automation managed site collection. If the site collection’s storage reaches the percentage of the configured quota, a task will be assigned to the approver defined in the approval process. The approver can choose to change the site collection quota or ignore the quota threshold.

You can perform the following actions on the quota threshold tasks:


o Change Quota – Click Change Quota on the ribbon and a pop-up window appears. Select a new quota template from the drop-down list and click OK to save the changes.

o Ignore – Click Ignore on the ribbon to ignore the site collection quota threshold. In the pop-up window, set the time internal to remind the threshold if the size of the site collection still exceeds the quota threshold after the time interval. Enter a positive integer in the text box and select Day(s) or Week(s) from the drop-down list. Then, click OK to save your configurations.

• Change Quota – Select a task and click Change Quota on the ribbon and a pop-up window appears. Select a new quota template from the drop-down list and click OK to save the changes.

• Ignore – Select a task and click Ignore on the ribbon to ignore the site collection quota threshold. In the pop-up window, set the time internal to remind the threshold if the size of the site collection still exceeds the quota threshold after the time interval. Enter a positive integer in the text box and select Day(s) or Week(s) from the drop-down list. Then, click OK to save your configurations.

Content Database Policy Threshold Warning Task If a site collection quota change request is approved by the approver and the changed quota make the corresponding content database exceed the database size threshold that is configured in a content database policy, a warning task will be assigned to the database contact to remind this and provide recommended solutions. The task title is named in the format of Content database [content database name] is going to exceed its policy threshold of [maximum database size] GB.

You can perform the following actions on the content database policy threshold warning task:

204



o View recommended solutions – The recommended solutions are provided in Summary.

o OK – Click OK to finally approve the site collection quota change request.

o Reject – Click Reject to reject the site collection quota change request.

• OK – Select a task and click OK on the ribbon to finally approve the site collection quota change request. Enter some comments for this task for further reference in the pop-up window. Click OK to finish this task or click Cancel to return to the All Tasks interface.

• Reject – Select a task and click Reject on the ribbon to reject the site collection quota change request. Enter some comments for this task for further reference in the pop-up window. Click OK to finish this task, or click Cancel to return to the All Tasks interface.

Error Tasks You can perform the following actions on the error tasks assigned to administrators:

• View Task – Click a task title to see detailed information. In the View Details page, click Retry on the ribbon to re-run the failed section or click Skip to continue the workflow past the failed section.

• Retry – For a task which contains failed section, click before a task title to select it, and then click Retry on the ribbon to re-run the failed section.

• Skip – For a task which contains failed section, click before a task title to select it, and then click Skip on the ribbon to continue the workflow past the failed section.

Audit Reports Audit Reports provide detailed information on all Administrator, service request and approval process activities:

• User Activity Report ‒ Provides detailed information on all actions performed by Governance Automation users, including administrators and business users. User Activity Report allows you to inspect the behaviors done by users when errors occur for furnishing useful information, or check the legality of user behaviors.

• Service Request Report ‒ Provides detailed information for all of the submitted service requests. Service Request Report gives you overall usage information of service requests, which you can gather for IT chargeback and budgeting.

• Approval Process Report ‒ Provides all of the processing tracks of the approval processes for the service request once they are approved. Approval Process Report allows you to view the detailed information of service requests for reviewing the performances, which can help you optimize your service request flow and make the processes more efficient.

205


User Activity Report To access User Activity Report, in the Monitoring and Reporting page, click User Activity Report. Click Back to close the User Activity Report interface.

Managing User Activity Reports To change the number of reports displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the reports, click in a column heading such as Object, Object Type, and Action then select Ascending or Descending.

You can customize how the reports are displayed in a number of different ways:

• Search – Allows you to filter reports displayed by the keyword you designate. The User and Object Instance Name column support to search for the desired reports, and only the content in the column displayed in the current view can be searched.


• – This allows you to filter which item in the list is displayed. Click the in the column heading you want to filter, then select the checkbox next to the item name to have that item shown in the list.

Filtering User Activity Reports To filter User Activity Reports, complete the following steps:

1. Click Set Filter on the ribbon to customize the report. You can set filters for Object, Type, Action, Time Range and User.

2. To set new filter rules, click Reset and the previous filter rules are cleared to the default ones.

3. Click Generate Report to retrieve data for your report, or click Export to Datasheet to export the report to storage.

a. In the pop-up window, choose to export the report to a local path or an export location to store the report.

b. If you choose Export to an export location, select an export location from the drop-down menu, or click Add New Location to redirect to the Report Export Location interface to create a new one.

c. Select either CSV or XLS as the report format from the drop-down menu in the Report Format section.

d. Click Export to Datasheet to generate the report, or close the pop-up window to return to the previous interface.

206


Exporting User Activity Reports To export the currently displayed reports, click Export Report on the ribbon and then select a Report Export Location and Report Format.

Service Request Report To access Service Request Report, in the Monitoring and Reporting page, click Service Request Report. Click Back to close the Service Request Report interface.

Managing Service Request Reports To change the number of reports displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the reports, click in a column heading such as Service Type, Category, Department, Status, and Assign To then select Ascending or Descending.


• Search – Allows you to filter reports displayed by the keyword you designate. The Service Name, Service Request Name, Requester, and Assign To column support to search for the desired reports, and only the content in the column displayed in the current view can be searched.



Filtering Service Request Reports To filter Service Request Reports, complete the following steps:

1. Click Set Filter on the ribbon to customize the report. You can set filters for Service Type, Service Name, Requester, Assign To, Time Range and Department.






207



Exporting Service Request Reports To export the currently displayed reports, click Export Report on the ribbon and then select a Report Export Location and Report Format.

Approval Process Report To access Approval Process Report, in the Monitoring and Reporting page, click Approval Process Report. Click Back to close the Approval Process Report interface.

Managing Approval Process Reports You can change the number of reports displayed per page, as well the order they are displayed in. To change the number of reports displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the reports, click in a column heading such as Service Type, Status, and Department then select Ascending or Descending.


• Search – Allows you to filter reports displayed by the keyword you designate. The Service Request Name and User column support to search for the desired reports, and only the content in the column displayed in the current view can be searched.



Filtering Approval Process Reports To filter Approval Process Reports, complete the following steps:

1. Click Set Filter on the ribbon to customize the report. You can set filters for Service Type, Service Request Name, Status, Time Range, Department, and User.





208




Exporting Approval Process Reports To export the currently displayed reports, click Export Report on the ribbon and then select a Report Export Location and Report Format.

Administration Reports Administration Reports provide basic information on all Site Collections and Sites created by Governance Automation:

• Site Collection Report ‒ Provides a list of site collections created by Governance Automation and the corresponding information, including site collection URL, department, title, policy, site collection template, primary site collection administrator, secondary site collection administrator, primary site collection contact, secondary site collection contact, and so on. You can customize how the report displays the data by considerable criteria.

• Site Report ‒ Provides a list of sites created by Governance Automation and the corresponding information, including site URL, department, title, site template, primary site contact, and secondary site contact. You can customize how the report displays the data by considerable criteria.

• Content Database Report ‒ Provides a list of content databases created by Governance Automation and the corresponding information, including content database policy name, database contact, current quota of a database, current size of a database, maximum size of a database, current number of site collections, and maximum number of site collections. You can customize how the report displays the data by considerable criteria.

Site Collection Report To access Site Collection Report, in the Monitoring and Reporting page, click Site Collection Report. Click Back to close the Site Collection Report interface.

Managing Site Collection Reports To change the number of reports displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the reports, click in a column heading such as Department, Policy, Site Collection Template, Publish to Directory, Quota Size (GB), Site Collection Size (GB), Tiered Storage Used for Storage Manager (GB), Status, and Site Maximum Depth then select Ascending or Descending.


209


• Search – Allows you to filter reports displayed by the keyword you designate. The URL, Title, Description, Primary Site Collection Administrator, Secondary Site Collection Administrator, Primary Site Contact, Secondary Site Collection Contact, and metadata column support to search for the desired reports, and only the content in the column displayed in the current view can be searched.

• – You can manage which columns are displayed in the list so that only information you want to see is displayed. By default, URL, Department, Title, Policy, Site Collection Template, Primary Site Collection Administrator, Primary Site Collection Contact, Secondary Site Collection Contact, Publish to Directory, Content Database Name, Quota Template, Quota Size (GB), Site Collection Size (GB), Tiered Storage Used for Storage Manager (GB), Inactivity Threshold Date, Lease Period Expiration Date, Status, Site Maximum Depth, and Deployment Manager Plan are displayed. Click , then select the checkbox next to the column name to have that column shown in the list.


Filtering Site Collection Reports To filter Site Collection Reports, complete the following steps:

1. Click Set Filter on the ribbon to customize the report. You can set filters for URL, Site Template, Site Collection Size, Status, Department, Policy, and Primary Site Collection Contact. Filter by Expiration Date is also supported. Set Inactivity Threshold Date and Lease Period Expiration Date to add more filter rules.







Exporting Site Collection Reports To export the currently displayed reports, click Export Report on the ribbon and then select your desired Report Export Location and Report Format.

210


Site Report To access Site Report, in the Monitoring and Reporting page, click Site Report. Click Back to close the Site Report interface.

Managing Site Reports To change the number of reports displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the reports, click in a column heading such as Department, Site Template, Primary Site Contact, and Secondary Site Contact, then select Ascending or Descending.


• Search – Allows you to filter reports displayed by the keyword you designate. The URL and Title column support to search for the desired reports, and only the content in the column displayed in the current view can be searched.



Filtering Site Reports To filter Site Reports, complete the following steps:

1. Click Set Filter on the ribbon to customize the report. You can set filters for URL, Site Template, Department, and Primary Site Contact.







211


Exporting Site Reports To export the currently displayed reports, click Export Report on the ribbon.

Content Database Report To access Content Database Report, in the Monitoring and Reporting page, click Content Database Report. Click Back to close the Content Database Report interface.

Managing Content Database Reports To change the number of reports displayed per page, select the desired number from the Show rows drop-down menu in the upper-right corner. To sort the reports, click the sort ( ) button in a column heading such as Name, Current Quota (GB), Current Size (GB), Maximum Size (GB), Current Number of Site Collections, and Maximum Number of Site Collections, then select Ascending or Descending.


• Search – Allows you to filter reports displayed by the keyword you designate. The Name and Policy Name column support to search for the desired reports, and only the content in the column displayed in the current view can be searched.

• Manage columns ( ) – You can manage which columns are displayed in the list so that only information you want to see is displayed. Click the manage columns ( ) button, then select the checkbox next to the column name to have that column shown in the list.

• Filter items ( ) – This allows you to filter which item in the list is displayed. Click the filter items ( ) button in the column heading you want to filter, then select the checkbox next to the item name to have that item shown in the list.

Filtering Content Database Reports To filter Content Database Reports, complete the following steps:

1. Click Set Filter on the ribbon to customize the report. You can set filters for Name, Policy Name, and Database Contact.






212



Exporting Content Database Reports To export the currently displayed reports, click Export Report on the ribbon.

Public Site Collection Directory The Public Site Collection Directory allows administrators and business users to monitor business ownership and usage. Note that site collections with the Publish to Directory metadata are considered as published site collections. For more information about the Publish to Directory metadata, see Configuring Metadata.

To access the Public Site Collection Directory, click Public Site Collection Directory in the Administrator landing page.

Managing Public Site Collection Directory Reports To change the number of the directory reports displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the directory reports, click in a column heading such as Department, Policy, Site Collection Template, Site Collection Size (GB), Status, and Site Maximum Depth, then select Ascending or Descending.

You can customize how the directory reports are displayed in a number of different ways:

• Search – Allows you to filter the directory reports displayed by the keyword you designate. The URL, Title, Description, Primary Site Collection Administrator, Secondary Site Collection Administrator, Primary Site Collection Contact, Secondary Site Collection Contact, and metadata column support to search for the desired reports, and only the content in the column displayed in the current view can be searched.

• – You can manage which columns are displayed in the list so that only information you want to see is displayed. By default, URL, Department, Title, Policy, Site Collection Template, Primary Site Collection Administrator, Primary Site Collection Contact, Secondary Site Collection Contact, Publish to Directory, Content Database Name, Quota Template, Quota Size (GB), Site Collection Size (GB), Inactivity Threshold Date, Lease Period Expiration Date, Status, Site Maximum Depth, and Deployment Manager Plan are displayed. Click , then select the checkbox next to the column name to have that column shown in the list.


Filtering Public Site Collection Directory Reports To filter Public Site Collection Directory Reports, complete the following steps:

213


1. Click Set Filter on the ribbon to customize the directory report. You can set filters for URL, Site Template, Site Collection Size, Status, Department, Policy, and Primary Site Collection Contact. Filter by Expiration Date is also supported. Set Inactivity Threshold Date and Lease Period Expiration Date to add more filter rules.







Exporting Public Site Collection Directory Reports To export the currently displayed directory reports, click Export Report on the ribbon and then select your desired Report Export Location and Report Format.

My Sites My Sites displays a list of site collections and sites in which the login user is the primary contact or secondary contact.

To access My Sites, click My Sites in the Administrator landing page.

Managing My Sites Reports To change the number of reports displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the reports, click in a column heading such as Title, Department, Type, and Policy, then select Ascending or Descending.


• Search – Allow you to filter reports displayed by the keyword you designate. The Title and URL column support to search for the desired reports, and only the content in the column displayed in the current view can be searched.

• – You can manage which columns are displayed in the list so that only information you want to see is displayed. By default, URL, Type, Department, Title, Policy, Primary Contact, Secondary Contact, Primary Site Collection Administrator, and Secondary Site Collection

214


Administrator are displayed. Click , then select the checkbox next to the column name to have that column shown in the list.

Filtering My Sites Reports To filter My Sites Reports, complete the following steps:

1. Click Set Filter on the ribbon to customize the report. You can set filters for URL, Department, Policy, and Primary Contact.


3. Click Generate Report to retrieve data for your report, or click Export to Datasheet to export the report to store the report.


b. If you choose Export to an export location, select and export location from the drop-down menu, or click Add New Location to redirect to the Report Export Location interface to create a new one.



Exporting My Sites Reports To export the currently displayed reports, click Export Report on the ribbon, then select your desired Report Export Location and Report Format.

215


Working with Requests and Tasks Governance Automation administrators can create services which contain a set of configured settings for SharePoint operations that comply with your organization’s rules and standards. These services are tailored to the needs of different departments and purposes within your organization. You (IT Admins) will be able to submit requests for these services according to your SharePoint needs. Once you submit a service request, the approval process associated with each corresponding service will automatically notify the designated persons in your organization of your request. After all approvers of a service have approved the request, Governance Automation will perform the necessary operations to complete the service you have requested.

If you are a designated approver for any service, a task will appear in your My Tasks list whenever a request for the service is submitted and any/all previous approvers have approved the request.

Starting a Request A request is a form for a management operation in SharePoint and requires approval depending on the service that is requested.

To start a request for a service, click Start a Request on the landing page of the Governance Automation interface. You will be brought to the Start a Request interface, where all of the available services and questionnaires (if configured and activated) are displayed in your catalog.

In the Start a Request interface:

1. Select a service by clicking the service name.

If you select a questionnaire, answer the questions and click Submit to submit your questionnaire. The available services will display according to your answers.

2. Enter the necessary information in the configuring service request interface.

3. Choose one of the following options:

• Click Save As Draft to save the request as a draft and leave the configured settings for later use.

• Click Save and Submit to submit this request to the approvers.

• Click Cancel to return to the Start a Request interface without saving any configurations.

To search service requests or questionnaires, enter the service name keyword or questionnaire name keyword in the provided text box in the upper-right corner. You can also filter service requests or questionnaires according to the language by clicking the language filter icon on the ribbon. Then, select the checkboxes next to the language names to have the services or questionnaires of these languages shown.

216


Viewing My Requests In My Requests, all of the Governance Automation requests created by you previously are displayed. They include Submitted Requests, and Saved Requests.

To manage the requests, click View My Requests in the Administrator landing page. When accessing My Requests from the landing page and it is not in your current view, click the ARROW icon to switch the view to find your target.

Select the Submitted Requests or Saved Requests tab in the My Requests page to access the corresponding request type.

Submitted Requests In Submitted Requests, all of the requests submitted by you are displayed here. You may change the number of submitted requests displayed per page, as well the order they are displayed in. To change the number of submitted requests displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the submitted requests, click in a column heading such as Service Request, Category, Service, Last Modified Time, and Assign to then select Ascending or Descending.

You can customize how the submitted requests are displayed in a number of different ways:

• Search – Allows you to filter service requests displayed by the keyword you designate. The Service Request column, the Service column and the Assign To column support to search for the desired service requests, and only the content in the column displayed in the current view can be searched.


• – This allows you to filter which item in the list is displayed. Click the of the column you want to filter, and then select the checkbox next to the item name to have that item shown in the list.

You can perform the following actions in Submitted Requests:

• View Details – Click a request title to see detailed information. Close the interface to return to the All Request interface.

• Copy – Duplicate the existing service request to make minor changes in order to submit as a new service request. Select a submitted request by checking in front of the service request name. Click Copy on the ribbon, and make the desired modifications.

When you have finished making changes, choose one of the following options:

o Click Save to save as a new service request.

o Click Save and Submit to submit this request to the approvers.

217


o Click Cancel to return to the Start a Request interface without saving any configurations.

• Cancel Request – Select a submitted request which you wish to cancel and click Cancel Request on the ribbon.

Saved Requests In Saved Requests, all of the requests saved by you without submitting are displayed here. You may change the number of saved requests displayed per page, as well the order they are displayed in. To change the number of saved requests displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the saved requests, click in a column heading such as Service Request, Category, Service, and Last Modified Time then select Ascending or Descending.

You can customize how the saved requests are displayed in a number of different ways:

• Search – Allows you to filter service requests displayed by the keyword you designate. The Service Request column, and the Service column support to search for the desired service requests, and only the content in the column displayed in the current view can be searched.



You can perform the following actions in saved requests:

• View Details – Click a request title to see detailed information.

• Edit – Select a saved request by clicking before a service request name, and click Edit on the ribbon to edit the settings of this request. When completing the configurations, click Save to save all of the settings, or click Save and Submit to submit this request to the approvers, or click Cancel to return to the Start a Request interface without saving any configurations.

• Delete – Select a saved request by clicking before a service request name, and click Delete on the ribbon. A confirmation window will pop up for this deletion. Click OK to delete the selected request, or click Cancel to return to the My Request interface without deleting the selected request.

• Copy – Duplicate the existing service request to make minor changes in order to save as a new service request. Select a submitted request by clicking before a service request name. Click Copy on the ribbon, and make the desired modifications.

When you have finished making changes,

o Click Save to save all of the settings.

o Click Save and Submit to submit this request to the approvers.

218


o Click Cancel to return to the Start a Request interface without saving any configurations.

Viewing My Tasks When a service request is submitted and you are one of the approvers of this request, a task will be assigned to you.

To view and manage your tasks, click View My Tasks in the Administrator landing page.

In My Tasks, all of the tasks assigned to you are displayed here. You may change the number of tasks displayed per page, as well the order they are displayed in. To change the number of tasks displayed per page, select the desired number from the Show rows drop-down menu in the upper right-hand corner. To sort the tasks, click in a column heading such as Title, Requester, Service, Category, Service Type, and Last Modified Time then select Ascending or Descending.

You can customize how the tasks are displayed in a number of different ways:

• Search – Allows you to filter tasks displayed by the keyword you designate. The Title column and Requester column support to search for the desired tasks, and only the content in the column displayed in the current view can be searched.



Create, Archive, Delete, Extend Site Collection, and Create Site Tasks You can perform the following actions on tasks from Create Site Collection, Create Site, Archive Entire Site Collection, Delete Entire Site Collection, and Extend Site Collection services:






219


• Approve – Select a task, and click Approve on the ribbon to approve the task. Enter any comments you may have in the pop-up window. Click OK to finish this task, or click Cancel to return to the My Tasks interface without executing the task.

• Reject – Select a task, and click Reject on the ribbon to reject the task. Enter comments you may have in the pop-up window. Click OK to finish this task, or click Cancel to return to the My Tasks interface without executing the task.

Site Collection Lifecycle Management Tasks You can perform the following actions on tasks from Site Collection Lifecycle Management services:

• View Task – Click a task title to see detailed information in the View Details page.

• Continue Access – Select a task, and click Continue Access on the ribbon if the corresponding site collection is still in use and you would like to continue allowing users access to that site collection. In the pop-up window, click OK to confirm this action, or click Cancel to return to the My Tasks interface without executing the task.

• Extend – Select a task, and click Extend on the ribbon to extend the lease for the site collection in this task. In the pop-up window, configure the following options:

o Terms Agreement – Choose whether to agree to the terms and conditions by selecting the Yes or No radio button. If you choose No, a message will pop up to remind that you must agree to the terms and conditions to submit this request.

o Extend Site Collection Lease Period – Specify the amount of time to extend beyond the site collection lease period by entering a positive integer in the text box and selecting Day(s), Week(s), Month(s), or Year(s) from the drop-down menu. Then click OK to confirm this action, or click Cancel to return to the My Tasks interface without executing the task.

• Archive – Select a task, and click Archive on the ribbon to archive the site collection. In the pop-up window, click OK to confirm this action, or click Cancel to return to the My Tasks interface without executing the task.

• Delete – Select a task, and click Delete on the ribbon to delete the site collection. In the pop-up window, click OK to confirm this action, or click Cancel to return to the My Tasks interface without executing the task.

• Change Policy – Select a task, and click Change Policy on the ribbon to change the policy associated with the site collection. In the pop-up window, click OK to confirm this action, or click Cancel to return to the My Tasks interface without executing the task.

• Change Quota – Select a task, and click Change Quota on the ribbon to change the site collection’s quota template or quota size. In the pop-up window, select a new quota template or enter your desired quota size. Click OK to save your configuration, or click Cancel to return to the My Tasks interface without executing the task.

Site Lifecycle Management Tasks You can perform the following actions on the tasks from Site Lifecycle Management services:

220









User Permission and Manual Archive Tasks You can perform the following actions on the tasks from Clone or Transfer User Permissions, Grant Permissions, Remove Permissions, and Manual Archive services:

• View Task – Click a task name to see the detailed information of this task. In the View Details page, you have the following options:





o Click Review the Report on the ribbon to review detailed report of this task, then select View on screen or Download report.

View on screen – Open the report directly to view details on screen.

Download report – Download the report and then modify the data that you wish to change. In the pop-up window, click Browse to select the modified file to upload.

221




Change Actions, Content Move, and Create Tasks You can perform the following actions on the tasks from Change Site Collection Contact or Administrator, Change Site Collection Settings, Change Site Contact, Change Site Metadata, Content Move, Create My Site, Create Library/List, Change Library/List Settings services.



o Reject –Click Reject on the ribbon to reject this task.



• Approve – Select a task, and click Approve on the ribbon to approve the task. Enter some comments for this task for further reference in the pop-up window. Click OK to finish this task or Cancel to return to the My Tasks interface without executing the task.

• Reject – Select a task, and click Reject on the ribbon to reject the task. Enter some comments for this task for further reference in the pop-up window. Click OK to finish this task, or click Cancel to return to the My Tasks interface without executing the task.

Permission Recertification Tasks When permission recertification is enabled in a site collection policy and the site collection policy is applied to a Governance Automation managed site collection, a permission recertification task will be generated. This task contains the searched permissions of users and groups for this site collection. Approvers can then modify the permissions in Governance Automation and the permission changes will be updated to SharePoint.

You can perform the following actions on the permission recertification task:


222


o Filter Records – Select User Based or Object Based from the drop-down list in the top left-hand corner. By default, All Items is selected.

o Submit – Click Submit on the ribbon to submit the changes and apply all of your configurations to SharePoint.

o Reset – Click Reset on the ribbon to select Reset My Changes or Reset All Changes.

Reset My Changes – Your changes on the task will be cleared.

Reset All Changes – All users’ changes on the task will be cleared.

o Export Report – Click Export Report on the ribbon to export the permission recertification report. In the Export Report window, choose to export the report to local machine or export the report to an export location. If you choose Export to an export location, select a previously configured export location from the drop-down list, select a report format (CSV or XLS), and then click Export to Datasheet to export the report.

o Delete User – Select a user and click the ellipsis ( ) button to select Delete User. A pop-up window appears which asks you to confirm your deletion. Click OK to delete the selected user.

o Edit User Permissions – Select a user and click the ellipsis ( ) button to select Edit User Permissions on the ribbon. In the Edit Permissions interface, modify the permission levels in the Permissions section. Then, click Save on the ribbon to save your changes and go back to the View Details page. The edited record is highlighted.

o Remove User Permissions – Select a user and click the ellipsis ( ) button to select Remove User Permissions. A pop-up window appears which asks you to confirm your operation. Click OK to remove the user’s permissions.

o Edit Group Permissions – Select a group and click the ellipsis ( ) button to select Edit Group Permissions on the ribbon. In the Edit Permissions interface, modify the permission levels in the Permissions section. Then, click Save to save your changes and go back to the View Details page. The edited record is highlighted.

o Remove Group Permissions – Select a group and click the ellipsis ( ) button to select Remove Group Permissions. A pop-up window appears which asks you to confirm your operation. Click OK to remove the group’s permissions and go back to the View Details page. The edited record is highlighted.

o Delete User – Click the display name of a group and you are brought to a new window. Select one or more group users and click Delete User on the ribbon. A pop-up window appears which asks you to confirm your deletion. Click OK to delete the selected users.

o Remove User From Group – Click the display name of a group and you are brought to a new window. Select one or more group users and click Remove User From Group on the ribbon. A pop-up window appears which asks you to confirm your operation. Click OK to remove the selected users from the group.

o Change Group – Click the display name of a group and you are brought to a new window. Select one or more group users and click Change Group on the ribbon.

223


In the Change Group interface, select the group that you wish to change to and select the method for changing group, Copy or Move. Copy will copy the users to the new group. Move will remove the users from the previous group and then add the users to the new group. Click Save to save your changes and go back to the View Details page. The edited record is highlighted.

• Submit – Select a task and click Submit on the ribbon to submit changes of the task. Enter comments for this task for further reference in the pop-up window. Click OK to finish this task or click Cancel to return to the All Tasks interface.

Quota Threshold Tasks When site collection quota threshold is enabled in a site collection policy and the site collection policy is applied to a Governance Automation managed site collection. If the site collection’s storage reaches the percentage of the configured quota, a task will be assigned to the approver defined in the approval process. The approver can choose to change the site collection quota or ignore the quota threshold.

You can perform the following actions on the quota threshold tasks:


o Change Quota – Click Change Quota on the ribbon and a pop-up window appears. Select a new quota template from the drop-down list and click OK to save the changes.

o Ignore – Click Ignore on the ribbon to ignore the site collection quota threshold. In the pop-up window, set the time internal to remind the threshold if the size of the site collection still exceeds the quota threshold after the time interval. Enter a positive integer in the text box and select Day(s) or Week(s) from the drop-down list. Then, click OK to save your configurations.

• Change Quota – Select a task and click Change Quota on the ribbon and a pop-up window appears. Select a new quota template from the drop-down list and click OK to save the changes.

• Ignore – Select a task and click Ignore on the ribbon to ignore the site collection quota threshold. In the pop-up window, set the time internal to remind the threshold if the size of the site collection still exceeds the quota threshold after the time interval. Enter a positive integer in the text box and select Day(s) or Week(s) from the drop-down list. Then, click OK to save your configurations.

Content Database Policy Threshold Warning Task If a site collection quota change request is approved and the new quota exceeds the database size threshold that is configured in a content database policy, a warning task with recommendations will be assigned to the database contact. The task title is named in the following format: Content database [content database name] is going to exceed its policy threshold of [maximum database size] GB.

You can perform the following actions on the content database policy threshold warning task:

224



o View recommended solutions – The recommended solutions are provided in Summary.

o OK – Click OK to finally approve the site collection quota change request.

o Reject – Click Reject to reject the site collection quota change request.

• OK – Select a task and click OK on the ribbon to finally approve the site collection quota change request. Enter some comments for this task for further reference in the pop-up window. Click OK to finish this task or click Cancel to return to the All Tasks interface.

• Reject – Select a task and click Reject on the ribbon to reject the site collection quota change request. Enter some comments for this task for further reference in the pop-up window. Click OK to finish this task, or click Cancel to return to the My Tasks interface.

Error Tasks You can perform the following actions on the error tasks assigned to you:

• View Task – Click a task title to see detailed information. In the View Details page, click Complete on the ribbon to finish this task, or click Close on the ribbon to exit this page.

• Retry – For a task which contains failed section, click before a task title to select it, and then click Retry on the ribbon to re-run the failed section.

• Skip – For a task which contains failed section, click before a task title to select it, and then click Skip on the ribbon to continue the workflow past the failed step.

225


Changing Branding Elements in Governance Automation Governance Automation provides a flexible and simple way for you to modify user interface elements so that you can align its look and feel with your corporate branding. Note that to change colors, you will modify CSS color codes in CSS files.

Figure 22 shows the default user interface of the homepage in Governance Automation with the mouse hovering over the Approval Process tile.

Figure 22: The default user interface of the Home page in Governance Automation.

226


Figure 23 shows the re-branded Governance Automation user interface for the fictional customer Contoso.

Figure 23: Re-branded Governance Automation user interface for Contoso.

The branding elements can be changed through modifying CSS files and configuration files.

• Changing the Title Style

• Changing the Logo and Logo URL

• Changing the Theme Color

• Changing the Navigation Bar Color

• Changing the Table Style

• Changing the System Name Image on Login Page

• Changing the System Logo Image on Login Page

• Changing the About Background Image

• Changing the Governance Automation App Logo

• Changing the Site Information Card Logo

• Supporting Custom CSS Files

227


Changing the Title Style The default title:

Figure 24: The default title of Governance Automation.

The changed title:

Figure 25: The changed title of Governance Automation.

Refer to the instructions below to change the title of your Governance Automation.

1. On the server where Governance Automation is installed, navigate to …\AvePoint\GovernanceAutomation\Resources.

2. Find the core.en-us.resx file and open it with Notepad.

Figure 26: The core.en-us.resx file.

228


3. Find the attribute data name="Landing_ProductName" and modify the value DocAve Governance Automation to your desired product name. In the example below, we used Contoso SharePoint Portal.

Figure 27: Modifying the title.

4. Save and close the core.en-us.resx file.

5. You can also change the font of the title. To modify the title font, follow the steps below.

a. On the server where Governance Automation is installed, navigate to …\AvePoint\GovernanceAutomation\Content\Themes\Base\Style.

b. Find the GALayoutStyle.css file and open it with Notepad.

Figure 28: The GALayoutStyle.css file.

229


c. Find the attribute ga-title and modify the values of font-size and color to your desired ones.

• The value of font-size determines the font size of the title.

• The value of color determines the font color of the title

Figure 29: Modifying the title font.

d. Save and close the GALayoutStyle.css file.

*Note: If the title does not change after saving the files and refreshing the browser page, go to the Internet Information Services (IIS) Manager. Navigate to Application Pools, select Governance Automation and right-click to select Recycle…. The Governance Automation application pool restarts. Then, refresh the browser page to view the changed title.

Changing the Logo and Logo URL The default logo:

Figure 30: The default logo of AvePoint.

The changed logo:

Figure 31: The changed logo of Contoso.

230


Refer to the following instructions to change the logo of your Governance Automation.

1. Create your own logo image. Make sure the height of your image is 20 pixels and the width of your logo is 20 pixels, and the file name of the image is exactly Organization_Logo_Image_20x20.

2. Copy the image to the server where Governance Automation is installed.

3. Navigate to …\AvePoint\GovernanceAutomation\Content\Themes\Custom\Images and place the copied image to the Images folder.

4. To change the logo URL, complete the steps below:

a. On the server where Governance Automation is installed, navigate to …\AvePoint\GovernanceAutomation\Views\Shared.

b. Find the GALayoutPageTitle.cshtml file and open it with Notepad.

Figure 32: The GALayoutPageTitle.cshtml file.

c. Find the following node and modify www.avepoint.com to your desired URL.

titleBar.avepoint.click(function () {

window.open('http://www.avepoint.com');

}).keydown(function () {

e = arguments[0];

if (e.keyCode == 13) {

window.open('http://www.avepoint.com');

231


Figure 33: Modifying the URL.

d. Save and close the GALayoutPageTitle.cshtml file.

Changing the Theme Color The default title bar and the component tiles:

Figure 34: The default title bar and the component tiles.

232


The changed title bar and the component tiles:

Figure 35: The changed title bar and the component tiles.

Refer to the following instructions to change the theme color of your Governance Automation:

1. On the server where Governance Automation is installed, navigate to …\AvePoint\GovernanceAutomation\Content\Themes\Base\Style.

2. Find the GALayoutStyle.css file and open it with Notepad.

Figure 36: The GALayoutStyle.css file.

233


3. Find the attribute title-bar and modify the value of background-color to your desired one.

Figure 37: Modifying the GALayoutStyle.css file.

4. On the server where Governance Automation is installed, navigate to …\AvePoint\GovernanceAutomation\Content\Themes\Base\Style\GAUI.

5. Find the GATitleView.css file and open it with Notepad.

Figure 38: The GATitleView.css file.

234


6. Find the attribute gatitleview-boxcaptionbig and modify the values of background and color to your desired ones.

a. The value of background determines the color that is displayed when the mouse hovers over a big tile (for example, the Approval Process tile in the Home Page).

b. The value of color determines the color of the characters displayed on the tile description.

Figure 39: Modifying the attribute gatitleview-boxcaptionbig.

7. Find the attribute gatitleview-boxcaptionsmall-background and modify the value of background to your desired one, which determines the color that is displayed when the mouse hovers over a small tile (for example, the Create Site Collection tile in Service Management > Create New).

Figure 40: The attribute gatitleview-boxcaptionsmall-background.

235


27. Find the attribute gatitleview-boxcaptionsmall and modify the value of color to your desired one, which determines the color of the characters displayed on the small tile description.

Figure 41: Modifying the attribute gatitleview-boxcaptionsmall.

8. Save and close the GATitleView.css file.

Changing the Navigation Bar Color The default navigation bar:

Figure 42: The default navigation bar.

The changed navigation bar:

236


Figure 43: The changed navigation bar.

Refer to the following instructions to change the navigation bar color of your Governance Automation.

1. To modify the background color of a selected tile on the navigation bar, navigate to …\AvePoint\GovernanceAutomation\Content\Themes\Base\Style\GAUI on the server where Governance Automation is installed,

2. Find the GAUICommon.css file and open it with Notepad.

Figure 44: The GAUICommon.css file.

3. Find the attribute gabtn-outerdivselmenu.

• If you use Internet Explorer 9, Google Chrome, or Firefox to access Governance Automation, modify the value of background-color: rgba(128, 8, 8, 0.70) to your desired one.

237


Figure 45: Modifying the GAUICommon.css file.

• If you use Internet Explorer 8 or Internet Explorer 10 to access Governance Automation, modify =#680707 and #680707 within -ms-filter: 'progid:DXImageTransform.Microsoft.Gradient(enabled=true, startColorStr=#680707 , endColorStr=#680707 ) to your desired ones. If the values of the start color and the end color are different, the color is displayed as gradient.


4. Save and close the GAUICommon.css file.

5. To modify the background color of the navigation bar, navigate to …\AvePoint\GovernanceAutomation\Content\Themes\Base\Style.

6. Find the GALayoutStyle.css file and open it with Notepad.

7. Find the menu-bar attribute and modify the value of background-color to your desired one.

Figure 47: Modifying the GALayoutStyle.css file.

8. Save and close the GALayoutStyle.css file.

238


Changing the Table Style The default table:

Figure 48: The default table.

The changed table:

Figure 49: The changed table.

Refer to the following instructions to change the table style of your Governance Automation.

1. On the server where Governance Automation is installed, navigate to …\AvePoint\GovernanceAutomation\Content\Themes\Base\Style\GAUI.

2. Find the GAUICommon.css file and open it with Notepad.

239



3. Find the attribute gagrid-data-head-background and modify the value of background-color to your desired one.


4. Save and close the GAUICommon.css file.

5. To change the background color of the manage columns ( ) button, complete the following steps:

a. On the server where Governance Automation is installed, navigate to …\AvePoint\GovernanceAutomation\Content\Themes\Base\Style\GAUI.

b. Find the GAUICommon.css file and open it with Notepad.

240



c. Find the attribute gagrid-colmgr-container-background and modify the value of background-color to your desired one.


d. Save and close the GAUICommon.css file.

*Note: To change the table style of an individual page, go to …\AvePoint\GovernanceAutomation\Content\Themes\Base\Style\[Folder name with Page category]. In the CSS files within [Folder name with Page category], modify the value of background-color to your desired one.

Changing the System Name Image on Login Page The default system name image on the login page of Governance Automation:

241


Figure 54: The default system name image.

The changed system name image on the login page of Governance Automation:

Figure 55: The changed system name image.

Refer to the following instructions to change the system name image on the login page of Governance Automation:

1. Create your own system name image. Make sure the height of your image is 490 pixels and the width of your image is 65 pixels, and the file name of the image is exactly System_Name_Image_490x65.


242



Figure 56: Placing the copied image to the Images folder.

4. Refresh the login page and the changed system name image will be displayed.

Changing the System Logo Image on Login Page The default system logo image on the login page of Governance Automation:

Figure 57: The default system logo image.

The changed system logo image on the login page of Governance Automation:

243


Figure 58: The changed system logo image.

Refer to the following instructions to change the system logo image on the login page of Governance Automation:

1. Create your own system logo image. Make sure the height of your image is 280 pixels and the width of your image is 250 pixels, and the file name of the image is exactly System_Logo_Image_280x250.



244



4. Refresh the login page and the changed system logo image will be displayed.

Changing the About Background Image The default background image that appears after clicking About:

Figure 60: The default About background image.

The change background image that appears after clicking About:

245


Figure 61: The changed About background image.

Refer to the following instructions to change the background image of About:

1. Create your own About background image. Make sure the height of your image is 450 pixels and the width of your image is 294 pixels, and the file name of the image is exactly About_Background_Image_450x297.




4. Click About again and the changed background image will be displayed.

246


Changing the Governance Automation App Logo Refer to the following instructions to change the logo of your Governance Automation App:

1. Create your own app logo image. Make sure the height of your image is 20 pixels and the width of your image is 20 pixels, and the file name of the image is exactly AppLogo_20x20.



Changing the Site Information Card Logo Refer to the following instructions to change the logo of your Site Information Card app part:

1. Create your own app part logo image. Make sure the height of your image is 200 pixels and the width of your image is 30 pixels, and the file name of the image is exactly InfoCardLogo_200x30.



Supporting Custom CSS Files Governance Automation supports using custom CSS files to change the look and feel of your Governance Automation user interface.

Build the custom CSS files and then place the CSS files to the directory …\AvePoint\GovernanceAutomation\Content\Themes\Custom\Style.

*Note: You can customize the CSS file names and place the CSS files in nested folders within the Style folder.

247


Governance Automation Web API SDK Build your customizable, extendable, and programmable usage of Governance Automation functions by invoking the program interfaces provided by Governance Automation Web API SDK.

To access detailed information on the commands available in the Governance Automation Web API SDK:

1. Go to the Governance Automation server.

2. Navigate to …\AvePoint\GovernanceAutomation.

3. Double-click the help file named GovernanceAutomationWebAPISDK.chm to view the information.

Getting Started Refer to the sections below for important information on getting started with Governance Automation Web API SDK.

Environment Requirement For Governance Automation Web API SDK, the .NET Framework version must be v4.5 or later.

Required DLL File Governance Automation API libraries are installed during the Governance Automation installation. You can find them in the directory …\AvePoint\GovernanceAutomation\bin. You must add the required DLL file GAWeb.dll into your project references.

Supported Features in Governance Automation Web API SDK The following features are supported by Governance Automation Web API SDK:

*Note: All types of services are supported.

• Get a list of activated services that the login user has the permission to use

• Get a specific service by service ID

• Put a request model

• Update a request model

• Create a request depend on a posted request model

• Get a specific request by request ID

• Update a request

• Submit a request by request ID

248


• Cancel a request by request ID

• Get a list of requests that the login user has created

• View Site Collection Report – Get a list of all Governance Automation managed site collections

• View Site Report – Get a list of all Governance Automation managed sites

Implementing Governance Automation API for Create Site Collection Request Refer to the following example to implement Create Site Collection request through Governance Automation API.

The examples provided below are based on the information listed in Governance Automation SDK Documentation, which can be found in GovernanceAutomationWebAPISDK.chm.

Logging into Governance Automation To log into Governance Automation, refer to the following example:

RequestExample serviceRequest = new RequestExample();

RequestExample.HostName = "10.2.4.67";

RequestExample.Port = "15000";

RequestExample.UserName = "admin";

RequestExample.Password = "admin";

RequestExample.LogonMode = AuthenticationMode.Local;

serviceRequest.Logon();

249


Managing Create Site Collection Requests Refer to the following example to manage Create Site Collection requests:

System.Net.ServicePointManager.ServerCertificateValidationCallback =

((sender, certificate, chain, sslPolicyErrors) => true);

RequestExample serviceRequest = new RequestExample();

serviceRequest.LogonAsLocal();

serviceRequest.GetSecurityToken();

ServiceExample serviceRequestDefinition = new ServiceExample();

List<APIService> services = serviceRequestDefinition.Get();

APIService service = services.FirstOrDefault(s => s.Type == GAServiceType.ProvisionSiteCollection && s.Name == "Create a Site Collection (Sample)");

if(service != null)

{

APIService apiService = serviceRequestDefinition.Get(service.Id, service.Type);

APIServiceProvSite serviceSite = (APIServiceProvSite)apiService;

APIRequest request = serviceSite.APIRequest;

APIRequestProvSite requestSite = (APIRequestProvSite)request;

250


requestSite.Title = "your request title";

requestSite.Description = "This is service request created by Governance Automation Web API";

requestSite.SiteTitle = "your site title";

requestSite.SiteDescription = "This site is created by API;"

requestSite.Url.Prefix = serviceSite.DefaultWebApplication;

requestSite.Url.ManagedPath = serviceSite.WebAppManagedPathMappingSelection[serviceSite.DefaultWebApplication][0];

requestSite.Url.Url = "your site url";

requestSite.PrimaryContact = "domain\\primarycontactuser";

requestSite.SecondaryContact = "domain\\secondarycontactuser";

List<CustomMetadata> customMetadatas = new List<CustomMetadata>();

foreach (CustomMetadata metadata in serviceSite.CustomMetadata)

{

if (metadata.TagName.Equals("your metadata name", StringComparison.OrdinalIgnoreCase))

{

metadata.DefaultValue = "your metadata value";

}

customMetadatas.Add(metadata);

}

requestSite.CustomMetadatas = serviceRequest.ConvertObjToString(customMetadatas);

requestSite.SiteTemplate = HttpUtility.UrlDecode(serviceSite.DefaultTemplate);

251


requestSite.Language = serviceSite.DefaultLanguage;

foreach (KeyValuePair<Guid, string> policy in serviceSite.PolicySelection)

{

if (policy.Value.Equals("your policy name", StringComparison.OrdinalIgnoreCase))

{

requestSite.PolicyId = policy.Key;

}

}

Guid requestId = serviceRequest.Post(requestSite);

request = serviceRequest.Get(requestId, GAServiceType.ProvisionSiteCollection);

requestSite = (APIRequestProvSite)request;

requestSite.Title = "your request title changed";

requestSite.SiteTitle = "your site title changed";

requestSite.Url.Prefix = "http://yourwebapplicationprefix:yourport";

requestSite.Url.ManagedPath = "/sites/";

requestSite.Url.Url = "your site url changed" + DateTime.Now.Millisecond;

requestSite.SecondaryContact = "domain\\user";

bool submitSuccess = false;

252


if (serviceRequest.Put(requestSite) == "true")

{

submitSuccess = serviceRequest.Submit(requestId);

}

if (submitSuccess)

{

string comment = "Cancel this Request By Web Api.";

serviceRequest.Cancel(requestId, comment);

}

}

253


Appendix A: Configuring a Filter Policy This section describes how to configure Filter Policies in DocAve Control Panel in order for Governance Automation to leverage DocAve Granular Backup and Restore, the Auditor feature in DocAve Report Center, and the Dead Account Cleaner feature in DocAve Administrator.

Configuring Filter Policy to Use DocAve Granular Backup and Restore Log into DocAve and navigate to Control Panel > Filter Policy and click Create. Configure the Filter Policy as follows:

1. Name – Enter a name for this filter policy.

2. Description – Enter an optional description for future references.

3. Click Add a Filter Level Group to add a filter rule. The filter rule configuration field appears.

a. Select Site Collection from the first drop-down menu.

b. Click Add a Criterion and select Custom Property: Text from the second drop-down menu. An additional text box will appear after the second drop-down menu for you to input the custom property text.

c. In the new text box, enter Gov Auto Policy.

d. In the Condition column, select Equals from the next drop-down menu.

e. In the Value column, enter the exact name of the policy for which you have Granular Backup enabled in the DocAve Configurations section.

4. When you have finished adding all of the policies to the Criteria, click OK to save this Filter Policy.

Once the Filter Policy has been created, you must add it to a Granular Backup and Restore plan. For information on configuring Granular Backup and Restore, see the DocAve Granular Backup and Restore User Guide.

*Note: You can add more than one Governance Automation Policy to each Filter Policy if you know that you would like to use the same Granular Backup and Restore Plan for all site collections affected by those policies. Otherwise, create separate Filter Policies so that you can associate the different Governance Automation policies to the different Granular Backup and Restore plans.

254


http://www.avepoint.com/assets/pdf/sharepoint_user_guides/Granular_Backup_and_Restore_User_Guide.pdf

http://www.avepoint.com/assets/pdf/sharepoint_user_guides/Granular_Backup_and_Restore_User_Guide.pdf

Configuring Filter Policy to Use Audit Controller in DocAve Report Center Log into DocAve and navigate to Report Center > Settings > Audit Controller. When creating a new Audit Controller plan or modifying an existing one, under Apply Rule Settings, configure the Filter Policy as follows:

1. Click Add a Filter Category.

2. In the Rule column, make sure that Site Collection is selected. All criteria within this category will only apply at the site collection level.

3. Click Add a Criterion.

4. For the first criterion, configure the following:

a. In the Rule column, select Custom Property: Text

b. In the text box that appears next to the drop-down menu in the Rule column, enter Gov Auto Policy

c. In the Condition column, select Equals

d. In the Value column, enter the EXACT name of the Governance Automation policy for which you want to use this Audit Controller plan.

5. Be sure all changes are saved.

For information on configuring the rest of the Audit Controller plan in DocAve Report Center, see the DocAve Report Center User Guide.

*Note: You can add more than one Governance Automation policy to each Filter Policy if you know that you would like to use the same Audit Controller plan for all site collections affected by those policies. To do so, add a criterion for each policy. Otherwise, create separate Audit Controller plans.

Configuring Filter Policy to Use Dead Account Cleaner in DocAve Administrator Log into DocAve and navigate to Control Panel > Filter Policy and click Create. Configure the Filter Policy as follows:





255


http://www.avepoint.com/assets/pdf/sharepoint_user_guides/Report_Center_User_Guide.pdf

b. Click Add a Criterion and select Custom Property: Text from the second drop-down menu. An additional text box will appear after the second drop-down menu for you to input the custom property text.

c. In the new text box field, enter Gov Auto Policy.

d. In the Condition column, select Equals from the next drop-down menu.

e. In the Value column, enter the exact name of the policy for which you have Dead Account Cleaning enabled in the DocAve Configurations section.

4. When you have finished adding all of the policies to the Criteria, click OK to save this Filter Policy.

Once the Filter Policy has been created, you must add it to a Dead Account Cleaner plan. For information on configuring Dead Account Cleaner plans, see the DocAve Administrator User Guide.

*Note: You can add more than one Governance Automation policy to each Filter Policy if you know that you would like to use the same Dead Account Cleaner Plan for all site collections affected by those policies. Otherwise, create separate Filter Policies so that you can associate the different Governance Automation policies to the different Dead Account Cleaner Plans.

Configuring Filter Policy to Use DocAve Deployment Manager Log into DocAve and navigate to Control Panel > Filter Policy and click Create. Configure the Filter Policy as follows:





b. Click Add a Criterion and select Custom Property: Text from the second drop-down list. An additional text box will appear after the second drop-down list for you to enter the custom property text.

c. In the new text box field, enter Gov Auto Policy.

d. In the Condition column, select Equals from the drop-down list.

e. In the Value column, enter the exact name of the policy for which you have DocAve Deployment Manager enabled in the DocAve Configurations section.

4. When you have finished adding all of the policies to the filter policy, click OK to save this filter policy.

Once the filter policy has been created, you must add it to a deployment plan. For information on configuring a deployment plan, refer to Appendix C: Configuring DocAve Deployment Manager Plans.

256


http://www.avepoint.com/assets/pdf/sharepoint_user_guides/Administrator_User_Guide.pdf

*Note: You can add more than one Governance Automation policy to each filter policy if you know that you would like to use the same deployment plan for all site collections affected by those policies. Otherwise, create separate filter policies so that you can associate the different Governance Automation policies to the different deployment plans.

257


Appendix B: Configuring DocAve Archiver Profiles In order for Governance Automation to utilize DocAve Archiver to archive site collections, Archiver Profiles must be created in DocAve.

*Note: Each farm needs its own Archiver Profile.

Log into DocAve and navigate to Archiver > Profile Manager, and click Create. Configure the Archiver Profile as follows:

1. Name – Enter a Name and an optional Description for the new Archiver Profile.

2. Farm – Select the farm from the drop-down menu.

3. Category – Specify the category in the text box.

4. Click Next.

5. In the Rules page, click Create. A popup window will appear for you to configure the new Rule for this Archiver Profile. Configure the Rule as follows:

• How would you like to archive the SharePoint content? – Select Create a new rule. Then enter a Name and an optional Description for this new Rule.

• What type of content would you like to archive? – Select Site Collection from the drop-down menu.

• How would you like to define the content to be archived? – Configure the following Criteria:

o Select URL in the first drop-down menu.

o Select Matches in the second drop-down menu.

o Enter * in the text box.

• Where would you like to store the archived data? – Select the desired Storage Policy. For information on how to configure Storage Policies, see the DocAve Control Panel Reference Guide.

• Data Compression – Choose to compress the data when archiving. A low compression level takes less time to complete but results in larger data sets, while high compression level takes more time to complete but results in smaller data sets. Note that smaller data sets results in slower backup and recovery.

• Data Encryption – Choose to enable Data Encryption. Enabling this option results in slower backup and recovery.

When you have finished configuring the new Archiver Rule, click OK to save and return to Archiver Profile configuration.

6. Configure the desired settings for Processing Pool which allows you to a lot specific resources to run the Archiving job, Workflow and Notification.

7. Schedule – Be sure that No schedule is selected.

258




8. Click Next.

9. Review your settings, then click Finish to save the new Archiver Profile.

259


Appendix C: Configuring DocAve Deployment Manager Plans In order for Governance Automation to utilize DocAve Deployment Manager to deploy site collections, Deployment plans must be created in DocAve.

*Note: Each farm needs its own deployment plan.

Log into DocAve and navigate to Administration > Deployment Manager. Refer to the following instructions to configure a deployment plan.

Creating a Deployment Mapping To configure a deployment plan, a deployment mapping must be created first.

1. In the Source pane, click on a farm to expand its object tree. Continue clicking the relevant objects until you find the object you wish to deploy from. Select the source object.

2. In the Destination pane, click on a farm to expand its object tree. Continue clicking the relevant object until you find the object you wish to deploy to. Select the destination object.

3. Click Add to Queue on the ribbon. The Add to Queue window will pop up. Depending on the mapping you are creating, some of the following settings may be configured:

*Note: Deployments can only be mapped between a source and destination that are using the same version of SharePoint. If the experience version of the site in SharePoint 2013 is SharePoint 2010, it can only be deployed to the site that has the same experience version.

• Reorder the Solutions – If there are multiple solutions being deployed, you may configure the order that the solutions are deployed in by selecting the desired place in the Order column.

• Conflict Resolution – Choose Skip, Merge, or Replace from the Container level conflict resolution drop-down menu. Select the Check lower objects checkbox to configure content level conflict resolution. Choose Skip, Overwrite, or Overwrite by Last Modified Time from the Content level conflict resolution drop-down menu. For detailed information on how Deployment Manager resolves conflicts based on these configurations, see DocAve Deployment Manager User Guide.

• Mappings – If you have previously configured Domain Mapping, User Mapping, or Language Mapping in Control Panel, you may choose to apply them to this deployment mapping when adding this deployment to the Queue.

• Filter Policy – A filter policy allows you to designate specific object or data within each SharePoint level.

o Source – Select a previously created filter policy from the drop-down menu to filter the source object or data or click New Filter Policy to create a new one.

260


http://www.avepoint.com/assets/pdf/sharepoint_user_guides/Deployment_Manager_User_Guide.pdf

o Destination – Select a previously created filter policy from the drop-down menu to filter the destination object or data or click New Filter Policy to create a new one.

*Note: The filter policy in the Destination drop-down menu only filters at the site collection level and site level filter rules configured in filter policy. Lower level objects or data in the destination cannot be filtered even if the selected filter policy contains rules applicable to those objects.

• Source Content Settings – Select the source components that you want to deploy to the destination:

o Include security – Enable this option to deploy user and/or group permissions to the destination node.

o Include user profile – Enable this option to deploy user profile to the destination node. Make sure that the selected destination’s Web application is connected to the User Profile Service Application before you select this option.

o Include User Content – Enable this option to deploy the customized content to the destination node.

• Workflow – Enable the Include workflow definition option to also deploy the definition of existing source workflows to the destination node.

• Deploy to Relative Lists and Sites – Enable this option to synchronize the source content type to the destination. If you have deployed a content type from the source to the destination before, with this option selected, the content type changes will be synchronized to the destination after this deployment job. When this option is not selected, the content type changes will not be synchronized to the destination content type that has already been used by lists or sites.

• Preserve the Null Column Values – Choose to preserve the null value of item column(s) in the source. Some values of the newly created column(s) may be null for previous items, and this option allows you to choose to replace the null value with the default value in the destination. By default, we will preserve the null value for those items.

• Web Configuration Settings – This option appears when you perform an IIS Site Files level deployment. Choose to include Web Configuration in the deployment job. By default, the following parameters are included for searching the related configuration in web.config files:

configuration/SharePoint/PeoplePickerWildcards;

configuration/system.web/membership/providers;

configuration/connectionStrings;

configuration/connectionStrings;

You can customize the parameters according to the XPath format in the left pane of the interface.

Choose to include the parent node’s properties if the parent node does not exist in the destination by selecting the checkbox.

261


• Options – This option appears when you perform a Managed Metadata Service level deployment. Choose the deployment mode, Full Deployment or Incremental Deployment. A Full Deployment deploys all of the source content or settings to the destination, while an Incremental Deployment only deploys the modified settings since the last incremental or full deployment.

If selecting Incremental Deployment, the following options will be available:

o Modifications – Choose to deploy the modifications since the last job.

o Deletions – Choose to deploy the deletions since the last job. Click OK to add this deployment mapping to the Queue, or click Cancel to return to selecting Source and Destination nodes for the deployment mapping.

• Click OK to save your configurations.

Creating a Deployment Plan When you have finished adding the deployment mappings to the queue, click Save as a Plan on the ribbon or located at the bottom of the screen. You will be brought to the Save as a Plan interface. Configure the following settings to create a deployment plan:

1. Plan Name – Enter a Plan Name for this new plan. Then, enter an optional Description for future references.

2. Backup Environment Before Running Plan – Enable this option to back up the destination environment before running the plan. You must then select a storage policy. Enabling this option allows you to use the Rollback feature in Job Monitor.

3. Schedule Selection – Configure a schedule for this plan:

• No Schedule – The plan will be executed after the service request is approved.

• Start Time – Select the date and time you wish this plan to be executed. If applicable, you may change the time zone by clicking on the hyperlink to select a different time zone.

4. Notification – Choose the type of notification and designate which DocAve user will receive an e-mail notification report. Select a notification profile you previously created from the drop-down list. Click View beside the drop-down list to view details of the notification profile, or click New Notification Profile from the drop-down list to create a new one.

5. Associated Plan Group – Add the plan to one or more plan groups to manage multiple plans with common settings. Select a plan group you previously created from the drop-down list or click New Plan Group from the drop-down list to create a new one.

6. Click OK located at the bottom of the screen to save the plan.

262


Appendix D: Configuring a Policy Enforcer Profile Before creating the Policy Enforcer profile, you must configure the source collection policy for the nodes selected on the SharePoint farm.

Configuring a Source Collection Policy To configure the source collection policy, complete the following steps:

1. In DocAve Manager, navigate to Administration > Administrator. On the Policy Enforcer tab, click Source Management on the ribbon to configure the auditing and scanning policy.

2. Click Create in the Manage group on the ribbon to create a new source collection policy.

3. In the New Source Collection Policy interface, configure the following settings:

a. Source Collection Policy – Enter the Name for the policy you are about to create. Enter an optional Description for future references.

b. Select Auditor Mode or Scan Mode to configure the corresponding details before applying them on the selected nodes of the SharePoint farm.

• Auditor Mode – Select the Auditor Mode checkbox and click Configure in the Manage group on the ribbon. In the pop-up window, all the enabled Auditor Mode event types are displayed in the Available Event Type column.

o Interval – Specify how often this source collection mode will run to collect the Audit events of the enabled event types in SharePoint to identify out of policy objects. The collected data is stored as DocAve Job Data. Frequency of collection can improve quality of remediation but can impact SharePoint performance.

o Event Type – By default, all of the event types are enabled to ensure all of the available audit events can be collected by DocAve to identify out of policy objects in SharePoint. To change the event types’ statuses in this source collection policy, select the event types whose status you want to change, click Disable to disable the selected event types or click Enable to enable the event types. The Audit events of the disabled event types will not be collected by DocAve to identify out of policy objects.

Click OK to save the configuration.

• Scan Mode – Select the Scan Mode checkbox and click Configure in the Manage group on the ribbon. In the pop-up window, all the scanning conditions are displayed in the Event Type column.

o Interval – Specify how often this source collection mode will run to scan the conditions of the enabled event types in SharePoint to identify out of policy objects, settings, permissions and/or features. The collected

263


data is stored as DocAve Job Data. Frequency of collection can improve quality of remediation but can impact SharePoint performance.

*Note: If Day(s) is selected as the interval, you can specify a start time for the jobs of this source collection mode.

o Event Type – By default, all of the event types are enabled to ensure all of the available conditions can be collected by DocAve to identify out of policy objects in SharePoint. To change the event types‘ statuses in this source collection policy, select the event types whose statuses you want to change, click Disable to disable the selected event types or click Enable to enable the event types. The corresponding conditions of the disabled event types will not be collected by DocAve to identify out of policy objects.

Click OK to save the configuration.

c. Click Save to save the configuration of the source collection policy.

Creating a Policy Enforcer Profile To create the Policy Enforcer profile, complete the following steps:

1. In DocAve Manager, navigate to Administration > Administrator. On the Policy Enforcer tab, click Profile Manager on the ribbon to configure the Policy Enforcer profile.

2. Click Create in the Profile Management group on the ribbon to create a new Policy Enforcer profile.

a. Profile Name – Enter the Name for the profile you are about to create. Enter an optional Description for future reference.

b. Farm – Select a SharePoint farm from the drop-down list to apply the configured profile on this selected farm.

*Note: The selected farm is the one where the Governance Automation managed site collection resides.

c. Source Collection Policy –Select one previously configured source collection policy for the event types to be monitored by Policy Enforcer from the drop-down list, or select New Storage Policy to create a new one.

d. Retention Policy – Specify the retention period by entering a positive integer and selecting Day(s), Week(s), or Month(s) for keeping the job data associated with this profile.

3. Click Add Rule in the Rule Management group on the ribbon. All of the rules for the actions and conditions in SharePoint will be displayed in the pop-up window. Select the checkboxes of the rules that you want to apply on the selected nodes of the SharePoint farm and click OK to add the selected rules to this profile.

4. Click Save in the Profile Management group to save the configuration of this profile.

264


Notices and Copyright Information Notice The materials contained in this publication are owned or provided by AvePoint, Inc. and are the property of AvePoint or its licensors, and are protected by copyright, trademark and other intellectual property laws. No trademark or copyright notice in this publication may be removed or altered in any way.

Copyright Copyright ©2014 AvePoint, Inc. All rights reserved. All materials contained in this publication are protected by United States and international copyright laws and no part of this publication may be reproduced, modified, displayed, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of AvePoint, 3 Second Street, Jersey City, NJ 07311, USA or, in the case of materials in this publication owned by third parties, without such third party’s consent. Notwithstanding the foregoing, to the extent any AvePoint material in this publication is reproduced or modified in any way (including derivative works and transformative works), by you or on your behalf, then such reproduced or modified materials shall be automatically assigned to AvePoint without any further act and you agree on behalf of yourself and your successors, assigns, heirs, beneficiaries, and executors, to promptly do all things and sign all documents to confirm the transfer of such reproduced or modified materials to AvePoint.

Trademarks AvePoint®, DocAve®, the AvePoint logo, and the AvePoint Pyramid logo are registered trademarks of AvePoint, Inc. with the United States Patent and Trademark Office. These registered trademarks, along with all other trademarks of AvePoint used in this publication are the exclusive property of AvePoint and may not be used without prior written consent.

Microsoft, MS-DOS, Internet Explorer, Microsoft Office SharePoint Servers 2007/2010/2013, SharePoint Portal Server 2003, Windows SharePoint Services, Windows SQL server, and Windows are either registered trademarks or trademarks of Microsoft Corporation.

Adobe Acrobat and Acrobat Reader are trademarks of Adobe Systems, Inc.

All other trademarks contained in this publication are the property of their respective owners and may not be used without such party’s consent.

Changes The material in this publication is for information purposes only and is subject to change without notice. While reasonable efforts have been made in the preparation of this publication to ensure its accuracy, AvePoint makes no representation or warranty, expressed or implied, as to its completeness, accuracy, or suitability, and assumes no liability resulting from errors or omissions in this publication or from the use of the information contained herein. AvePoint reserves the right to make changes in the Graphical User Interface of the AvePoint software without reservation and without notification to its users.

AvePoint, Inc. Harborside Financial Center, Plaza 10 3 Second Street, 9th Floor Jersey City, New Jersey 07311 USA

265


Date post:	25-Apr-2020
Category:	Documents
Upload:	others
View:	12 times
Download:	0 times