Listen
Translate
Robots Repository
Product provides functionality to store and manage various files (e.g., task, workflow, and other supporting files) that are required to support the user to successfully and efficiently orchestrate automation.
Audit log details: Delete Robot
- Audience & purpose
-
As an Automation Administrator, you want to check who deleted a Robot from the repository. This:
- Facilitates tracking of all the changes that Robots/files/folders have undergone.
- Allows you to give a better description of error messages when the action was unsuccessful.
Deleting a Robot: Audit details
The Audit Log will capture the following details when a "Delete Robot" operation is performed:
- The breadcrumb trail will show "Audit log" → "View action".
- The "Action details" group box will contain:
- Status: Successful/Unsuccessful
- Action type: Delete Robot
- Action taken by: <username>
- Source: Product/Product Client
- Object type: Action
- Time: <Date and time operation performed>
- Item name: Name of Robot
- Device: N/A or Client machine name
- Start time: N/A
- Results: Show this for unsuccessful actions and the error message (without correction action) that was shown to you while performing the operation.
- The Task bot/Meta bot details group box will show the following details
Attribute Value Path Path in the Product "My Docs" → "Sample docs" Object Type Robot Robot type Taskbot/Metabot - Click the "Back" button to return to the page you came from.
Security
This page will not be accessible to unauthorized users.
Audit log details: Delete file
- Audience & purpose
-
As an Automation Administrator, you want to check who deleted a file from the repository. This will:
- Facilitate tracking of all changes that bots/files/folders have undergone.
- Allows you to put better descriptions of error messages when the action was unsuccessful.
Delete audit details
The Audit Log will capture the following details when a "Delete" file operation is performed:
- The breadcrumb trail will show "Audit log" → "View action".
- The Action details group box will contain:
- Status: Successful/Unsuccessful
- Action type: Delete file
- Action taken by: <username>
- Source: Product/Product Client
- Object type: Action
- Time: <Date and time the operation was performed>
- Item name: Name of Robot
- Device: N/A or the Client machine if it is from the Product Client.
- Start time: N/A
- Results: This will show for unsuccessful actions and the error message (without corrective action) that was shown to the user while performing the operation.
- The Document/Workflow details group box will show the following details:
Attribute Value Path Path in the Product My Docs → Sample docs Object type File File type Document, Executable, Report, Script, Workflow - Click the "Back" button to return you to the page you came from.
Security
This page will not be accessible to unauthorized users.
Audit log details: Delete folder
- Audience & purpose
-
As an Automation Administrator you want to check who deleted a folder from the repository. This:
- Facilitates tracking of all the changes that Robots/files/folder have undergone.
- Allows you to put a better description of error messages when the action was unsuccessful.
Deleting a folder audit details
The Audit Log will capture the following details when a "Delete folder" operation is performed:
- The breadcrumb trail will show "Audit log" → "View action".
- The "Action details" group box will contain:
- Status: Successful/Unsuccessful
- Action type: Delete folder
- Action taken by: <username>
- Source: Product
- Object type: Action
- Time: <Date and time operation performed>
- Item name: Name of folder
- Device: N/A
- Start time: N/A
- Results: Show this for unsuccessful actions and the error message (without correction action) that was shown to you while performing the operation.
- The "Folder details" group box will show the following details:
Attribute Value Path Path in the Product "My Docs" → "Sample docs" Object Type Folder Folder type User-created - Click the "Back" button to return to the page you came from.
Security
This page will not be accessible to unauthorized users.
Audit log details: Edit Robot
- Audience & purpose
-
As a Product Administrator with the "Edit" privilege, this will allow you to facilitate the tracking of all the changes that Robots, Files, and Folders have undergone.
- It will also allow you to enter a better description of error messages when the action was unsuccessful.
Edit audit details
The Audit Log will capture the following details when an "Edit" Robot operation is performed:
- The breadcrumb trail will show "Audit log" → "View action".
- The Action details group box will contain:
- Status: Successful/Unsuccessful
- Action type: Edit Robot
- Action taken by: <username>
- Source: Product
- Object type: Action
- Time: <Date and time the operation was performed>
- Item name: Name of Robot
- Device: <Client machine from where the user accessed it>
- Start time: N/A
- Results: This will show for unsuccessful actions and the error message (without corrective action) that was shown to the user while performing the operation.
- The Task bot/Meta bot details group box will show the following details:
Attribute Value Path My Tasks → Sample tasks Object type Robot Robot type Taskbot/Metabot Production Version 10 (Show only if the user updated it.) Version Control Unlocked (Show only if the user unlocked it.) - Click the "Back" button to return you to the page you came from.
Security
This page will not be accessible to unauthorized users.
Audit log details: Multiple delete
- Audience & purpose
-
As an Automation Administrator you want to check who deleted a File, Folder, or Robot from the repository. This:
- Facilitates tracking of all the changes that Robots/files/folder have undergone.
- Allows you to put a better description of error messages when the action was unsuccessful.
Description
Login to Product and go to the "Audit" tab.
- Click the "View" icon on the Audit entry row.
- The system will display the details page. See the following screenshot.
- The breadcrumb trail will show the "Audit log" → "View" action.
- Click "Back" to return to the previous page.
- The system will show Successful/Unsuccessful types of detail pages.
- The entire Audit log entry will be read-only. You can only act on the page-level toolbar.
- The lower-half of the page will show the details of a file at the time of the Audit entry.
Details
The "Result" box appears only for failure scenarios and contains the error message.
- Action details
- Status = (Unsuccessful, Successful)
- Time = <time>
- Action type = Delete file
- Object/file name
- Successful = <file name>
- Unsuccessful = If you know it, the <file name<, else "Unknown"
- Action taken by = <Username>
- Device = <Device name>
- Source = Product
- Start time = N/A
- <file type> details
- Size
- Path
- File type (values = Document, Executable, Report, Script, Workflow)
- Object type = File
- Number of bots that depend on this file = 0
Security
This page:
- Will be visible to the user who has deleted the file.
- Will be visible to users who have the "Audit log tab" permission.
- Will not be accessible to any other user.
Audit log details: Multiple unlock
- Audience & purpose
-
As an Automation Administrator, the system will audit log a multi unlock operation and capture the status on each Robot selected for unlock. This:
- Facilitates tracking of all the changes that Robots/Files/Folders have undergone.
- Allows you to put better descriptions of error messages when an action was unsuccessful.
Audit log details: Page for Robots
- Audience & purpose
-
As an Automation Administrator you want to check the tracking of all the changes that Robots/Files/Folders have undergone.
- It also allows you to put a better description of error messages when an action was unsuccessful.
Directions
Go to "Audit log" → "View action".
- Click "Back" to return to the previous page.
- The system will show Successful/Unsuccessful types of "Detail" pages.
- The entire Audit log entry will be read-only. You can only act on the page-level toolbar.
- The lower-half of the page will show the details of Robots/Files/Folders corresponding to the particular audit entry, not necessarily the latest data.
- Detail pages will include version control info when the VCS (Version Control System) is on.
Security
This page will not be accessible to any user except users who do not have one of the:
- "Upload", "Download", and/or the "Delete" permissions on "Robot"/"File".
- "Upload", "Download", "Delete", and/or "Execute" permissions on "Meta bots".
Audit log details: Unlock
- Audience & purpose
-
As an Automation Administrator you want to check who deleted a Robot from the repository. This:
- Allows you to capture who, when, and what has been done as part of this transaction to conform to various audit requirements.
Unlock audit details
The Audit Log will capture the following details when an "Unlock" operation is performed:
- The breadcrumb trail will show "Audit log" → "View action".
- The Action details group box will contain:
- Status: Successful/Unsuccessful
- Action type: Unlock bot/file
- Action taken by: <username>
- Source: Product
- Object type: Action
- Time: <Date and time the operation was performed>
- Item name: Name of bot
- Device: N/A
- Start time: N/A
- Results: This will show for unsuccessful actions and the error message (without correction action) that was shown to the user while performing the operation.
- If it is a Robot, the Task bot/Meta bot details group box will show the following details:
Attribute Value Path My Tasks → Sample tasks Object type Robot Robot type Taskbot/Metabot - If it is a file, the "File details" group box will show the following details:
Attribute Value Path My Docs → Sample docs Object type File File type Document/Workflow - Click the "Back" button to return you to the page you came from.
Security
This page will not be accessible to unauthorized users.
Delete repository file: Single
- Audience & purpose
- As Product user with "Delete" privileges, you can delete files that are no longer required in the repository so that they will not be accidentally used while creating an automation.
- Note: See the "Confirmation and Error Messages reference" data table at the end of this topic.
Deleting a file with version control "Off"
Versioning Control is currently not enabled.
- Login to Product and go to the "Robots" tab.
- Go to a folder to which you have the "Delete" privilege (this is set at the folder level while creating a role).
- Note: An Admin user by default has access to all files and folders with all privileges.
- Click the "Delete" icon to delete a specific file (at the object-level toolbar).
- Note: If you do not have the "Delete" privilege, the Delete icon will not appear.
- The system will let you delete a file only:
- If no other file has a dependency on this file.
- If this not currently being processed (run).
- If this is not scheduled for any future run.
- Note: See the following "Confirmation and Error messages reference" topic.
- After closing the confirmation message and if the delete was successful, a toast message with name of "file/bot" and "successfully deleted" will be shown. See the following screenshot.
- If a file cannot be displayed, the error message will be displayed on the screen above the grid. See the following "Confirmation and Error messages reference" topic.
- If the delete was successful the file will be removed from the list.
- For your guide:
- Object type = File
- File type (values = Document, Executable, Report, Script, Workflow)
- Object type = Robot
- Robot type (values = Task Robot, Meta Robot, IQ Robot)
- Object type = Folder
Deleting a file with version control "On"
If Version Control is turned on, the "Delete" icon will not appear on the User Interface for any file, or at the table level.
Confirmation and Error messages reference
The following data table lists messages you may encounter when using the "Robots" Landing page. The "Actions" column is listed in alphabetical order for your convenience.
Source: Robots Landing page # Action Current status Message Command buttons (Left to Right) 1. Delete Robot Confirm Delete. Do you want to permanently delete the <bot type> "<bot name>"? No = cancel
Yes = delete2. Delete Robot Robot is currently running. The <bot type> "<bot name> is currently running.
To continue, wait until the bot is finished and try again.Close 3. Delete Robot Robot is currently scheduled to run. The <bot type> "<bot name> is currently scheduled to run.
To continue, delete the scheduled occurrence and try again.Close 4. Delete Robot Cannot delete any dependency. One or more bots, listed below, are dependent on the <object type> <object name>.
You cannot delete a bot that is a dependency for another bot.
To delete this bot, please remove the dependency, and try again.
Robots dependent on this bot:
▸ Task Robot "<bot name>"Close 5. Delete Robot Delete privilege revoked. You no longer have permission to delete a bot.
To continue, please contact your system administrator.Close 6. Delete Robot/File Robot/File deleted. <name of object> wasn't found
It may have been renamed, moved, or deleted.
To continue, please contact your system administrator.Close 7. Delete Robot/File Robot/File access revoked (on the folder). You no longer have permissions for the bot/file <name of bot/file>
To continue, please contact your system administrator.Close 8. Delete File Confirm delete. Do you want to permanently delete the <file type> "<file name>"? No, cancel
Yes, delete9. Delete File Cannot delete any dependency. One or more bots, listed below, are dependent on the <object type> <object name>.
You cannot delete a file that is a dependency for another bot.
To delete this file, please remove the dependency, and try again.
Robots dependent on this file:
▸ Task Robot "<bot name>"Close 10. Delete File Delete privilege revoked. You no longer have permission to delete a file.
To continue, please contact your system administrator.Close 11. Delete Folder Confirm delete. Do you want to permanently delete the folder "<folder name>"?
No, cancel
Yes, delete12. Delete Folder Delete privilege revoked. You no longer have permission to delete a folder.
To continue, please contact your system administrator.Close 13. Delete Folder Folder not empty. The folder is not empty.
To continue, please delete all the files in the folder and try again.Close 14. Delete Folder Folder deleted. <name of object> wasn't found
It may have been renamed, moved, or deleted.
To continue, please contact your system administrator.Close 15. Delete Folder Folder access revoked. You no longer have permissions for the folder <name of folder>.
To continue, please contact your system administrator.Close 16. Edit No "Set production version" privilege. You no longer have permission to edit a file
To continue, please contact your system administrator.Close 17. Edit Robot/File Deleted <name of object> wasn't found.
It may have been renamed, moved, or deleted.
To continue, please contact your system administrator.Close 18. Edit Robot/File access revoked (on the folder). You no longer have permissions for the bot/file <name of bot/file>.
To continue, please contact your system administrator.Close 19. Run Robot deleted. <name of object> wasn't found.
It may have been renamed, moved, or deleted.
To continue, please contact your system administrator.Close 20. Run Robot access revoked (on the folder). You no longer have permissions for the bot/file <name of bot/file>.
To continue, please contact your system administrator.Close 21. Run No Run privilege (can be run/scheduled). You no longer have permission to run/schedule a bot.
To continue, please contact your system administrator.Close 22. Unlock Confirm unlock. Do you want to unlock the <object type>
"<object name> locked by <First Name> <Last Name> (<userid>)"?
You cannot undo this action from inside the Product.No, cancel
Yes, unlock23. Unlock Robot/File deleted. <name of object> wasn't found.
Close 24. Unlock Robot/File access revoked (on the folder). You no longer have permissions for the bot/file <name of bot/file>.
To continue, please contact your system administrator.Close 25. Unlock No Unlock privilege. You no longer have permission to unlock a file.
To continue, please contact your system administrator.Close 26. Unlock File is already unlocked. <name of bot/file> is already unlocked.
This may be because:To continue, please contact your system administrator.
- someone else unlocked it,
- someone else may have done an “undo check out”, or
- a new version may have been checked in.
Close 27. Unlock/Edit VCS turned off. You no longer can perform this operation as Version Control is turned off.
To continue, please contact your system administrator.Close 28. Unlock/Edit Cannot connect to VCS. Unable to connect to Version Control Repository.
To continue, please contact your system administrator.Close 29. View Robot/File Robot/File Deleted. <name of object> wasn't found.
It may have been renamed, moved, or deleted.
To continue, please contact your system administrator.Close 30. View Robot/File Robot/File access revoked (on the folder). You no longer have permissions for the bot/file <name of bot/file>.
To continue, please contact your system administrator.Close 31. View Folder Folder Deleted. <name of object> wasn't found.
It may have been renamed, moved, or deleted.
To continue, please contact your system administrator.Close 32. View Folder Folder access revoked. You no longer have permissions for the folder <name of folder>.
To continue, please contact your system administrator.Close
Delete repository files: Multiple
- Audience & purpose
-
As a Product user with "Delete" privileges, you will be able to delete files that are no longer required in the repository.
- This will prevent the files being accidentally used while creating an automation.
- It will allow you to delete multiple, unwanted files in a single shot.
Delete using the icon at Table level: version control is off
Note: In this scenario, Versioning Control is not enabled.
- Login to Product and go to the "Robots" tab.
- Go to a folder to which you have the "Delete" privilege.
- Admin users by default have access to all files and folders with all privileges (this is being set at the folder level while creating a role).
- Select multiple files or select all.
- You will be able to delete the selected files by clicking the "Delete" icon at the top (table level).
- The system will let you delete a file only:
- If no other file has a dependency on this file.
- If this is not currently being processed (run).
- If this is not scheduled for any future run.
Confirmation, error, and warning messages
The system will display the appropriate confirmation message. See the following data table.
Reason Title bar Message Buttons (L to R) Confirm delete Robot Delete bot Do you want to permanently delete the <bot type>, "<bot name>"? No, cancel | Yes, delete Cannot delete any dependency Delete bot Unable to continue because one or more bots are dependent on the <object type> "<object name>".
Robots dependent on this file: Task Robot "<Robot name>"Close Cannot delete a bot that is
currently runningDelete bot Unable to continue because the <bot type> "<bot name>" is currently running.
To continue, wait until the bot is finished and try again.Close Cannot delete a bot that is
currently scheduled to runDelete bot Unable to continue because the <bot type> "<bot name>" is currently scheduled to run.
To continue, delete the schedule and try again.Close Confirm delete file Delete file Do you want to permanently delete the <file type> "<file name>"? No, cancel | Yes, delete Cannot delete any dependency Delete file Unable to continue because one or more bots are dependent on the <object type> "<object name>".
Robots dependent on this file: Task Robot "<bot name>".Close If you confirm to proceed, the system will try to delete the selected files.
If the delete is successful, those file(s) will be removed from the list.
Delete using the icon at the Table level: version control is on
If version control is turned on, the "Delete" icon at the table level will not be present.
Delete repository subfolders
- Audience & purpose
-
As a Product user with "Delete" privileges, you want to delete files or folders that are no longer required in the repository.
- This is to prevent them being accidentally used while creating an automation.
- It also allows you to cleanup the repository.
Delete a subfolder
Login to Product and go to the "Robots" tab.
- Go to a folder to which you have the "Delete" permission.
- Note: An Admin user by default has access to all files and folders with all privileges.
- Only subfolders created under the "default" folders can be deleted.
- The default folders of Product such as My Docs, My Exes, My MetaRobots, My Reports, My Scripts, My Tasks, and My Workflows cannot be deleted.
- Delete a folder by clicking the "Delete" icon (next to the folder) in the Tree view, or via the "Delete" icon on the object-level tool bar.
- Note: If you do not have a Delete access permission to a folder, the Delete icon will not be shown.
- A folder can only be deleted after user confirmation.
- The folder to be deleted must be empty.
- It should not comprise any files and/or sub-folders.
- If you try to delete such folders, you are given an error. See the following message.
Reason Message Button The folder is not empty. To continue, please delete all the files in the folder and try again. Close - After closing the confirmation message, if successful, a toast with name of the folder and stating "successfully deleted" will be shown. See the following screenshot.
- If the folder cannot be deleted, an error message will be displayed on the page. See the following "Error messages" data table.
- If the delete action is successful, the folder will be removed from the tree and the view on the right side (if applicable).
- If the deleted folder was displayed on the grid, the folder will be displayed one level up in the structure to which the user has access.
- If there is no folder in that branch, pick the folder from the branch above it.
- If none, pick the one from the branch below it.
Error messages
Verify the following scenarios when a user is traversing on the left side of the folder view.
Action Reason Message Comment User clicks on a folder. The destination folder
no longer exists."Folder 'xxxxx' does not exist"
message appears on the page.User stays at the current folder. User clicks on a folder. The source and destination
folders no longer exist."Folder destination does not exist"
message appears on the page.Take the user up a level in that branch,
or go to the next branch if the source
branch no longer exists.No access to any folder. Access to all folders is deleted. You do not have access to any folder. The message will appear in the Tree view box. User clicks on a folder. The user no longer has access
to that folder."You no longer have access to Folder 'xxxxx'"
message appears on the page.User stays at the current folder
Download file from server (VCS disable)
- Audience & purpose
- You are a Product user with the "Download" permission and with VCS disabled. You want to download items from the Product.
Criteria
With VCS (Version Control System) disabled, see the following points.
- This is the same client behavior as offered in the Product version 10.3.
- Having the "Download" permission, you can download the latest and specific version of a Task, MetaRobot, Script, and Document files from the Product.
- If you do not have the "Download" permission you will not be allowed to download any of these items.
Download file from server (VCS enable)
- Audience & purpose
- You are a Product user with the "Download" permission and with VCS enabled. You want to download items from the Product.
Criteria
With VCS (Version Control System) enabled, see the following points.
- This is the same client behavior as offered in the Product version 10.3.
- Having the "Download" permission, you can download the latest and specific version of a Task, MetaRobot, Script, and Document files from the Product.
- If you do not have the "Download" permission you will not be allowed to download any of these items.
Edit Robot Details
- Audience & purpose
- As a Product user with the "Set production version" privilege, you want to set/change the production version of any Robot that you have access to so that the correct version of a Robot can be deployed when a schedule gets executed. For example, this will set a version as the "production version" so that the correct version gets deployed.
Setting the production version
Make sure that "Version Control" is ON.
- Login to Product and go to the "Robots" tab.
- Ensure you have the privilege "Set Production Version" to set a production version for a file.
- Go to a folder to which you have "View" access.
- The "Edit" icon will be enabled for any Robot files in that folder.
- Click the "Edit" icon.
- The system will display the "Edit" page with the following details (under the image). See the following screenshot. "Edit" page details:
- Name
- Size (includes a measurement value, e.g., KB)
- Path (Shows which folders it belongs to)
- The "Production version" table contains the following details:
- The default selection will be the previously set production version.
- If the production version was never set, then "None" will be shown as the default.
- Columns:
- Select
- Version: Label and values
- Description: If there is none, 2 dashes "- -" will be shown
- Last modified
- Modified by
- Close/Cancel button: This button will say "Close" until you make changes, then it will turn to "Cancel".
- Clicking "Close" returns you to where you came from.
- The "Save changes" button will be disabled until you make changes.
- If changes are successfully completed, an Audit entry is made, returns to where you came from, and shows a toast as described in the following data table.
Reason Title bar Message Buttons (L to R) Confirm save Save edit Do you want to save changes? Yes, No - If you confirm your actions, the system will save the changes you made.
- After closing the dialog, a toast message with the "name of the Robot" and "successfully edited" will be displayed. See the following screenshot.
- If any operation fails, an error message will be shown and you will stay in the same page.
- The system will display the general details as in the preceding screenshot.
Breadcrumb trail
The system will display the following breadcrumbs at the top of the page:
Robots → My Robots → Edit Robot
Error and confirmation messages
The following data table contains confirmation and error messages you may encounter while editing Robots.
Edit Robot details: Messages Action Status Message Save changes Robot deleted. The bot, <name of bot>, wasn't found.
It may have been renamed, moved, or deleted.
To continue, please contact your system administrator.Save changes Robot access revoked (on the folder). You no longer have permissions for the folder <folder name>.
To continue, please contact your system administrator.Save changes Unlock privilege removed. You no longer have permissions to unlock files.
To continue, please contact your system administrator.Save changes Lost "Set production" privilege. You no longer have permissions to edit the bot <bot name>
To continue, please contact your system administrator.Save changes Unlock failed due to Robot/File
not being locked anymore.<name of bot> is already unlocked.
This may be because someone else unlocked it,
someone else may have done an "undo check out",
or a new version may have been checked in.
To continue, please contact your system administrator.Save changes Edit failed due to system error. Unable to edit <name of bot> due to system error.
Please try again. If the problem persists, please contact
your system administrator.
Note: This can be shown for any unknown error that can occur
while committing the transaction (row was locked, etc.).Save changes Robot successful. <object name> Save changes VCS turned off. Version Control is turned off.
To continue, please contact your system administrator.
Export Robot details (Landing table)
- Audience & purpose
- As a Product user with the "Robot view details" permission, you want to export the Repository file details so that you can share them with others offline.
Exporting table contents
- Click the "Export" icon to export the table's contents.
- You will be given an option to upload "All" or any "Selected items" you choose from the table.
- Note: If you did not select any record, "Selected items" will be disabled.
- The system will export all/selected records (as per the above selection) from the right-side panel to a CSV (Comma Separated Values) file.
- The system will let the you save the file to your local file system.
Audit log entry
The Audit log will constructed with the following details.
- A Timestamp.
- The user id, user first name, and user last name.
- The Action performed.
- For example: "John Smith (jsmith) downloaded the details of folder xxxxx."
Impact of enabling/disabling of VCS on Robots feature
- Audience & purpose
- As an Automation Administrator, you want to configure Version Control for your Robots.
Description
You will be able to "Turn On" or "Turn Off" Version Control for a particular Product.
- When the system is moving Robots from Product to SVN, the Product repository will be read-only and locked.
- Updates to the repository will not be allowed.
- When the repository is "read only", the following operations will not be allowed:
- Upload
- Delete
- Set production version
- Checkout/check in
- Note: Turning off ("Turn Off") Version Control will not delete the entire Version Control Repository from SVN.
Scenario
- VCS was "ON"
- A Robot "b1.atmx" had three versions in the SVN repository.
- VCS was turned off on 1st March 2017 by the Admin.
- VCS was turned on again on 1st April 2017.
- Turn VCS off
- At the time of turning VCS off, the system will show a list of checked-out Robots and files, and ask the user to confirm the "force unlock" of these Robots.
- The "b1.atmx" Robot versions have been checked out by users.
- You must unlock these Robots to proceed.
- Click "OK" to unlock all Robots and disable VCS.
- Columns that appear in the pop-up message are:
- Serial Number
- Name of Robot
- Path of Robot
- Name of the user who checked out the Robot.
- Note: The user will not be allowed to turn VCS off if that user does not "force unlock" all of the "b1.atmx" Robot versions.
- Turn VCS on again
- Turning VCS on will allow usage of the old SVN repository which had the version history of the Robots.
- At the time of turning VCS on, the following scenarios are possible for the three "b1.atmx" Robot versions:
- Same: There will be no update in the SVN repository for the "b1.atmx" Robot versions. The system will not create a new version of b1.atmx.
- Updated: If "b1.atmx" was updated, the system will create a new version 4.0 of b1.atmx in SVN.
- Delete: If b1.atmx was deleted when the VCS was off, the system will also delete it from the SVN repository (soft delete).
- In this case, any user will be able to create a new Robot with name "b1.atmx" and be allowed to upload it to Product and SVN.
- The first upload of this newly created Robot with the name "b1.atmx" will be saved as the "1.0" version.
- New Robots: All Robots which were newly created will be sent to the SVN repository with the "1.0" version.
- If a Robot is already present in the SVN repository, the system will not create a new version of it if the Robot is unchanged (e.g., a case of error in movement of the Robot from Product to SVN and retrying by turning VCS on).
- If the user chooses to configure VCS with a new (empty) SVN repository, the system will show the following warning to the user:
Your VCS was configured with "<old_repo_name>" repository on the "<hostname>" system. If you configure VCS with the "<new_repo_name>" repository on the "<hostname>" system, you will not be able to access your Robots' version history through the Product product. Do you still want to continue? (Yes/No)
- If the user chooses to configure VCS with a new (non-empty) SVN repository, the system will show the following error message:
Your VCS was configured with "<old_repo_name>" repository on the "<hostname>" system. Please configure VCS with the "<old_repo_name>" repository or with a new SVN repository.
Mark password-protected files with a special icon on the "Folder Details" view
- Audience & purpose
-
As a Product user you want to identify all password protected files so that you can inform your team to remove those same files.
- Users can visually see the files (with the icon placed next to them) that are password-protected so that they can take appropriate action on them.
Marking the files
Directions
- Login to Product and go to the "Robots" page.
- On the "Robots" page, if a file is password-protected, the special red lock icon for that file is displayed.
Repository folders: Folders & files view
- Audience & purpose
- As a Product user, when you login to Product you will be able to view the details of all folders to which you have access so that you can mange these folders and the files in them. This enables you to View/Edit/Run/Delete the files as applicable.
Folder Details
Login to Product with access to "My Robots".
- Click "Robots" → "My Robots".
- A folder view will be displayed on the left side of the window. See the following screenshot.
- Click any particular folder to which you have access to display all the contents of that folder (files and subfolders), on the right side.
- The table header will display the count of items displayed. For example, "Files and Folders (12 of 12)".
- The following columns will be present as per the preceding screenshot.
- Name
- Type
- Size
- Last Modified
- Modified By
- For "Type", the appropriate icon will show when the file is locked.
- There will be a checkbox in the title row that will allow you to "Select All" and "Unselect All" entries in the table.
- There will be check boxes beside each record.
- You will be able to "sort" on any of the columns.
- You will be able to "filter" on any/all of the columns.
- The size will be shown in KB/MB/GB. For example, 999 KB, 999 MB, 10 GB, etc.
- Under "Actions" for each record will be:
- "View" icon for all.
- "Run" icon for TaskRobots if you as a logged-in user has the "Run"/"Schedule-add" privilege.
- "Delete" icon if you have the "Delete" privilege (set at the folder level).
- "Unlock" icon if a file is locked and you have the "Force Unlock" privilege.
- When there are no entries to show for a folder, an icon of the file type (from the Folder name) and text as described in the following data table will be shown.
File type Message Supporting files To see a supporting file in this list, you must upload it from a client application.
Once uploaded, it will automatically appear here.Meta Robot To see a Meta Robot in this list, you must upload it from a client application.
Once uploaded, it will automatically appear here.Task Robot To see a Task Robot in this list, you must upload it from a client application.
Once uploaded, it will automatically appear here.
Folder details with Version Control
- If Version Control is enabled, display the following two additional columns:
- Version control: This column will be displayed for all folders.
- Values = Locked, Unlocked, and N/A
- Production version: Production version is available for Task Robots and Meta Robots.
- For these files, if a Production version is not set, show it as None.
- For other files/folders show it as "N/A".
- If Production version is set, the values for the following attributes will be for that Production version. Otherwise, they display the values for the latest version:
- Size
- Last Modified
- Modified By
- The "Edit" icon will be displayed for Task Robot/Meta Robot folders (and their subfolders if any) if versioning is enabled and you have the "Set Production Version" privilege.
- The Production version column will not be displayed in "My Docs/My Exes/My Reports/My Scripts" and "My Workflow" folders though VCS is enabled. This behavior is similar to that in version 10.3.
- Any change in privileges/config (like VCS on/off) will immediately take effect.
- The following buttons if displayed, will be in this order:
- Run
- Unlock
- Edit
- View
- Delete
Refresh Folder
- The system should get the latest folder structure and contents of the current folder whenever there is a change.
- Important note: Due to technical limitations, we will not be doing this for version 11.0.
- Click the "Refresh" button to get the latest contents.
- Click the folder name on the left side to bring the new contents of that folder.
Breadcrumb trail
These breadcrumbs will be displayed at the top of the page: "Robots" → "My bots".
Repository folders: Tree view
- Audience & purpose
- As a Product user logging in to Product, you want to view the details of all and only the folders to which you have access and mange these folders and the files in them.
Tree View
You have access to "My Robots" and login to Product.
- Click "Robots" → "My Robots".
- A folder view will be displayed on the left side of the page. See the following screenshot.
- A message is displayed at the top of the table "To see Robots here, upload them from your Robot creator".
- You will only see Robots (and supporting files) that you have permission to see.
- There will be a Tree View and a list of all the folders to which the user has access.
- "Folders" are displayed on the table header.
- The following folder structure will be displayed by default on the left side of the page.
- My Docs
- My Exes
- My IQRobots (this will NOT be shown)
- My MetaRobots
- My Reports
- My Scripts
- My Tasks
- My Workflow
- The system only displays the folders that you have access to (you should have at least one of the privileges Upload/Download/Delete/Execute).
- A folder will not appear in the tree if the user does not have access to that folder (and any of its contents).
- Click the "node" to expand it and display any subfolders under it.
- Default folders cannot be deleted, so the "Trash can" icon will not appear next to them.
- Subfolders can be deleted.
- The "Trash Can" icon will be seen next to a subfolder if the you have delete access on that folder.
- Otherwise the Delete icon will not be shown.
- There will always be a selected item in the tree. By default, select the "My Tasks" folder.
- If you do not have access to "My Tasks" and any subfolders under it, select the first folder from the tree to which you have access.
- The "last selection over the session" will be remembered. You do not need to remember a selection across the sessions.
- If a full folder name cannot be displayed, truncate it and put ... (an ellipses) at the end.
- A tool tip "with full name" will be displayed for those folders.
Error messages
Action Reason Message Comment User clicks on a folder. Destination Folder no longer exists. Folder "xxx" does not exist. The user stays at the current folder. User clicks on a folder. Source and destination folders no longer exist. Folder "destination" does not exist. Take the user up in that branch,
or go to the next branch if the
source branch no longer exists.No access to any folder. Access to all folders deleted. You do not have access to any folder. This message will appear in the Tree view box. User clicks on a folder. User no longer has access to that folder. You no longer have access to Folder "xxx". User stays at the current folder.
Refresh a folder
Click the "Refresh" button to get the latest contents.
- On Refresh, the selection will be retained but all previously expanded nodes out of the selected path will be collapsed.
- If you do not have access to any folder, the following message will be displayed in the area:
You do not have access to any folder.
Repository folders: Tree view file count
- Audience & purpose
- As a Product user, when you login to Product you will be able to view the details of all folders you have access to so you can mange these folders and the files in them. This allows you to see how many files there are in the given folder.
Tree View with file count
- You have access to "My Robots" and login to Product.
- Click Robots → "My Robots".
- A folder view will be displayed on the left side.
- The count of items in that folder next to folder name (the count includes folders and files; a subfolder is counted as 1 item) is displayed.
- This count will match with the number of items that we display for that folder (on the right side).
- If you do not have access to a folder, then the files in that folder will not be included in the count.
- If you have access to a subfolder or any folders under that subfolder (at any level) then it will be added to the count.
Sample scenarios
- Scenario 1. You have access to "My Tasks" and all of its subfolders.
- My Tasks (4) (has access).
- → Task1
- → Task2
- → → SubFolder1 (Has access).
- → → SubFolder2 (No access).
- → → → Sub_SubFolder (No access).
- The file count for the "My Tasks" folder is "3" for you as a user.
- This will not include "SubFolder2" in the file count.
- "SubFolder2" will not appear in the Tree since you do not have access to that folder and any of its subfolders.
- Scenario 2. You have access to "My Tasks" and some of its subfolders.
- My Tasks (3) (has access).
- → Task1
- → Task2
- → → SubFolder1 (Has access).
- → → SubFolder2 (No access).
- → → → Sub_SubFolder (No access).
- The file count for the "My Tasks" folder is 3 for you as a user.
- This will not include "SubFolder2" in the file count.
- "SubFolder2" will not appear in the Tree since you not have access to that folder and any of its subfolders.
- Scenario 3. You have NO access to "My Tasks" but you do have access to some of its subfolders.
- My Tasks (2) (no access).
- → Task1
- → Task2
- → → Sub Folder1 (Has access).
- → → Sub Folder2 (No access).
- → → → Sub_Sub Folder (Has access.)
- The file count for the "My Tasks" folder is 1 for you as a user.
- This will not include Task1, Task2 and "Sub Folder2" in the count, since these items will not be shown on the right.
- The "My Tasks" folder appears in the Tree (even though you do not have access to it) because you have access to one of its subfolders.
- Scenario 4. You have NO access to "My Tasks" but you do have access to some of its subfolders.
- My Tasks (1) (No access)
- → Task1
- → Task2
- → → SubFolder1 (Has access).
- → → SubFolder2 (No access).
- → → → Sub_SubFolder (No access.)
- The file count for the "My Tasks" folder is 1 for you as a user.
- This will not include Task1, Task2 and "SubFolder2" in the count, since these items will not be shown on the right.
- The "My Tasks" folder appears in the Tree (even though you do not have access to it) because you have access to one of its subfolders.
- Scenario 5. You have NO access to "My Tasks" and any of its subfolders.
- "My Tasks" will not appear in the Tree.
Refreshing the Tree
The system will get the latest folder structure and the contents of the current folder whenever there is a change.
Repository folders: Tree View file search
- Audience & purpose
-
As a Product user, when you login to Product you will be able to view the details of all and only the folders that you have access to, so that you can mange these folders and the files in them.
- The Search functionality for both Client and Server will enable a simpler user experience.
Using Tree View
- You have access to "My Robots" and login to into Product.
- Click "Robots" → "My Robots".
- A folder view will be displayed on the left side of the page.
- You will be able to search for a folder in the Tree.
- As you type, the system will show the matching folder names as a drop-down list below the text box (similar to Google search).
Unlock a file in the repository
- Audience & purpose
-
As a Product user with the "Force Unlock" privilege, you want to unlock a file that was checked out so that other users can work on this file as required.
- For example, you want to unlock a file if the checked-out user is not available and someone else has to work on that file.
Forcing an unlock
Versioning Control is currently enabled on this Product.
- Login to Product and go to the "Robots" tab.
- You have the "Force Unlock" privilege to unlock any file that was checked out by any user.
- Go to a folder where you have the privilege to view its contents.
- Note: An Admin user by default has access to all files and folders with all privileges.
- The system displays the "Unlock" icon in that object row for the files that are currently checked out.
- Click the "Unlock" icon to "Force Unlock" it. The system displays the following confirmation message:
Reason Message Buttons (L to R) Confirm unlock Do you want to unlock the <object type> "<object name>"?
You cannot undo this action from inside the Product."No" = cancel
"Yes" = unlock- After closing the confirmation message, and if the unlock is successful, a toast message with "name of the file" and "Successfully unlocked" will be shown.
- The service will make sure you have the "Force unlock" privilege and that you should have the "Upload", "Download", "Delete", or "Execute" privilege on the Robot or the folder containing it.
- Note:
- If the unlock is Successful (the file is no longer locked), the page will be refreshed with the "Unlock" icon removed for that file.
- If the unlock is unsuccessful, the following error message will be displayed.
Unlock failed due to: 1. Privilege lost 2. File is not locked anymore 3. VCS is turned off 4. Other system error
- The confirmation/error message will show the respective user as username (firstname lastname)
Audit entry
Note:
- The system will log an Audit entry for the "Unlock" action:
Action - Force unlock bot/file Item name - <name of bot/file>
Unlock multiple files
- Audience & purpose
- As a Product user with the "Force Unlock" privilege, you want to unlock a file that was checked out so that other users can work on this file as required.
Using Force Unlock
Versioning Control is enabled on this Product.
- Login to Product and go to the "Robots" tab.
- You have the "Force Unlock" privilege to unlock any file that was checked out by any user.
- Go to a folder to which you have the privilege to view it contents.
- Note: An Admin user by default has access to all files and folders with all privileges.
- The system displays the "Unlock" icon at the table level.
- You select one or more files and click on the Unlock icon to "Force Unlock".
- The System displays the appropriate confirmation message. See the following message data table.
Reason Message Buttons (L to R) Confirm unlock Do you want to unlock the <object type> "<object name>"?
You cannot undo this action from inside the Product."No" = Cancel
"Yes" = Unlock- If you confirm to proceed, the system will try to unlock the selected files.
View file details
- Audience & purpose
- As a Product user, when you login to Product you want to view the details of any file/folder that you have access to in the repository.
Viewing details
You have access to "My Robots" and login to Product.
- Click "Robots" → "My Robots"
- The system displays all of the repository folders to which you have access.
- The Page title will be the <type of file> icon, and the <Name of file> (include the "Locked" icon, if relevant, when version control is on).
- The <file type> details group box will contain:
- Size
- Path = Default folder → subfolders, if any
- Production version (Displayed if version control is enabled. This will show "None" if you have not set one for Taskbots, Metabots, IQbots, and N/A if not relevant).
- Version control (Displayed if version control is enabled. Values = Locked, Unlocked).
- The "General details" group box will show:
- Last modified
- Modified by
- Robot/File type
- Object type
Robot/File type Object type Comment Task Robot, Meta Robot Robot Label will say "Robot type". Document, Executable, Report, Script, Workflow File Label will say "File type".
Working with top level actions
If the selected file is of type "Taskbot", and you have the "Run/Schedule" privilege, the "Run" icon will be displayed.
- Click the "Run" icon to take you to the "Create automation" wizard with the given Robot pre-selected.
- If you have "Unlock" privileges and the file is locked, the "Unlock" icon will be displayed.
- The "Edit" icon will be displayed if you have "Set production version" privileges and the file is TaskRobot or MetaRobot. Click this icon to go to the "Edit" page.
- Click the "Back" button to return to the previous page.
Breadcrumb details
The following breadcrumbs will be displayed at the top of the page: "Robots" → "My bots" → "View bot".
View folder details
- Audience & purpose
- As a Product user, when you login to Product you want to view the details of any file/folder that you have access to in the repository.
Viewing Details: Folder
- Login to Product with access to "My Robots".
- Click "Robots" → "My Robots".
- The system will display all of the repository folders to which you have access.
- Click any folder with a subfolder under it. For example, assume you have access to "SubFolder1" under the My Taskbots folder.
- Click the "View" icon of a subfolder to display the details of that folder. See the following screenshot.
- The following details will be displayed as per the screenshot:
- Size N/A (since it is a folder).
- Path (the relative path of this file from the default folder. For example, My Scripts → SubFolder1).
- A list of all files in the folder will be displayed with the following details:
- Type
- Name
- Size
- Last Modified
- Modified By
- The following details will be displayed under "General Details".
- Object Type = Folder
- Last Modified = Date last modified
- Modified By = User who last modified this folder (First Name, Last Name).
Breadcrumb details
The following breadcrumbs will be displayed at the top of the page: "Robots" → "My bots" → "View folder".
Click the "Back" button to return to the previous page.