Create a New Shell Manually

To create a new shell manually

Go to the Company Workspace tab and switch to Admin mode.
Click Company Sponsored Shells in the left Navigator.
Select a shell type.
Notes:
- Ensure that you configure and test shells in the Development environment before you import the shells into the Test environment or Production environment.
- The DE of type Rich Text DE is not available to be added to the Company Sponsored Shells.
Click the New button. The <shell> Details window opens.
On the General tab, complete the fields as described in the table below.
Note: The table only lists the required fields that are common across most shells. The shell that was designed for your company will include other required and optional fields. Required fields are marked with an asterisk (*).
On the Currency tab, click the Add button to add a default currency for the shell.
Note: You cannot modify this default currency after you save the changes to the Details window. When you click Apply to save changes, you will receive a confirmation warning that reads: "You are about to create a new <Shell Type Name>. The default currency of this <Shell Type Name> is <Currency Name> (<Currency Code>). After the <Shell Type Name> has been created, this default currency cannot be changed. Are you sure you want to continue?" If you click Yes, you will not be able to change the default currency.
Use the information in the table below to add a currency.
Click the Options tab, and complete the fields.
You can upload an image to display on the landing page of the shell in both Administrator and User Modes, specify a phase of the shell, and configure email notification. (For information on this mailbox, see Dedicated Mailbox for Shells.)
Complete the Links tab to add links to the shell.
These links are displayed on the shell landing page in User mode. Use links to provide users with access to useful websites, your company's website, an intranet, or other destinations.

Click Add and enter the name and URL for the links you want to add to the landing page.
Click the Calendar tab, and select one of the following options:
- Standard Calendar: This option lets you use a standard calendar for your shell. You can select the Company Calendar (Default) or other listed calendars.
- Custom Calendar: This option lets you use a custom calendar for your shell. You can use Copy to select a calendar or create a custom calendar.
If applicable, click the Integration tab, and enter the Project ID of the Source Project.
Click Apply to save changes as you enter information, and OK when you are ready to save information and exit the window.

In this field	Do this
Administrator	Select an administrator for the shell.
Hierarchy Path	The Location picker allows you to change the location of a shell, and is accessible when you set up a shell or modify the shell details. See Location Picker Behavior for details. Use the Location Picker to select where the shell instance will reside. In the Location picker: Find searches the current level Open shows the next level of shells Select completes the action Location Picker will allow breadcrumbs to display through the hierarchy Work systematically from the top of the hierarchy to the bottom There must be an instance of a single shell to connect to You can use the Location picker to reorganize the shell hierarchy. The shell can move across tabs, or laterally along the hierarchy. When you move a shell instance, all of the shell data moves with the shell. If an auto-populated business process moves with the shell instance, then the auto-populated data moves with the business process. Data for the business process will be collected from the new shell location. In addition, if a child shell has been designed with linked elements, field values on the shell's attribute form or single-record BPs will be automatically updated to reflect changes when the shell is moved.
Status	You can activate the shell immediately, or place it On-hold and activate it later. A shell that is On-hold or Inactive cannot be used. It is good practice to leave a shell On-hold until you have completed the setup. Shell Administrators/Users with "modify shell status" rights are the only ones who can change the status. Status definitions for shells are: On-hold: The initial shell status. On-hold shells appear on the shells log. Shell administration functionality is available to shell administrators for setup and maintenance for users with permissions to perform that function. Users cannot create records in a shell that is On-Hold. If a user attempts to access a shell that is On-Hold, the system displays an alert message stating that the shell is On-Hold. Active: Active, in-progress shell. All shell actions in User and Administration Mode are available. View-Only: For end users, View-Only shells can be viewed, printed, exported, and included in reports. They cannot be modified. When a shell is View-Only, the status overrides (but does not modify) access control permissions, granting only View permissions. The shell reverts to the access control permissions when the shell is made Active. View-Only shells can be added to and removed from programs, and can roll up to UDRs and dashboards. Business process records cannot be auto-created in View-Only shells. Data rolls up to dashboards on a View-Only shell from child shells in the hierarchy, and rolls up to a parent shell from a View-Only shell. No updates can occur to View-Only projects through Integration, Mobile, or through reverse auto-population. View-Only shells cannot be updated through templates. Consolidate line item functionality is disabled for View-Only shells. Users can navigate through the shell hierarchy using View-Only shell instances. View-Only shells have only view, export, and print permissions available. Tasks and Drafts are not available for View-Only shells. Messages are available, but users cannot add comments. Mailbox is available for viewing, but users cannot send, edit or delete messages for View-Only shells. When a shell becomes View-only, all scheduled jobs associated with it are canceled. When the status of the shell changes back to Active, you must restart any scheduled jobs. Administrators can perform all actions on View-Only shells. Inactive: Used to suspend shell usage. Inactive shells are visible from the Administration Mode under Sponsored Shell log only, but not visible under the Shells node (i.e., only Sponsor Company can access the shell), or in User Mode logs and selections. Only System and Shell Administrators (users with Modify Status rights) can reactivate the shell. Note: "Late" tasks in an inactive shell may still show up in users' tasks logs. Though they can access the task, no transactions can be performed in the inactive shell.
Currency Name	Select the currency you want to use for the cost functions in this project. If the currency you selected is other than the company Base Currency, then complete the following fields.
Rate	Enter an exchange rate to use for conversion calculations. From the drop-down list select one of the following: If Float is selected, the rate is updated automatically from the company currency table (Standards & Libraries > Exchange Rate). A Peg rate is locked at the company rate on the day the rate is set. (Only a Project Administrator can manually modify the Peg rate to a value other than the company peg rate.).
Hedge?	If the Hedge selection is Yes, then the Hedge rate is used for conversion calculations. Otherwise, the Float rate will be used.
Rate	(Optional) If an amount is entered for the Rate, then the hedge rate is used until the amount specified is reached (by spends) and then the system will revert back to the normal rate.
Amount	(Optional) If Float is specified, the system will retrieve the rate, based on today's date and time. If Peg Rate is specified, the field will be editable.
Comments	(Optional) Add any comments that might be necessary to explain the default currency.

To create a new shell manually

Related Topics