Prevent the screen from locking until the scenario is executed

Features

Prevent the screen from locking until the scenario is executed.

At the specified time, execute the main scenario (another scenario) with "GoToScenario.ums6".

• For the process to be executed after waiting, open another scenario with "GoToScenario.ums6" or place the node directly in this sample scenario.
• For the stadby type, choose a type that does not affect the scenario to be executed from either "Mouse drag" or "Sending texts".

WinActor Modules to use

In this sample scenario, the following WinActor modules are used.

• Node\Action\Wait_for_specified_period
• 01_WinActor_Control*/02_ScenarioControl/GoToScenario.ums6
• 02_ErrorHandling/ErrorHandling_RaiseError.ums6
• 12_Mouse/Mouse_Drag.ums6
• 14_InputBox/InputBox_EmulateInputText.ums6

* WinActor 6.1 : 01_OR-5200_Control

Operating Environment

The operation of this sample scenario was confirmed in the following environment.

• Windows 10
• OR-5200 6.1.0、WinActor 7.1.1

How to use

Step 1. Preparation

Create a scenario to be executed after waiting,

Step 2.Open the sample scenario

Extract the downloaded ZIP file and open this sample scenario contained in the extracted folder.
*If there is a required process before the standby process, add the process to the Pretreatment group.

Step 3. Setting and checking variables required for operation

The following three variables need to be set in advance.

• 1.Specified time
  • Specify the time you want to end the wait.
    For further details, please refer to "6.4.4.3 Format for specifying time" in WinActor(OR-5200) operation manual.
    E.g.) 2020/01/01 10:00-2020/01/01 10:01
• 2.Standby type

  • Specify the standby type.
    Specify the standby type that does not affect the process of the main scenario.
    

    Value	Standby type
    1	Mouse drag
    2	Sending texts

• 3.Main scenario path
  • Specify the path of the scenario file for main process as an absolute path or a relative path from this scenario file.
    E.g.)
    Absolute path: C:\winactor\main.ums6
    Relative path: main.ums6

Step 4.Executing the scenario

Execute this sample scenario with WinActor.
According to the specified standby type until the specified time, the standby operation is performed every 50 seconds, and when the specified time comes, the specified main scenario is executed.

Step 5.Confirming the status of the executed scenario

Please confirm the status of the executed scenario

Trouble shooting

In this sample scenario, an error message will be displayed if a variable is specified incorrectly.
See the error message list for more information.

Error messages	Details
Please input the format of time destination.	The SpecifiedTime in the variable list is invalid. Please refer to the operation manual of WinActor.
Failed to run the script Error numer:1 Details: Specify 1 or 2 as the StabyType	StandbyType in the variable list is invalid. Specify 1 or 2 as the StabyType.
Failed to run the script Error numer:1 Details: Library execution (spv_ScebarioGoto) failed.	The target file specified in the MainScenarioPath in the variable list does not exist or cannot be opened. Check the value of the MainScenarioPath and the specified file.
Failed to load the scenario file.	The target file specified for the MainScenarioPath in the variable list is not a scenario file. Check the value of the MainScenarioPath and the specified file.

Description

This section describes the implementation technique used in this sample scenario and an extension example of this sample scenario.

Waiting until the specified date and time

In this sample scenario, two standby types are available.
It is assumed that each standby type is used properly as follows.

• Mouse drag
  Moving the mouse to the right for each wait process with using "Mouse_Drag.ums6"
  It is recommended to use it when there is no mouse operation in the main scenario.

• Sending texts
  Sending "a" for each wait process with using "InputBox_EmulateInputText.ums6"
  It is recommended to use it when there is no operation such as text input in the main scenario.

Call Main process

Calling an external scenario as the main scenario with using "GoToScenario.ums6", it is possible to execute the schedule without editing the created scenario.
* If it is a short process, it is possible to execute the schedule only in this sample scenario by deleting the GoToScenario node of the main process group and creating the process directly.

Track changes

Version	Date	Details
1.0	10/08/2020	First edition