Testing and executing projects

The execution environment provides access to all project execution resources.

Execution Tool Space

Build—should be used to request the preparation of the Project for real-time execution and the rescue of the project's history, including compilations and Builds from Scripts in executable code libraries. 

Test—allows you to verify a project and its execution in real time before publishing it for use on the actual Server.

 Startup—allows you to specify diagnostic tools and modules to be used to test applications and Scripts in project executions.

 Publish—this is where you publish the project to get the final installation file on the server. A new project review identifier is obtained.

UseCount—presents a summary of the project as the number of Tags Used. It also provides a cross-reference report of project objects.

Localization—enables the customization of the language to be used in alarm messages and text from project screens.

Extensions—imports configuration data already created for OPC Servers, any configuration tables in CSV format - or even a complete project. It also works to configure the use of external applications (Models) by sharing data in real time.

 Building

Build serves to recompile all project screens and script objects for final verification of possible errors before project placement into production.

Image RemovedImage Added

A thorough scan of the application logic is performed while preparing the files for the final production version. This operation is not required during project development, as all modifications are automatically and transparently compiled into background while edits are made.

Testing the project

This function makes it possible to run the project in Test mode, which means enabling the protections that allow execution, even on the same machine that the project is running in the actual start. Historian and Alarm recording functions are directed to use temporary files instead of those defined in the final project database in production.

Test

As an option, diagnostic tools can be enabled to help solve some problems that may be present in the construction of the project. You can choose to disable any of the modules during testing.

Project Startup

This area allows you to set up how the project will run in final production mode. It means enabling historian and alarm recording functions to use the actual databases defined in the project rather than temporary files used in test mode.

You can optionally enable diagnostic tools to assist in solving any problems that may be occurring in the project. You can choose to disable any of the modules during testing. The check-box "Online Setup" when checked, indicates that the possibility of changing settings during project execution should be accepted. Thus, when running, if changes are made to the project parameters, they are effective and incorporated into the project while executing.

 Publishing the Project

The Publish function creates a version for the read-only project on an appropriate file to be installed on the final production machines.

When the Publish command is executed, a new project file (with the .teng) is created, using for version number what is specified in the corresponding field of this area, shown below.

Published projects (files with the extension "Tproj") are in all similar to current projects under development (extension "proj") but can only be opened in protected mode (read-only). This feature allows you to have a secure version of published applications that can be left as backup in the final installation itself.

Information and Version Control

The Information environment provides access to current project configuration details.

Image RemovedImage Added

Projectt—shows product and project versions, project location, language used, and various other details.

Track—for information on project publications, version numbers and change history.

Notes—to fill out important notes and notes for other users who are developing the project.

Help—to call the online reference aid of the Action.NET.

license—shows information specific to the current licensing of the product. A Registry tab makes it easy to register the software online.

Checking information about the Project

The Action.NET itself helps in obtaining and keeping information about the project.

While managing project versions are developing, installing, commissioning, or maintaining a project, it is important to be aware of the version of the software being used, license details, project details, and other configuration information.

The Project desktop components tab provides this information and allows you to change it if necessary. Some of these attributes are also available in real time if needed.

Tracking project changes

A very important feature available in Action.NET is the ability to keep track of any changes made to the project. Traceability assists in verifying project configurations at various stages of its development and implementation. This is important because you often need to be able to check which version of the project is used when developing improvements and working with diagnostics.

Or Action.NET tracks changes from all configuration parts of the project.

The tab Tables (Tables) shows a list of all the project tables that have had some field changed, with the line indication that has changed With a double click on the line whether it goes to the editor (datagrid, or code or screen editor) that generated the change.

The tab Changes (Changes) provides information about the specific module in which the changes occurred, the specific change that was made, the specific Build operation in which the change occurred, as well as the date of the change, and any comments made by the user.

The tab Releases provides information about the date when the project was published, who published it, and the number of the last Build on which the project was published.

Adding and sharing project annotations

Often, during the development and implementation of a project, developers need to be able to leave notes for themselves or others who are collaborating on the project, in order to mainly document the actions and reasons for decisions made. However Action.NET, this can be done by using the Notes utility available in the software.

 Annotations created are of the "post-it" type and are visible to all members of the project development team. The Notes are visible on the desktop when editing the project.

Image Removed

Image Added

Help

The Action.NET includes a Reference guide (online assistance) to explain development tools. Use the index to search for keywords online.

The question mark in the upper-right corner of the Configurator also calls the same online help.

When you click on this icon, the Contents, in which the currently configured help appears and fields for setting up the desired online helpform: CHM help file or a website. Here too, you can configure which of these means to use when you press the blue button with the question mark at the top of the Engineering Workspace.

 Licensing Information

The Licensing tab displays information about the license currently installed for the Action.NET. This information will be of great use if it is necessary to contact the technical support area of Spin Engenharia and when it is time to upgrade to a newer version of the software.

See more at Versions and Licenses Action.NET.