Design Requirements for the Shell Manager

For the Shell Manager to work effectively, you will need to create the following components in uDesigner:

Note: Whether you include Data Elements (in one of the Log nodes for an item in the Shell Manager node in uDesigner) or not, Unifier will include the "Name" column in the log, by default, at runtime.

Shell Type Attribute form	Sets up the Shell Manager and defines the shell types, the kind of cost manager that will be used in the shells, the number of sub-shells that can be created, and enables the mapping feature. The information from this attribute form appears in Unifier on the Shell Properties window. The attribute data appears on the General tab when the user opens a shell from the Shell Manager node.
Log (standard or advanced)	Lists all the records that were created for the manager in Unifier at runtime. Standard logs display fields from the manager's attribute form that you want to monitor. For example, you might want a log for the Document Manager to include the names of all documents and their creators as well as their locations. For the Resource Manager, you might want the log to include the names of all resources and their current status. Advanced logs support data pickers. An advanced log should be designed for any shell that contains records that will be displayed on a data picker. (For more information on data pickers, see About Data Pickers.) See Designing a Log for a Manager.

Shell Type Attribute form

Sets up the Shell Manager and defines the shell types, the kind of cost manager that will be used in the shells, the number of sub-shells that can be created, and enables the mapping feature.

The information from this attribute form appears in Unifier on the Shell Properties window. The attribute data appears on the General tab when the user opens a shell from the Shell Manager node.

Log (standard or advanced)

Lists all the records that were created for the manager in Unifier at runtime.

Standard logs display fields from the manager's attribute form that you want to monitor. For example, you might want a log for the Document Manager to include the names of all documents and their creators as well as their locations. For the Resource Manager, you might want the log to include the names of all resources and their current status.

Advanced logs support data pickers. An advanced log should be designed for any shell that contains records that will be displayed on a data picker. (For more information on data pickers, see About Data Pickers.)

See Designing a Log for a Manager.

Design Flow

The following table outlines the design steps necessary to launch the manager and create a shell.

1. Create a data structure.	You must create two mandatory data elements: Shell name (based on the data definition SYS Shell Name) Shell number (based on the data definition SYS Shell Number) (Optional) Create a data picker(s). See Creating a Data Structure.
2. Launch the manager.	See Launching a Manager.
3. Create a Shell Type Attribute Form. See the instructions beginning with Starting an Attribute or Detail Form for a Manager.	Mandatory fields for the shell attribute form are: ID (must begin with us_ and at least one alpha-numeric character, allows up to eight characters) Shell name Shell number Shell administrator (uuu_administrator) Shell status (uuu_shell_status) Description uuu_location If the shell status should be automatically updated, include the field uuu_au_setup_picker. If the shell will be using mapping (that is, geo-searching is chosen as an option for this shell type), the following fields are mandatory: Either: An address (uuu_address_code) Or: A latitude (uuu_latitude) and A longitude (uuu_longitude) If the shell Project Start Date will be automatically populated to the Schedule Start Date for the master schedule sheet in the Schedule Manager, the following field is mandatory: Project Start Date—uuu_project_start_date
4. Create a log for the manager.	See Designing a Log for a Manager.

1. Create a data structure.

You must create two mandatory data elements:

Shell name (based on the data definition SYS Shell Name)

Shell number (based on the data definition SYS Shell Number)

(Optional) Create a data picker(s).

See Creating a Data Structure.

2. Launch the manager.

See Launching a Manager.

3. Create a Shell Type Attribute Form.

See the instructions beginning with Starting an Attribute or Detail Form for a Manager.

Mandatory fields for the shell attribute form are:

ID (must begin with us_ and at least one alpha-numeric character, allows up to eight characters)

Shell name

Shell number

Shell administrator (uuu_administrator)

Shell status (uuu_shell_status)

Description

uuu_location

If the shell status should be automatically updated, include the field uuu_au_setup_picker.

If the shell will be using mapping (that is, geo-searching is chosen as an option for this shell type), the following fields are mandatory:

Either:

An address (uuu_address_code)

Or:

A latitude (uuu_latitude) and

A longitude (uuu_longitude)

If the shell Project Start Date will be automatically populated to the Schedule Start Date for the master schedule sheet in the Schedule Manager, the following field is mandatory:

Project Start Date—uuu_project_start_date

4. Create a log for the manager.

See Designing a Log for a Manager.

In This Section

Details Block

Last Published Monday, June 3, 2024