this Section’s purpose is to take you through the process of building a simple App in Wizzdi Cloud.

the example is available on wizzdi cloud public marketplace

Register

Before Using Wizzdi Cloud You must register.

Email/Password Registration

1. press the Sign Up highlighted text
2. input the details above
3. Press the Sign Up button

Single Sign On Register/Login

press the Google Icon or the GitHub Icon , to SSO with Google/GitHub.

Create App

press the New App button on the bottom right of the screen.

insert your App’s name.

App Overview

Domain Model

in this part we will create a simple Person Entity with the fields: id,address,birthDate.

the Domain Model Editor is a powerful tool that allows creating connection between entities ,setting indexes , creating inheritance relshionship and much more.

for a more extensive view of the Domain Model Editor check its documentation.

Create The ‘Person’ Entity

1. on the right side menu select the New… button and select New Entity
2. a new rectangle will show on the editor , enter the Entity name – ‘Person’ and press OK

Add The ‘id’ Field

1. select the ‘Person’ Entity
2. press the Add Field button
3. insert name ‘id’
4. press Enter in the keyboard or the green checkmark

Add The ‘Address’ Field

1. select the ‘Person’ Entity
2. press the Add Field button
3. insert name ‘address’
4. press Enter in the keyboard or the green checkmark

Add The ‘birthDate’ Field

1. select the ‘Person’ Entity
2. press the Add Field button
3. insert name ‘birthDate’
4. press Enter in the keyboard or the green checkmark
5. select the ‘birthDate’ field
6. on the right side drawer select the type (currently ‘String’)
7. in the drop down select ‘OffsteDateTime’

Exposed APIs

In this section we can see the automatically CRUD (create, read, update and Delete) APIs.

more options available here such as adding a new custom endpoint , defining if the project is a contract-first of domain-first and much more.

check the Exposed API Documentation for an extensive view of it.

Git

In Wizzdi Cloud Users allways own the code they generate from the platform . to deploy the app we must first commit it to a GIT repository.

Setup Remote

lets setup the remote git repository that the platform should push code to.

you should select one of the two options bellow

Automatic Connection With Github

we will do this by connecting with github in one click

1. press the SETUP REMOTES button
2. on the right side drawer press the pencil button
3. press the Connect With GitHub button
4. in GitHub screen press the Install & Authorize button
5. press the OK button

Setup Remote (Manual)

lets setup the remote git repository that the platform should push code to.

we will do this by providing the GIT credentials to connect to the target git repository.

1. press the SETUP REMOTES button
2. on the right side drawer press the pencil button
3. press the Manual Connection button
4. insert the Name  which will be the name of the remote in wizzdi cloud
5. insert the Username which will be used to connect to the git repository
6. insert the Password which will be used to connect to the git repository
7. insert the URL of the git repository
8. press the OK button

NOTE: some GIT providers such as bitbucket and GitHub do not allow using normal username/password credentials

and App Passwords / developer tokens should be used per the provider documentation.

Commit

now that we have setup the remote git repository for the application , lets commit the code .

wizzdi cloud will generate compile and commit it to the git repository setup above.

1. press the Commit button
2. insert a commit message , for example : “Init”
3. press the Commit button

you should now see the progress for generate compile and commit.

Review The Code

now the code should be available , this example code can be found here.

Deploy

lets deploy our application into Wizzdi Cloud secure scalable Cloud.

in the overview screen press the install button , press the OK button in the next dialog.

a progress screen for the app deployment will be opened.

when it is successfully done we will see this screen:

Run

now that the app is deployed we can check the app’s Overview section there we will see the server’s URL as well as the swagger URL which allows us to try APIS

we can now press the copy button next to App Url or next to the Swagger Url to get the api root or the swagger UI.

The post Quickstart first appeared on wizzdi.

this Section’s purpose is to take you through the process of building a book store management app.

the example is available on wizzdi cloud public marketplace

App Overview

Domain Model

in this part we will create the domain model to describe the normal data that is handled in a typical book store: Book,Author,BookLend,Genre,Subscription,Person

the Domain Model Editor is a powerful tool that allows creating connection between entities ,setting indexes , creating inheritance relationship and much more.

for a more extensive view of the Domain Model Editor check its documentation.

The Person Entity

The Person Entity will be used as a Mapped Super Class for the Customer and the Author Entities , a Mapped Super Class is kind of a Mold for Other Entities , this allows us to have the name ,id , birthDate of Person in the Author and Customer Entities.

The Author Entity

The Author Entity defines an author , it is connected with the book entity in a many-to-one relationship since Author has Many Books and in our example Book may have only single author.

if we did wanted to support multiple authors for a book we would need an intermediate entity called BookToAuthor which will define a many-to-many relationship between book and author

The Genre Enum

the Genre Enum is a list of predefined values that will represent the possible Genres we support in our Book Store. we may add more to the list . for more flexibility we should have defined this as an Entity.

The BookLend Entity

The BookLend Entity will be used to represent the fact that a Book was taken by a Customer , this will have the date it was taken as well as the date it should be returned and the date of actual return.

Exposed APIs

In this section we can see the automatically CRUD (create, read, update and Delete) APIs.

more options available here such as adding a new custom endpoint , defining if the project is a contract-first of domain-first and much more.

check the Exposed API Documentation for an extensive view of it.

Review

Review The Code

now the code is available, this example code can be found here.

Review The App’s API Docs

the swagger docs for the app is available here.

The post Book Store first appeared on wizzdi.

this Section’s purpose is to take you through the process of building a Pizza Delivery App.

the backend will serve multiple clients:

1. the management – used by management
   1. managing branches
   2. managing toppings
2. the user app – used by customer to order pizza
   1. allows creating a new order
   2. adding multiple pizzas
   3. adding toppings for a pizza
   4. pay via PayPal
   5. track delivery location live using WebSocket
3. the delivery app – used by delivery to report location
   1. push GPS location

the example is available on wizzdi cloud public marketplace

App Overview

Domain Model

in this part we will create the domain model to describe the normal data that is handled in a typical Pizza Restaurant: Basic,SecuredBasic,Branch,Topping,PizzaOrder,OrderStatus,Pizza,PizzaToTopping

the Domain Model Editor is a powerful tool that allows creating connection between entities ,setting indexes , creating inheritance relationship and much more.

for a more extensive view of the Domain Model Editor check its documentation.

The Basic Entity

The Basic Entity will be used as a Mapped Super Class for all other Entities , a Mapped Super Class is kind of a Mold for SecuredBasic, Branch and  Topping, this allows us to have the name ,id , creationDate, updateDate of Basic in all the other Entities.

The SecuredBasic Entity

The SecuredBasic Entity will be used as a Mapped Super Class for all other Entities  , this allows us to have the all the fields of Basic Entity as well as the creator field which will hold the creator of the things the customers create , this will automatically filter the data so users only see their own data (except admin users).

The Branch Entity

The Branch Entity defines a Branch of our Pizza Restaurant chain, a pizza order will be made at a specific branch

The Topping Entity

The Topping Entity defines the possible toppings our Pizza Restaurant chain provides and their price.

The PizzaOrder Entity

The PizzaOrder Entity will be used to represent a new Pizza Order

The OrderStatus Enum

the OrderStatus Enum is a list of predefined values that will represent the possible Status values a Pizza Order Goes through

The Pizza Entity

The Pizza Entity will be used to represent a Pizza in a Pizza Order , we can have many pizzas in a single pizza order

The PizzaToTopping Entity

The PizzaToTopping Entity will be used to represent a Topping on a Pizza , the user will be able to select the toppingCoverage , a pizza may have many toppings.

Exposed APIs

In this section we can see the automatically CRUD (create, read, update and Delete) APIs.

more options available here such as adding a new custom endpoint , defining if the project is a contract-first of domain-first and much more.

check the Exposed API Documentation for an extensive view of it.

Custom APIs

we have added three APIs in addition to the automatically created CRUD apis;

1. getPizzaOrerSummary – given a PizzaOrder id will return a summary of the order , we will use this to display a summary of the order before paying , it is connected to the OrderSummayFlow(more on flows later)
2. prepareCheckout – given a pizza order id we will start the checkout process with PayPal , it is connected to the PrepareCheckoutFlow
3. completeOrder – this will be called by PayPal when the order is paid for , providing a PayPal order id we will mark the order as paid and change the PizzaOrder Status , it is connected to the CheckoutValidationWebhookFlow

Flows

business flows are used to express a custom business logic connected to custom APIs  or other type of triggers (schedule ,event and more) ,

check the Flows Documentation for an extensive view of it.

OrderSummaryFlow

the order summary flow is using a Method Definition activity which is written in Java

PrepareCheckoutFlow

the PrepareCheckoutFlow will be called when the user tries to pay for an Order , it :

1. fetches the order based on the incoming id
2. gets the order summary by calling the getSummary method definition (which calls the logic from OrderSummaryFlow)
3. if a PayPal order id is not set on this order
4. calls PayPal api with the total that should be paid and the order id
5. takes PayPal order id from the response and sets it on the order
6. returns the order

CheckoutValidationWebhookFlow

the CheckoutValidationWebhookFlow will be called by PayPal (the url of this API should be set as a webhook in PayPal) when the user successfully paid for an Order , it :

1. calls the PayPal api to verify the webhook call ( this prevents anyone from simply calling this webhook and impersonate payapl)
2. if it was not validated – return failure
3. fetches the order
4. updates the order status to STARTED
5. return success

UpdatePizzaOrderFlow

the UpdatePizzaOrderFlow will be trigger when a PizzaOrder is updated (it is triggered by an event), it will push update message of the order status to WebSocket (more on Websocket integration later), this will allow us to update the customer without constantly calling an api to refresh the data , it :

1. fetches all the websocket sessions that listen to the changed pizza order id
2. creates an update message that will be sent to all of them
3. for every session it sends the message

Integrations

Integrations allow adding additional services to our deployed app , it also adds relevant integration code to the app and adds additional activities to the activities toolbar .

check the Integration Documentation for an extensive view of it.

in this application we will be using only one integration – the websocket integration.

Web Socket Integration

we are using the websocket integration in our UpdatePizzaOrderFlow, here we define the url of the websocket endpoint (we can have multiple endpoints) , and the message structure that will be used in our websocket endpoint.

Security

since we have multiple users for our backend it is important that we allow each user to execute only the actions it allowed to do.

additionally we also like to support SSO login and registration.

SSO Login

in the sso login area we can define support for sso login /registration , wizzdi cloud support many of the known providers as well as the option to add a custom provider.

check the SSO Login Documentation for an extensive view of it.

Permissions

in the permissions area we set which roles are allowed to which permissions (this can be done from this screen or from the exposed apis screen by pressing the lock icon next to the api endpoint).

since Branch and Toppings should not be added by normal app users we will allow only admin to manage them.

check the Permissions Documentation for an extensive view of it.

Properties

finally we need to set some properties to make PayPal SSO Clients work :

1. SSO Clients details , this will require PayPal client and secret
2. SSO Clients scope – https://api.paypal.com/v1/payments/.*
3. SSO Clients token URI – https://api-m.sandbox.paypal.com/v1/oauth2/token
4. SSO Clients authorization URI – https://api-m.sandbox.paypal.com/signin/authorize

Review

Review The Code.

now the code is available , this example code can be found here.

Review The App’s API Docs

The swagger docs for the app is available here.

The post Pizza Delivery App first appeared on wizzdi.