In this section, we will go through the development of the Aged care application and will cover information about the Skyve platform and Skyve Foundry in detail.
This section also covers how to create and add different documents: Residents, Assessments, and Facilities in the Aged care application and how to deploy an application in Foundry.
Succinct statement of the purpose, key functions and general nature of Foundry, including (but not necessarily limited to):
- One-stop point-and-click tool for building apps
- Define all the data to be managed by your app, how it’s organised and how it’s related
- Deploy apps to a webserver so anyone can use them on the web
To create a new Skyve Project, we need to register our account first with following steps:
-
Go to the Skyve Foundry
-
Click on Register and Enter your account details
-
Active your Email address and if you are already register Sign in with your register email and password.
To create a new skyve project through Foundry go to the How to get started on the top right-hand side of skyve Foundry page and watch the video for more information about how to create new application.
In the Skyve Foundry, we can create and manage the browser-based applications. Skyve Foundry allows us to create numbers of application, and that each one will have a single record showing here on welcome screen.
Now, I will take you step by step creation of application:
Data driven design refers to how organisations use data to make their content more appealing to users by analysing their behaviour. In Skyve Foundry, we used different data designs such as modules, documents, and attributes to design an application.
Modules: In Skyve, modules define self-contained areas of functionality and have their own menu group. By default, Foundry apps start with a single module i.e Admin module. In the Design tab of your application, you can add or remove a module using the Add button.
Documents: In data design, documents are related to the real business entities (e.g.Residents, Facilities, Assessments). For more details about documents click on this link https://skyvers.github.io/skyve-dev-guide/concepts/
Attributes: Attributes contain information about each document (e.g. Resident's document attributes : name, id, photo, bio etc.). Attributes can have different data types and different view.
Data type: Data type specifies which type of value an attribute name hold.
-
Text or String: Used for a combination of any characters that appear on a keyboard, such as letters, numbers and symbols.
-
Memo: Memo data type also called "Long Text". It is used to store large amount of text.
-
Date: A Date includes the time, the year, the name of the day of the week, and the time zone.
-
Image: Image data type is used where we want to upload an image in our document.
-
Integer: It is used to store the numeric values.
-
Geomatry: It is used to map a three-dimensional object, such as a building.
-
Date/Time: The Date/Time type is used for values that contain both date and time parts.
- Association: This data type is used where there is a relationship between two entity object based on common attributes. An entity object only needs an association to access the data of another entity object.
The resident document will contain the personal information about the residents and the information about the facility they admitted.
Resident document contain attributes below:
Attribute name | Data Type | Length |
---|---|---|
ResidentID | Text | 100 |
Resident Name | Text | 500 |
Photo | Image | |
DOB | Date | |
Room Number | Integer | |
BIO | Memo | |
Admission Date | Date | |
Facility | Association |
The Facility
attribute will be an association to a Facility (held in the Facility data table). The association represents a link to the entire Facility record (including name, address etc). In a database this would be called a foreign key. In Skyve it is called an association, and in the Aged care application we are building - we will expect to see a drop-down list for this attribute so that the user can select the associated Facility record."
Now, we will create a Resident document and add attributes in Resident document in next few steps.
-
Click on Data Design to add the Documents
-
Add all information as shown below and click on Zoom out
-
You can see your document on screen.
-
Next, create documents for Facility and Assessment same as Resident and click on arrow to add attributes for each document
-
Click on Add button to add attributes to Resident document
-
Add all the attributes for Resident document as below
The Facility document will contain information about the facility(e.g.facility name, Facility manager, facility full address and location).
The attributes for Facility document as below:
Attribute name | Data Type | Length |
---|---|---|
Facility Name | Text | 500 |
Building Number | Integer | |
Street Name | Text | 500 |
Suburb | Text | 500 |
State | Text | 500 |
Facility manager | Association | |
Location | Geometry |
The Facility manager
attribute will be an association to a system user (held in the User data table). The association represents a link to the entire User record (including name, access levels, contact details etc). In a database this would be called a foreign key. In Skyve it is called an association, and in the Aged care application we are building - we will expect to see a drop-down list for this attribute so that the user can select the associated record for the system user who is the Facility manager."
This document will follow the same steps we followed for Resident document. It will look like as below:
The Assessment document will contain information about all the care assessments related to each resident.
The attributes for Assessments document as below:
Attribute name | Data Type | Length |
---|---|---|
Hygiene Assessment | Memo | |
Pain Assessment | Memo | |
Continence Assessment | Memo | |
Sleep Assessment | Text | 600 |
Behaviour Assessment | Memo | |
Assessment Created By | Association | |
Assessment Review Time | Date/Time |
The Assessment Created By
attribute will be an association to a system user (held in the User data table). The association represents a link to the entire User record (including name, access levels, contact details etc). In a database this would be called a foreign key. In Skyve it is called an association, and in the Aged care application we are building - we will expect to see a drop-down list for this attribute so that the user can select the associated record for the system user who is the Staff person.
In our attributes list, Sleep Assessment
does not need unlimited size, because it is a brief description of what state of sleep the resident is in at the time of the assessment, e.g. Awake, Asleep, Active, Resting etc.
Follow the same steps like Resident and Assessment documents. Assessment document look like as below.
Our Aged care application is almost ready, now the next step is to deploying our application to check how it look like. (Note: If you are using a free trail version, you can only deploy your application for an hours. To use the free version for another hour you need to redeploy it).
There are following steps to deploy Aged care application as we created in Foundry:
-
Go to Foundry and click on Aged care application
-
Click on Deloy tab and add User password and Confirm password then click on Deploy, usually it take 2 minutes to deploy your application
-
Next, click on the deploy link
-
Sign in with user "setup" and password which you initialised during deployment
Your application is ready to go. It contains two modules:Admin and Aged care. These two modules show as two menus in the application as shown below. The Admin module is the provided as part of the Skyve platform for all applications. It provides a range of powerful administration features, including:
- user and access management
- scheduled backups and restoring from backups
- ability to import and export data
- scheduled jobs and tasks
- comprehensive system user activity audit tracking, keeping records of every user interaction in the system.
In the Aged care module, you we see the a menu item for each of the three documents we created in the foundry. Let's see how it look like...
Click to expand the Aged menu.
You will notice two red lines- one at the top of the screen and one at the bottom of the screen. Generally organisations will run several instances of their application, for example, Production, Quality Assurance, Test/UAT and Development etc. For non-production instances, Skyve adds these labels so that the person using the system clearly understands whether they are working on a Production instance or not.
In this case, we are using the Foundry Free Trial
instance, so the two red indicators show. When you move to a production instance (either hosted on Foundry, or on your own infrastructure) these instance identifiers will not show.
Click on Facilities and then add button
Enter the detail of facility in the fields and click on "Ok" or "Save" button.
Ok button: This button performs Save and Close action on clicked. This will save the changes and return you in previous page.
Save button: This button will save any changes you perform in the current page when you click on it.
So, press Ok or Save as you go.
Next, click on Residents and add button
Then, click on Assessments
Add data in Assessments
Skyve provides two separate user interface: Normal mode and power user mode. In normal mode, the interface is responsive and mobile and tablet friendly where as the power user mode is great for desktop browsers.
To switch between interface click on the switch icon on the top-right of the application screen.
After switching
The Foundry free trial server will automatically undeploy your project after one hour - but you can redeploy your application as many times as you need during your testing and your data is saved while the project is offline.
- Can I make changes to my app after I’ve deployed it?
- I deployed my app – why did it stop working ?
- How do I re-deploy my app ?
- I’ve got what I came for. Can I build my own app now ?