Introducing the example “Online custom tee design” application
The gadget spec URL could not be found

Our approach to learning OrangeScape is by using it!

OrangeScape is ideal for building process-oriented business applications (example: leave management system). The distinguishable characteristic of a process-oriented application is its movement over time from state to state, or put differently, its progression from activity to activity to an ultimate goal. In OrangeScape, the process is implemented in a visual modeling environment by creating workflows, which is the closest/similar representation of a process. Hence, process-oriented applications can be easily built using OrangeScape. That said, OrangeScape can also be used for building social applications (example: twitter) i.e. applications where any sense of process is extremely short-lived or inessential and the focus is on providing an engaging user experience.

Building an application using OrangeScape can be straightforward and easy once you understand the fundamentals behind its design pattern. To help explain these concepts and learn about OrangeScape, we will be developing an example application “Online Custom Tee Design”.

  Before you read any further . . . Identifying example application functional requirements through exploration

A developed version of the online custom tee design application has already been deployed in Google App Engine. It can be accessed through the link given below. The login authentication has not been enabled as this is an example application in the Trial Studio.
  • Use the id " to login as a product team member.
  • Use the id "" to login as customer relations executive.
  • Use the id "" to login as customer service representatives.
Ordering process overview:
  • Customer service representatives "" can create an order for an existing customer using "Create Order" option. For a new user, they can add a new user and then create an order for the user.
  • Customers can login using their registered mail id and confirm, amend or cancel their order.
  • Product Team "" must review the orders confirmed by the user.
  • Customer relations team "" must close the reviewed and cancelled orders.
Explore the application and try to identify the data entities, relationships between them, and associated workflows.

  Review the functional requirements of the example application

Now, let’s take a look at the functional requirements for our example application.

What does this example application do?
  • Our example application is a simple order procurement system that provides the functionality to maintain catalog information, record and track orders,  and maintain customer details.
  • In simpler terms: you are the owner of business that makes and sells custom tees. You do not want to set up a storefront; instead you decide to accept orders from customers through customer service representatives, who are available to take orders, answer questions, and share information about pricing specials and other incentives.  You want to develop a system that allows you to upload your product photographs, its description, pricing and other attributes, which can all be set up and stored; record and track orders; generate purchase receipts that can be saved to a customers account.
Who are the users?
  • Customers
  • Product Team
  • Customer Relations
  • Customer Service Representatives
What functionality does it provide?
  • Provide product team the ability to maintain catalog information.
  • Provide customer service representatives the ability to take orders and track order status.
  • Provide the functionality to generate purchase receipts that can be saved to a customers account.
  What's Next?

At this point you've reviewed our example application's functional requirements. You should now have a clear idea of what this example application does. You also know what UI elements you need to implement and how you want to lay them out. Now you're ready to learn OrangeScape Studio essentials to build an application.