Manage repository
- Last UpdatedNov 26, 2025
- 4 minute read
A Repository contains workflow definitions, Queues, Calendars, Workflow execution data, and Business Activity Monitoring (BAM) data. The Repository Provider for the repository is also defined while creating a repository.
AVEVA Work Tasks supports only CONNECT repository provider by default.
Manage repository window fields
The table explains the fields of the Manage Repository window:
|
Field Name |
Description |
Example |
|---|---|---|
|
Repository Name |
Assign a name for the repository. Ensure that you do not use special characters other than ()-=[]{}\|;,<>./!@$^`~ in the repository name. |
Telematics Repository |
|
Description |
Provide a description for the repository. |
This stores Telematics Employee Leave Details. |
|
From mail |
Email ID used by the email channel to send emails. We recommend to define the From mail and Exception to mail in a production environment. This will assist the process administrator to track any exception that might occur in the Workflow instance due to data mismatch or any configuration related issue. An email with exception details will be sent to the mail ID defined in Exception to mail. The from address of email channel mails continue to use the previously configured email ID, even after this property is edited and the repository is saved. To avoid this, restart the Workflow Engine Service and Communication Service. |
admin@domain.com |
|
Exception to mail |
Define an exception email ID. Exceptions generated by the Workflow Engine when an activity fails is sent to the email ID specified in Exception to mail. |
admin@domain.com |
|
Alert initiator of the Workflow |
Determines if the status of a workflow should be sent as a notification mail to the initiator of the workflow. |
A process with a rule to check the pending leave available for the employee exists. If this rule fails due to a data mismatch, the employee who submitted the leave application will receive an e-mail with details related to the exception as a notification. |
|
Servers |
Lists the servers available in the Farm. Repository will be available only to the mapped servers. |
BANVM-RND5 |
|
Enterprise Consoles |
Lists all the Enterprise Consoles for a selected AVEVA Work Tasks Server. Repository will be available only to the mapped Enterprise Console sites. |
http://BANVM-RND5:80000/EnterpriseConsole |
|
Enable Theme |
Select this checkbox to enable the defined theme. Note: To use Process Designer, ensure that you check this checkbox and then type the Theme Name as "Default". |
- |
|
Theme Name |
AVEVA Work Tasks supports themes that you can use to change the look and feel of the user interface. It provides Default and Lite themes. |
- |
|
Resource Provider |
Lists the various default resource providers supported by AVEVA Work Tasks. Resource providers are also termed as User Provider. A User Provider is a data store containing information about the user. Only CONNECT resource provider is applicable. |
CONNECT |
|
Custom Application Folder |
Not applicable. |
- |
|
Hide Repository |
Select this option to make the repository unavailable to the Farm. |
- |
|
Source path |
Not applicable. |
- |
|
Attachment Storage Path |
Not applicable. |
- |
|
Auto Log Off Settings |
Automatically logs out the logged in user after the designated period of inactivity. Enter the time in minutes. This field accepts only valid integer values between 1 to 360. 0 minute is an invalid value. The maximum time allowed is 360 minutes. In some cases there may be a slight time lag of few seconds which can be maximum of 10 seconds. If you leave this field empty, then the log off time is not set for the repository, and the session does not log off automatically. You use this field to define the log off time for all the providers of a particular repository. If you have administrator rights to a repository, you can also set separate log off time manually for each provider. For more information about manually setting the auto log off time at the provider
level, see Configuring the Definition XML. Note: Default session timeout for the Enterprise Console is 40 minutes. A custom error
page is displayed if the Enterprise Console remains idle for more than the session
timeout. |
1 to 360 (minutes) |
|
Require User Credentials |
Request for user credentials for Work Tasks Pro app after the set time is elapsed. Enter the time in hours This field accepts only valid integer values between 1 to 48. If you leave this field empty, then the setting is disabled. |
1 to 48 (in hours) |
|
Offline Support |
Select this option to enable offline submission of items in Work Tasks Pro app. |
|
|
Refresh on Work Item submission |
Select this option to enable Inbox refresh on Work Item submission in Work Tasks Pro app. |
|
|
Timeout |
Enter the time in seconds to set the timeout. If the value is set as 0, then there
is no timeout. |
- |
|
Label for Fill Form |
Enter the name for the Fill Form label. |
- |
|
Date Configuration Flag for Alternate Actors |
Select the Enable Date Settings option to set the From date and To date as mandatory while creating alternate actors. For more information about creating alternate actors, see Alternate Actors topic in the User Guide. |
- |
To verify successful creation of the repository
-
Click Enterprise Console site URL in the Site Path column of the Repository List page.
The repository created is listed in the Enterprise Console page.
Add the created Enterprise Console Site link into "Add to Favorites" to easily navigate in future.
-
Click Repository User Provider (CONNECT) link to logon to the repository.
The Enterprise Console home page appears.
This indicates successful creation of a Repository.
All features are available for a user with administrative privileges.
Note: After creating a new repository or editing an existing one, the changes may not immediately appear in the Provider list within Enterprise Console. To ensure the updated repository is recognized, perform an IIS reset or recycle the AVEVA Work Tasks application pool in IIS.