Difference between revisions of "Activating the Pandora Development Environment"
From SmartWiki
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | The Pandora development environment is created using a Universal Tracking | + | The Pandora development environment is created using a [[Universal Tracking Application]]™. You may create this application for the purpose of creating and managing your API code. It is not mandatory to use this, but is a useful tool to edit, share and retain code. |
To set up this functionality: | To set up this functionality: | ||
| Line 9: | Line 9: | ||
Once this is set up, you can create Level 1's and edit your content as required. | Once this is set up, you can create Level 1's and edit your content as required. | ||
| − | The benefits of managing code in this manner are that you leverage all the functionality of the | + | The benefits of managing code in this manner are that you leverage all the functionality of the [[UTA]] to manage the development process. Some of the UTA features you can take advantage of are as follows: |
* Each Level 1 entity will represent a single web page of code. | * Each Level 1 entity will represent a single web page of code. | ||
* Different types of code can be managed through different Level 1 templates, for example – a template type to represent Search pages, Registration pages, Updating pages and Tutorial pages. | * Different types of code can be managed through different Level 1 templates, for example – a template type to represent Search pages, Registration pages, Updating pages and Tutorial pages. | ||
| − | * The status of the code can be controlled through standard level 1 statuses such as In Development, In Production, Checked Out and No Longer used. | + | * The [[status]] of the code can be controlled through standard level 1 statuses such as In Development, In Production, Checked Out and No Longer used. |
* Different developers can be associated with each page through the Contact feature. | * Different developers can be associated with each page through the Contact feature. | ||
* The security matrix can be used to determine who much control different users can have of each page. | * The security matrix can be used to determine who much control different users can have of each page. | ||
Latest revision as of 14:15, 22 June 2011
The Pandora development environment is created using a Universal Tracking Application™. You may create this application for the purpose of creating and managing your API code. It is not mandatory to use this, but is a useful tool to edit, share and retain code.
To set up this functionality:
- Configuration >> Tracking Applications >> New application
- Create application you will use as your code editor
- Application Settings >> Click the checkbox "Enable Content Management" if required
- Return to Level 1 templates >> Create/Edit template >> Select Content Management as Type and Save
Once this is set up, you can create Level 1's and edit your content as required.
The benefits of managing code in this manner are that you leverage all the functionality of the UTA to manage the development process. Some of the UTA features you can take advantage of are as follows:
- Each Level 1 entity will represent a single web page of code.
- Different types of code can be managed through different Level 1 templates, for example – a template type to represent Search pages, Registration pages, Updating pages and Tutorial pages.
- The status of the code can be controlled through standard level 1 statuses such as In Development, In Production, Checked Out and No Longer used.
- Different developers can be associated with each page through the Contact feature.
- The security matrix can be used to determine who much control different users can have of each page.
- Notes can be added to each page.
