Design Requirements for a Code and Records-based Manager

For a manager to work effectively, you will need to create the following components in uDesigner.

Data elements

To roll up quantity amounts to the manager sheet, you need to create specific data elements (fields) to place on the attribute form for the manager. These fields must be built on the following data definitions:

SYS BP Currency Amount

SYS BP Decimal Amount

SYS BP Integer Amount

Attribute form

Defines a code class. Users will see the information from this form in the Code Details window in Unifier; also appears on the Code Picker on business processes where users must choose a code from a list.

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, configurable manager class, or business process that contains records that will be displayed on a data picker. (For more information on data pickers, see About Data Pickers.)

Reference process

If you include a BP Picker on the form, a reference process is necessary to point to the BP you want to reference.

Data Picker(s)

(Optional) If you are designing a Code and Records-based manager that will operate across shells, data pickers will help users locate and pick the correct BP records within the hierarchy. A data picker filters the information that appears on the picker so that users do not have to search through a multitude of records in the shell hierarchy.

Design Flow

Following are the overall steps necessary to design the coding structure and launch a Code and Records-based manager.

The following table outlines these steps with additional details.

1. Create a data structure.

For this type of manager, you must create three data elements for the attribute form:

One to gather currency values from the line items of a business process. Use the SYS BP Currency Amount data definition to build this element.

One to gather decimal values from the line items of a business process. Use the SYS BP Decimal Amount data definition to build this element.

One to gather integer values from the line items of a business process. Use the SYS BP Integer Amount data definition to build this element

(Optional) If you are designing a Code and Records-based manager that will operate across shells, data pickers will help users locate and pick the correct BP records within the hierarchy. For more information on data pickers, see About Data Pickers.

See the instructions beginning with Creating a Data Structure.

2. Launch the manager.

This step initializes the design process for the manager. See Starting an Attribute or Detail Form for a Manager.

3. Create an attribute form.

See the instructions beginning with Designing a Form.

Mandatory fields for the attribute form are:

Code (uuu_cm[1...25]_code)

Code Status (uuu_cm[1...25]_status)

Code Name (uuu_cm[1...25]_name)

Any fields that should be used as part of the code.

If the manager sheet is in a tree format, this field is mandatory:

Navigation code (uuu_code_navigation_code)

 If users should be able to reserve this item, these fields are mandatory:

Allow item to be reserved (uuu_rsv_reservable)

Allow over-booking (uuu_rsv_overbook)

4. Create a log.

See Designing a Log for a Manager.


Last Published Monday, June 3, 2024