Application Construction Wizard

> Administration > Applications > [Create New Application]

Create Using Template

This tab appears only when the Community Marketplace is disabled.

It displays a catalog of basic applications that can be further customized. (The same applications as the Marketplace, but with less descriptive information.)

1. Click [Test Drive] to try one out and see if it is close to what you need.
2. When you find one that would make a good starting point, click [Install]
3. Then use the Designers Index to guide your customization efforts.

Create By Import

When you have data in a spreadsheet, you can use this tab to create an application built from that spreadsheet. The imported spreadsheet becomes a new Object in the application, which can then be customized.

1. Paste the data from the spreadsheet directly into the wizard, or import a CSV datafile that was exported from the spreadsheet.

   Important:
   Each column becomes a field in the platform object.

   The first row of the spreadsheet should contain labels for those fields.

2. Click [Next]
3. You can now specify the field names and the name of the object to create.
   You can also tell the wizard not to import selected columns of data.
4. Click [Create this Application]
   You now have a running, mobile-enabled application with data storage, and initial data entry and access forms.
5. Next, customize the data forms and take advantage of the platform's many other capabilities, using the Designers Index as a guide.

Create Using Wizard

When you click this tab, you can create an application by defining objects, fields, and the relationships between them. You can also create an entire Dynamic Case Management application with a single selection--adding other objects and relationships now or later.

There are several kinds of applications that can be created, or used straight out of the box:

• ServiceDesk application

  ServiceDesk is an specialized version of a Dynamic Case Management (DCM) app that is optimized to handle incoming incident reports, service requests, or "trouble tickets". It is the initial application your organization sees and, for many, it is the only application they need.

• Dynamic Case Management application

  A DCM app is an extended, general-purpose extension of a database application that helps to manage incoming cases (aka requests, investigations, or incidents). Your organization can have only one ServiceDesk application, but you can have as many DCM apps as you want.

• Database Application

  A database app provides interactive design, pre-built forms, the ability to collaborate, and much more. Like DCM apps, you can have as many database apps as you want.

Learn more: Types of Applications

Whichever option you choose, be sure to take advantage of the AgileApps Cloud platform's capabilities for Automating and Optimizing Your Activities.

To create an application using the wizard:

1. Enter the Application Name

2. Application Type
   • Dynamic Case Management Application

     Create a Dynamic Case Management application when your main Object records (be they cases, investigations, or incidents) could be in one of several states. For example: Open, Pending, or Closed. (The need for state-dependent behavior is a prime indicator that a DCM application may be appropriate.)

     • Case Object Title

       The default value is Cases. Throughout the documentation, and when writing code, the object always goes by that name. But the interface can display a label that is appropriate for the application. For example, Incidents or Investigations.

       Learn more: Building a Dynamic Case Management Application in the AgileApps Cloud (pdf)

     • [Add additional Object]

       Click this button to define additional application objects.

       Most of the objects you need are included automatically, with two exceptions: Accounts and Contacts.

       Those objects are part of the standard ServiceDesk application, and other common applications.

       They can be added to the current application after it is created, using Resource Sharing. But is not necessarily the case that the Contacts and Accounts used in one application are the same as those used in another, so they're not included by default.

   • Database Application

     A database application can have multiple objects with rich interconnections between them. It can also allow for collaboration among multiple parties.

     Learn more: Creating a Database Application

     • Object name

       Enter the name of the first object in the application.

Define an object:

1. Click [Define Fields]

2. Specify object labels:
   • Plural Label - The label used when the context is the object itself, or to the collection of records it contains
   • Singular Label - The label used when the context is a single record stored in the object
3. For the Cases object, specify the label to use for the built-in subject and description fields (or use the defaults).

4. Define up to 10 fields, to get started. (You can add more later.) For each field, specify:
   • Field Label - The label users will see.
   • Internal Field Name - The internal reference name. (Created for you. Modifiable, but generally best left alone.)
   • Field Type - Pick one of the many choices
5. Follow the prompts to add additional information, depending on the field type.
6. When done defining fields, click [Save]

For more, click [Add additional Object] and repeat the process.

Establish relationships between objects:

1. Click [Add a Relationship]
2. Under Relationships select the objects to fill in the blanks:

   Between __{baseObject}__ and __{relatedObject}__

3. Specify the Relationship Type:
   • One to Many - One {baseObject} record can be related to many {relatedObject} records

     For example: One Order can have many OrderItems.

     This option adds a Lookup field to the {relatedObject} that targets the {baseObject}.

     Notes:

     • To make a One to One relationship, construct it as One to Many, and add a Unique Index to the target object to ensure that only one such record can ever exist.
     • To make a Master-Detail relationship, use the Cascade Rules to auto-delete detail records when a master record is deleted.

   • Many to Many - One {baseObject} record can be related to many {relatedObject} records, and each of the {relatedObject} records can be related to many {baseObject} records

     For example: One Order can have many Tags, and one Tag can be applied to many Orders.

The relationships cause Lookup fields to be added to the objects, with names like "related_to_X". For example, the OrderItems object will have a field named related_to_Orders.

Create the application:

1. Click [Create this Application]
2. Click [Open Application] to run it