Line Item Type

Line item BPs can be used for any generic data. They lend themselves well to business processes that involve miscellaneous information you may want to document for a company or project; for example, a vendor contact list. Or, they are useful for project-specific information that only needs to be documented on a single form, such as the overall project scope, or meeting minutes.

Line item BPs are also useful for collecting data that other, more restricted types of BPs cannot. For example, while a simple-type BP can be used to collect basic vendor information, a company-level line item BP can collect additional vendor information, such as multiple business addresses. At the project level, you can use a line item BP to filter large numbers of company records into smaller lists of records for your projects.

Line item BPs use a separate detail form to enter line items, which then appear on a line item list at the bottom of the form. Or, for short line items, Unifier users can enter information directly into the line item list using a "grid view" of the list.

You can design these BPs to accommodate line item status, so you can control modifications to individual line items based on their status.

There are three sub-types of this BP:

Generic

Use this sub-type for all line item BPs unless you want to filter BP records. To filter BP records, use the sub-type explained below.

Line Items to filter Company Business Process Records

Use this sub-type to filter company records into smaller lists of records for your projects. This BP is particularly suited for routing a list of vendors for approval for a project, thereby filtering the list of company vendors into lists of vendors who are appropriate for specific projects. Used for this purpose, this BP type can be linked (as a reference process) to an RFB to supply a project-specific vendor list for bid invitations.

Preventive Maintenance (if the module is available)

Use Preventive Maintenance to maintain assets proactively and on a regular basis, even when no issue has been reported on the asset. The Preventive sub-type has 5 classifications (Asset, Asset Template, PM Book, PM Book Template, and Meter Reading) and they are available for selection from Classification drop-down menu, after you select Preventive Maintenance as a sub-type. A Company can have more than one BP of a particular type (for example, two or more Asset BPs, two or more Asset Template BPs, and so forth).

Use Preventive Maintenance to maintain assets proactively and on a regular basis, even when no issue has been reported on the asset. The Preventive sub-type has 5 classifications:

Asset
Asset Template
PM Book
PM Book Template
Meter Reading

These classifications are available for selection from the Classification drop-down list, after you select Preventive Maintenance.

Note: A Company can have more than one BP of a particular sub-type (for example, two or more Asset BPs, two or more Asset Template BPs, and so forth).

Design Requirements

For these business processes to work effectively, you will need to create the following components in uDesigner:

Upper form
Detail form
Line Item List
Workflow
Log

Design Flow

The following table outlines the design steps necessary to create this business process.


For this sub-type:	These fields are mandatory:
1. Create a data structure (if necessary)	For the line item sub-type Line items to filter company business process records, you will need to create a BP picker to specify the business process from which the user will select the items to include on the filtered list. Use the BP Picker data definition to build this picker. If you are designing a business process for a Generic sub-type that will roll up data across shells to a Code and Records-based manager, you will need to design data pickers to help Unifier users locate and pick the correct BP records within the hierarchy. You will also need to link the data picker to a manager picker using a formula. For more information on data pickers, see Across-Shell Functioning and About Data Pickers. For information on linking a data picker to a manager picker, see Adding Formulas to Fields.
2. Launch the design	This step initializes the design process for the BP. See Starting a New Design (Edit Studio).
3. Design an upper form	See the instructions beginning with Designing an Upper Form.
4. Design a detail form	See the instructions beginning with Designing Detail Form.
	Line items to filter company business process records	uuu_line_item_status to specify what status the line item should be to include or exclude the item from the filtered list. BP picker Users will use this picker to select records from the business process this field references. The records the users select will be included on the filtered list for the project. (This picker should be the same picker that you specify on the Options tab when you start the BP design.)
	Generic	If this business process is to roll up data from across shells, the following fields are mandatory on this form to provide user navigation to records across shells: A data picker for each manager class A configurable manager picker These fields are mandatory for the form, but are not required to be filled in at runtime. However, if these fields are left blank on the form at runtime, data rollups will not occur. 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)
	5. Create a line item list	See Adding an Item Log to a Detail Form.
6. Create a workflow (if necessary)	See the instructions beginning with Starting a Workflow.
7. Create a log	See Designing a Business Process Log (Standard or Picker).
8. Link to a reference process (For sub-type Line items to filter company business process records)	Link the BP picker on the detail form to the BP that contains the list of records the users will choose from. See Adding a Reference Process to Auto-Populate Data.

In This Section

Preventive Maintenance

Last Published Monday, June 3, 2024