...
...
...
...
...
Overview
In this lesson, we are going to explore Wayfast IDE’s interface and its main sections so we can have a smooth experience across this training.
| Info |
|---|
What’s an IDE? You can find more details on this link. |
Key Areas
We can identify 4 main sections during the Wayfast navigation experience:
Top Menu |  | All the sections provided by Wayfast can be accessible from this header. |
|---|---|---|
Body Main Screen |  | Each section will display the details on the body screen. We can find a drill down path in case we want to go back or forward in the project. |
To-Do List |  | As precondition to develop any Project in Wayfast, we need to create and activate requirements. Requirements will be automatically displayed in the To-Do list at the left side of the screen. As Wayfast Users, we can end tasks to execute a deployment or start new tasks to continue working on development. |
User InfoTop right panel |  | This section will display the details about Wayfast user and platform level menu. |
Now that we identify the main sections, let’s review each of the Top Header items. This will be a brief analysis since we will go deep on each of them in the following lessons.
...
Sections | Sub Menu | Description |
|---|---|---|
General Options  | This panel will help us to change any aspect that we selected in our first setup and now that we are in a process of learning the application, we want to renew | |
“Layout” section displays the different templates set by default in our initial “New Project” steps. It offers the possibility to remove or associate new layouts to the Project. | ||
This feature allow us to group different linked items that serve in navigating between the different pages or sections we have created in the project. | ||
This feature is connected to the project execution functionality where we can manage the deployments at customer level. |
...
Sections | Sub Menu | Description |
|---|---|---|
 | This section will manage the different instances as different work environments. We can handle requests to work with the data in any of the databases managed by that instance. | |
We can create or associate existent databases in our project and the relation with the different Instances depending on the environment that we are going to develop the application. | ||
User friendly visual tool to edit our database. | ||
This section will manage existent Tables in our databases and synchronize new ones from the SQL Server Management. | ||
Views are like a virtual table that contains data from one or multiple tables. This section will manage the different views associate them to the database. | ||
This section will manage the Stored Procedures created in database that are going to be used in the functions like Actions, Dataset and Controls. | ||
This section will display all the functions created from our database and also we can edit function’s statements or synchronize them between Wayfast and SQL. | ||
Here we can setup a simply scheduled program for each of the jobs connected to our database. | ||
In cases where database process where very large tables are divided into multiple smaller parts, we can manage this partitions on this section to reduce the overall response time to read and load data for particular SQL operations. | ||
This section will track automatically all the objects associated to out project’s database. | ||
Synchronize DB | Allows to updated Wayfast’s database model so it reflects database most up-to-date state. |
...
Sections | Sub Menu | Description |
|---|---|---|
Connectors  | In Wayfast we can include any kind of method to be developed in our projects. | |
Lists the Project’s APIs exposed by Wayfast. | ||
PDF Templates for exporting to PDF. |
...
Sections | Sub Menu | Description |
|---|---|---|
| This section is meant to continue application’s lifecycle after development. | |
Project Release | This section will track the release plan during the execution. | |
This section will help developers to identify which version of the application can be deployed to any of the instance where it needs as part of the development process. | ||
This section will bring a detailed extract to analyze the code structure and define new actions to take and also an easy way to audit what are the strengths and weakness of our code. |
...
Sections | Sub Menu | Description |
|---|---|---|
 | Unused Elements
| We can find a code quality tool that identify different elements like Pages, Controls, Datasets and more that are not being used inside the application. . |
Ondemand Elements | We recommend avoiding “On demand” execution type on pages, this is a tool where we can modify those elements and select the “Pre” execution to make the application more efficient. | |
Stats | This is a dashboard page where we can view different statistics associated to the unused and on demand elements available in the project. | |
Conditional by Customer | This is a report page that display all those elements that were created using conditional option. |