This section explains how to submit project requirements for approval.

SmartSpec à Capture Requirement à Version History

Once deployed, the robot (workflow) can be rolled back by choosing the previous version. Explanation follows.

Reviewing the status of submitted requirement is explained in this section.

The created requirement will be available in the Under-Approval Queue. It reflects all pertaining information such as the Name of the Tenant and Project, Created By, Modified By, Modified Date, Status, Approval Status and Completion Percentage. 

How to disconnect machines from programs? Explanation follows.

Figure 1

Robots that have been created or added in SmartManager would be developed in the SmartDesigner. While saving, this robot will be committed to UAT. The committed robots will be available in the Move to UAT. From move to UAT, if it passes UAT testing, it will go to In UAT.  From there, it will move to In Live-ready for Production environment. 

Use the Administration menu --> Create role option to add a new role for platform users.

This section explains how to capture project requirements, which is the first step in the Requirement Management process.

This section explains how to capture a process flow in Requirement Management and is the third step in capturing requirements.

Process Capture comprises Tools, Process Map, Requirements, and Appendices.

The transaction in the Interact can be moved from one queue to another queue using the Transaction Backpush sub-menu.

Figure 1 

The unique key is required to  install the SmartDesigner, SmartRunner and the Desktop Runner in the Virtual Machine or in a clientÔÇÖs machine.