AgileApps Support Wiki Pre Release

Difference between revisions of "Lab C.2: Explore the Application"

From AgileApps Support Wiki
imported>Aeric
m (Text replace - 'Settings > ' to 'File:GearIcon.png > Setup > ')
imported>Aeric
m (Text replace - 'Customization > Shared Global Resources > Packages' to 'Administration > Account Management > Packages')
 
(3 intermediate revisions by the same user not shown)
Line 2: Line 2:


==Discover the Objects Used in the Application==
==Discover the Objects Used in the Application==
# Click '''[[File:GearIcon.png]] > Setup > Administration > Global Resources > Packages > Order Processing'''<br/>A new pane appears with package information.
# Click '''[[File:GearIcon.png]] > Administration > Account Management > Packages > Order Processing'''<br/>A new pane appears with package information.
# Scroll to the bottom of the pane, to the list of dependencies.
# Scroll to the bottom of the pane, to the list of dependencies.
#* The entities this package depends on is displayed, under "Items".
#* The entities this package depends on is displayed, under "Items".
#*Notice the Contacts, and Accounts items, which are designated as type "Object".   
#*Notice the Contacts, and Accounts items, which are designated as type "Object".   
# Click '''Designer > Objects'''.<br/>The objects used in the application are shown, along with those used by other applications running in your instance of the platform.
# Click '''[[File:GearIcon.png]] > Customization > Objects'''.<br/>The objects used in the application are shown, along with those used by other applications running in your instance of the platform.
#:{{Tip|It's easy for applications to share information, because the objects they contain are living in the same cloud. For example, a customer record created in an order-entry application would be available for use in a shipping application.}}
#:{{Tip|It's easy for applications to share information, because the objects they contain are living in the same cloud. For example, a customer record created in an order-entry application would be available for use in a shipping application.}}


Line 12: Line 12:
An "object" in the platform is both a table in a database, and a record within it. When accessing a record, the singular form of the name is used, when referencing the table as a whole, the plural form is used. So the "Orders object" is a collection of records and the metadata that defines behaviors like validations and forms. An "Order object" on the other hand, is an individual record augmented by those behaviors.
An "object" in the platform is both a table in a database, and a record within it. When accessing a record, the singular form of the name is used, when referencing the table as a whole, the plural form is used. So the "Orders object" is a collection of records and the metadata that defines behaviors like validations and forms. An "Order object" on the other hand, is an individual record augmented by those behaviors.


# Click '''Designer > Objects > Orders'''.<br/>The Object Information pane appears.
# Click '''[[File:GearIcon.png]] > Customization > Objects > Orders'''.<br/>The Object Information pane appears.
# Here are the attributes you can modify:
# Here are the attributes you can modify:
#* [[Object Properties]], where the singular and plural forms of the object name are specified.  
#* [[Object Properties]], where the singular and plural forms of the object name are specified.  
#* [[Forms]] where you control how data is displayed and interactively edited
#* [[Forms]] where you control how data is displayed and interactively edited
#* Object [[Fields]]
#* Object [[Fields]]
#* GUI [[Actions]] to take when data is being specified (for example, to populate dependent fields)
#* [[Custom Form Actions]] that give the user action buttons they can press
#* [[Indexes]] though which records can be accessed
#* [[Indexes]] though which records can be accessed
#* [[Validations]] for field data
#* [[Validations]] for field data
#* [[Document Templates]] to determine how the data appears when printed, and
#* [[Document Templates]] to determine how the data appears when printed, and

Latest revision as of 00:07, 24 August 2013

In this exercise, you'll explore an application, identify some of its major components, and see how they are related.

Discover the Objects Used in the Application

  1. Click GearIcon.png > Administration > Account Management > Packages > Order Processing
    A new pane appears with package information.
  2. Scroll to the bottom of the pane, to the list of dependencies.
    • The entities this package depends on is displayed, under "Items".
    • Notice the Contacts, and Accounts items, which are designated as type "Object".
  3. Click GearIcon.png > Customization > Objects.
    The objects used in the application are shown, along with those used by other applications running in your instance of the platform.

Thumbsup.gif

Tip: It's easy for applications to share information, because the objects they contain are living in the same cloud. For example, a customer record created in an order-entry application would be available for use in a shipping application.

Examine the Orders Object

An "object" in the platform is both a table in a database, and a record within it. When accessing a record, the singular form of the name is used, when referencing the table as a whole, the plural form is used. So the "Orders object" is a collection of records and the metadata that defines behaviors like validations and forms. An "Order object" on the other hand, is an individual record augmented by those behaviors.

  1. Click GearIcon.png > Customization > Objects > Orders.
    The Object Information pane appears.
  2. Here are the attributes you can modify: