Disable or Lock QuerySurge Projects (Versions: 8.0+)

Versions: 8.0+

QuerySurge allows placing a Project into two restricted states (Disabled or Locked), to aid in finer-grained access control and maintenance activities for Projects. Disabled projects are hidden from users and cannot be logged into, while locked projects restrict activity to read-only actions. Setting a project in one of these restrictive states can be done when creating a new project or editing any existing one. 

When changing project to a restricted state, a alert message must be submitted to inform users of the pending changes. This alert was created to avoid potential data loss when project states are changed.

Disabling Projects

Disabling a Project will prevent all assigned users from accessing a Project. Global Admins may still modify the Project's attributes, including user and Agent assignments. In Global Admin views, disabled Projects are denoted by a gray indicator in the Enabled column.

To disable a Project:

1. Log into QuerySurge Global Administration Portal as a Global Admin.
2. Navigate to QuerySurge Administration > Projects.
3. Select the Project to be disabled, and click Edit (or double click the Project in the list). The Edit Project window will appear.
4. For the Enabled option, select Disabled.
5. Click Save. The Notify Users window will appear.
6. Specify options for the notification:
   Notification Time (minimum 5 seconds): Number of seconds prior to disabling a project to notify users. 
   Comment: Notification which will appear for end users informing of the disabling of the project. The comment may be up to 1023 characters long.
   
7. Click Continue.

QuerySurge will display a notification message with the specified comment to all users logged in and viewing the Project. After the notification time passes, the Project will become disabled, and all users currently accessing the Project will be redirected to another Project if one is available. Those users who do not have access to another enabled project will be logged out of QuerySurge.

Note: All default project assignments for the disabled Project will be reset to another available project which that user has access to. 

Note: Users that are only assigned to disabled projects may not login to QuerySurge until one or more Projects are re-enabled. 

To re-enable the Project, follow the above steps to edit the Project, and for the Enabled option, change it back to Enabled.

Locking Projects

Locking a Project will set it in a read-only mode. In a locked Project, all assigned users will only be able to view assets and run reports; users may not modify any assets (including Design assets, Test Suites, Connections, etc.) or schedule executions (Design-Time Runs or Scenarios). Additionally, Global Admins may not edit the Project (other than to unlock it), or change user and Agent assignments. In Global Admin views, locked Projects are denoted by a gold padlock indicator in the Locked column.

To lock a Project:

1. Log into QuerySurge Global Administration Portal as a Global Admin user.
2. Navigate to QuerySurge Administration > Projects.
3. Select the Project to be disabled, and click Edit (or double click the Project in the list). The Edit Project window will appear.
4. For the Locked option, select Locked.
5. Click Save. The Notify Users window will appear.
6. Specify options for the notification:
   Notification Time (minimum 5 seconds): Number of seconds prior to locking a project to notify users. 
   Comment: Notification which will appear for end users informing of the locking of the project. The comment may be up to 1023 characters long.
7. Click Continue.

QuerySurge will display a notification message with the specified comment to all users logged in and viewing the Project. After the notification time passes, the Project will become locked; users will not be able to edit any assets in the Project until it is unlocked.

To unlock the Project, follow the above steps to edit the Project, and for the Locked option, change it back to Unlocked.

Note: When a Project is currently exporting, it may not be unlocked.