Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »


Starter

Overview

On the first part of this document, we will explain how to start on Wayfast platform by creating a new Container (Solution) where the users can gather the different Projects and associate Databases to start any application in Wayfast account. This container will give you the ability to organize and save your work. In few words, you can build your platform -develop, run and manage Web and mobile applications- establishing the structure in simple steps.

How to create Solutions?

Solution Definition: TBD

Once the user has access to Wayfast, you can go to “My Solutions” section and clicks on “+ Solution” button.

A popup is displayed to create the container. First of all, user needs to complete the Name and Target fields before clicks “Accept” to continue. This container will organize the new applications created and you can easily view all your solutions in the Dashboard.

A Portfolio icon will provide the # of Projects allocate on each Solution created. Since this is a new container, the container is showing zero values. User can navigate through the “Solution Name” to access into the Solution details form.

How to create Projects?

Project Definition: TBD

Now that we have the main structure created, user can click on “Project” button and build the first element to initiate an Application.

A popup is displayed to select the main settings for your new application. It’s important to analyze which type of project fits better to your application objectives. There are 3 options available “Workflow”, “Application” and “Source Code”. Also the users need to select which Login Type is needed, Wayfast offers “SSO”, “User and Pass” and “Anonymous” options.

Type of Project Definition: Workflow / Application / Source Code

Login Type Definition: SSO / User and Pass / Anonymous

This is an important milestone on new project because it will define the whole structure for your applications. Once it’s created, user can’t edit the definitions previously selected[s1] .

Immediately after user clicks on “Accept” button, the “Select Skin” popup will offer different templates to apply in your application’s interface.

Dashboard will provide the main information regarding the status of your “Requirements”, Size of your code and database and finally the “Runs” information.  

How to associate our Database now that the Project is created?

 

Instance Definition: TBD

Database Definition: TBD

Now that we have the Portfolio container (Solution) generated and the Project set it up, we can start working on the Application by defining the Requirements. But first, we need to associate our Database (DB) to the Project. Otherwise this Requirements won’t have any relationship with the Application to build.

Turn into Dashboard, user clicks on “Project Size” section and selects “Database” icon on top header menu

On Submenu, selects “Instances” and then clicks “Associating Instances” to setup the new DEV Environment for the Application DB.

Wayfast automatically shows the different instances (Environments) that can be associated to our DB in next step. This selection should be repeated each time that you want to link instances.

On Submenu, click again “Database” section. User can create a new Database by choosing the Instance previously selected. This option will be prompted automatically on the Instance dropdown.

Also user can choose by adding a previously created DB using the “Attach DB” button.

Now we have the DB associated to the Project and user can continue defining the Requirements.

How to Create Requirements?

Requirements Definition: TBD

User can create this entity by clicking on “Requirements” icon at the top header. Automatically user will see the “New” button to start a New Requirement. This action is very important because it will the first object to interact with our newly DB.   

 A popup is displayed and User can choose on “Select the Type” dropdown the option “Requirement” to establish the association. 

User needs to complete the Request on Text Editor with the corresponding information to describe what is the purpose related to the Requirement. Also Wayfast brings the following options to be more accurate on the creation:

-Assignment Type: TBD

-Meetings: TBD

-Sprint: User can define the iterations to build the Project, normally a requirement is associated to a specific sprint to complete a set amount of work.
-Size: A requirement can be sized depending on the effort by Hours. User can choose between XS (1hs), S (2hs), M (4hs), L (8hs), XL (10h) and XXL (23hs).

-Developer: By default, it should populate the user who creates the Requirement.

-Criticality:  Users can set this option depending on the criteria defined by the team. A critical requirement is one that the system must achieve or the system cannot function at all.

-Upload: TBD

NOTE: None of this options are mandatory, however, they are recommended to generate a proper alignments for the each Requirement into the Project.

After creation, the Requirement will be grouped as “Pending Tasks” at the vertical Navigation bar. User can check the checkbox beside the Requirement to turn this on and moved them into “Active Tasks”. Also the user can see the Requirement generated into the Dashboard with

How to Create Page?

Page Definition:

If the user navigates under the Requirements, Wayfast offers the possibility to generate multiple Pages. But first, we need to define which Layout are going to be our default to create pages.

Clicks on “General Options” at the top header. Then clicks on “Layout” subsection to verify if there’s anyone defined into the Project. We can choose by “Associate Layout” if we select a predefined component. Selected layout will give us a default distribution of Controls under each page that we are going to create. Also Wayfast has the ability to create “New Layouts” defined by the users.

For example, we can use a “Simple” layout for normal pages and “Popup” for prompted windows in our Project. 

NOTE: User can select multiple Layouts, this selection will be the options available every time that create new pages.

Turn to “Project Pages” icon on the top header to finally create a new page from the scratch.

Click “New Page” and popup will be prompted on screen. There are 2 tabs: “General” tab to define the page name, type and the option to make this page as Home page by checking the “Is initial page” checkbox; “Layout” tab that will bring the options previously selected in General Options >Layouts to define which kind of distribution will contain the new page.

Once the user clicks “Accept” button, the page is loaded on Dashboard.

How to Add Control?

Control Definition: TBD

Now that we defined the Page under the Requirement, Wayfast give us the chance to establish a set of Controls under the page generated.

Navigate through the page by clicking on Page Details (link on page name) and expand the “Controls” subsection. Dropdown at the left side will display all the controls that Wayfast contains by default.

NOTE: Wayfast also brings the possibility to import controls.

After selecting any of the controls available (e.g. Label), the “New” button will be displayed beside the dropdown. If the user clicks on “New”, a popup will be displayed to select the multiple settings for this control.   

There are different tabs inside the Control popup, “General” tab will define the control name and the type of control. On “Layout” tab, we can set the location for the control inside the Page using the “Placeholder” dropdown field. Also it’s mandatory to fix an order inside the container page.

After clicking on “Accept” button, we can observe the new control associated to our page. At the top right corner, if the user clicks on “Preview” button, Wayfast will open a new tab that shows the  preliminary view of the page with the newly control created.

To complement different controls under the page, we can set a “Checkbox” control before the “Label” previously created in order to make this text visible or not.

Once we have the 2 controls created, we can now put a conditional input variable in the “Label” control who will depend in the “Checkbox”. It’s important to modify the “Order” field to primary view the checkbox and then the label.   

In this case, we will only display the “Hola Mundo” text when the control check is true on page.

NOTE: You can find more details about Controls on the specific documentation for this functionality.  

Recap

In the first part, we learnt about how to create a Solution and how they can contain Projects. We defined the structure by associating the Project with a Database. In the second part, we created Requirements that can be linked to multiple pages, and finally we navigated briefly through the Controls that we can insert and manage according to our application needs. This first approach to Wayfast definitely helped us to get a more familiar with the tool, now we can go through in depth all the features and functionality of the system.

 


 [s1]Please review if this is correct, there’s no clarification on video

 [s2]We can link this NOTE to the Controls doc

  • No labels