Across-Shell Functioning
Code and Records-based managers can operate across shells. An example would be warehouse managers located in various shells. In this scenario, each part could be tracked via a business process. The warehouses in the shells would stock parts and procure or replenish parts for the business processes across the shell hierarchy. In addition, stock could be moved or transferred from one warehouse to another, across shells. From the business processes for each part, quantities and costs could roll up to the appropriate warehouse; on-hand quantities could be maintained using formulas.
Such a manager, operating across shells, can accumulate a substantial number of records. With such an amount of records, users can easily make mistakes in choosing the correct one to work with. In order for the manager to function more efficiently, you should create data pickers to help Unifier users navigate to the correct log of records they want to work with. Using data pickers, users can pick records from the company level and from all shells in the hierarchy.
Using the functions available with data pickers, the sheets for these managers can display rollup data from across shells, and users will be able to drill down from the sheet to the business process transaction.
Note: For more information about data pickers, see About Data Pickers.
For the manager sheet, rollup data can come only from the following business processes. | |
At project/shell level: Cost - Line Items with Multiple Codes Line Item, Generic | At company level: Line Item, Generic |
For this type of manager to function across-shells, you need to create the following:
- A data picker for each manager class. When you place this data picker on a business process form, users can select a record across shells.
For this type of manager to roll up costs and quantities across-shells, you need to create the following:
- A data picker for each manager class. With this data picker, users can select a record across shells.
- A configurable manager picker
- A formula to link the configurable manager picker to the data picker
After you have created these pieces, place the data picker and the configurable manager picker on the business process whose costs or quantities should roll up to the manager sheet. (If the user does not need to see the configurable manager picker, you can place it in a hidden block on the form.)
Code-Based Manager
In Unifier, a code-based manager provides users a sheet on which to analyze information that is gathered from business processes, or manually entered on the sheet. This manager produces no records; the values being monitored appear only on the sheet. When designing the sheet, a user can specify business processes from which column values can be collected.
In Unifier, the [manager] node shows the sheets that have been created. Users can open these sheets to monitor items and add additional items to the sheets.
An example of a code-based manager might be a "facilities" manager where users could monitor ongoing or preventative maintenance on the company's facilities. In this manager, you could:
- Define a facilities code structure at the company level or at each building or shell level
- Design multiple business processes to track and calculate:
- Maintenance requirements
- Inspections
- Work orders
- Repairs
- Costs of facilities, from initial requisition through repairs and enhancements
- Various code-based managers, such as Facility Condition Index, to monitor the condition and usability of the facilities
Summary of Differences
The following table itemizes the differences between a code-based manager and a Code and Records-based manager.
Code-Based Manager | Code and Records-based Manager |
|---|---|
Uses an attribute form to create the codes that will appear on the sheet. | Uses an attribute (detail) form to define code "classes" for categorizing the items on the sheet and for collecting item details. Provides users a way to drill down to specific information from the sheet. |
Uses a single sheet for analyzing information about the items being managed. These items are added to the sheet manually by the user. Records do not exist for code-based managers; the values collected for a code-based manager exist only on the sheet. Values on this sheet can be gathered from business processes or manually entered. | Uses multiple sheets (one for each class) for analyzing information. New items are automatically added to the sheet from item records created by users filling out an attribute (detail) form. This type of manager gathers values from Cost and Line Item types of BPs for the manager sheet. |
The code structure for this type of manager is created by the administrator. | The code structure for this type of manager is created in uDesigner. |
You must design a picker for the manager. | The picker for the manager is based on the log design. |
Cannot operate across shell hierarchy | Can operate across the shell hierarchy. To facilitate this capability, one or more data pickers must be designed to help users navigate to records within the hierarchy. Sheets for these managers will display rollup data from across shells, and users will be able to drill down from the sheet to the business process transaction. |
The manager sheet: Is created manually by the user Shows codes as rows in a flat or tree format Can show rollup values from company and shell BPs at any status; values appear as columns on the sheet Does not support time-based filtering using queries | The manager sheet: Is created manually by the user; then automatically populated with the information gathered from class records Shows the records as rows in a flat or tree format Can show rollup values from company and shell BPs at any status; values appear as columns on the sheet Can update item records directly from sheet Supports the Unifier rules engine Does not support time-based filtering using queries |
Last Published Monday, June 3, 2024