Design Flow for Line Items with Multiple Codes BPs

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

  1. Create a Data Structure (if necessary)
  2. Launch the Design
  3. Design an Upper Form
  4. Design a Detail Form
  5. Create a Line Items list
  6. Create a Workflow
  7. Create a Log

The following explains each step in detail:

1. Create a Data Structure (if necessary)

This structure will include the data elements to be used on the forms. (If the data structure has not been created, see the instructions beginning with Creating a Data Structure.)

(Optional) If you are designing a business process 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. For more information on data pickers, see Across-Shell Functioning and About Data Pickers.

Reservation sub-type, you need to create one or more data pickers. Users will use these data pickers to choose the objects to reserve. The data pickers will be populated with the business process records (such as a space) that have been "calendar enabled."

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 in Designing an Upper Form.

For Change Commit sub-type, this field is mandatory:

A reference ID (Refid)

You will need to link the Change Commit BP to the Base Commit BP using this reference ID.

For Spends sub-type, this field is mandatory:

A reference ID (Refid)

You will need to link the Spends BP to the Base Commit BP using this reference ID.

For Lease sub-type:

If you want the straight-line rent amount to appear on the upper form of the lease, include this field:

If you include this field on the form, the user will not have to open the Payment Schedule to see the rent amount.

If you want to allow the Unifier user to adjust the date terms of a straight-line lease, or to add or subtract a one-time currency amount to/from the lease amount, include these fields on the Upper Form:

For Reservation sub-type:

If a Reservation business process should auto-create another business process before or after the reserved event takes place, these fields are mandatory and can be placed on the upper or Detail Form:

4. Design a Detail Form

If this business process is to roll up data from across shells, the following fields are mandatory on these forms to provide user navigation to records across shells:

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.

See the instructions in Designing an Upper Form.

For Base Commit sub-type, these fields are mandatory:

For Change Commit sub-type, these fields are mandatory:

For Spends sub-type,these fields are mandatory:

For Generic sub-type, these fields are mandatory:

For Payment Application sub-type, these fields are mandatory:

For Lease sub-type, these fields are mandatory:

To accommodate lease payment allocation, these fields are also mandatory:

If you want to allow the user to manually specify a first payment due date, include this field:

For Reservation sub-type, f the detail form should auto-create another business process before or after the reserved event takes place, these fields are mandatory:

5. Create a Line Items list

See Adding an Item Log to a Detail Form.

6. Create a Workflow

See the instructions beginning with Starting a Workflow.

7. Create a Log

See Designing a Business Process Log (Standard or Picker).


Last Published Monday, June 3, 2024