Design Requirements for Launching a Manager
For the managers to work effectively, you will need to create the following components in uDesigner:
Attribute Form (In some managers, this is a detail form.) | Each manager requires at least one attribute form to make it operational in Unifier. See the instructions beginning with Starting an Attribute or Detail Form for a Manager. |
|---|---|
Formula (For the Standard Cost Manager) | For the Cost Manager, you will need to define formulas to create codes for funds and company accounts. See Designing a Formula for Fund or Account Codes. |
Picker (For the Standard Cost Manager) | Two attribute forms—Fund Attributes and Account Code Attributes—use pickers designed specifically for them because they do not create records that will appear on logs; they exist only as part of a fund sheet or cost sheet. For these cases, you will need to design a picker in the same way you would design a log. See Designing a Picker. |
Picker (for a Generic Cost Manager) | The attribute form for a Generic Cost Manager will need a picker designed specifically because they do not create records that will appear on logs; they exist only as part of a fund sheet or cost sheet. For these cases, you will need to design a picker in the same way you would design a log. See Designing a Picker. |
Picker (for a code-based manager) | The attribute form for a code-based configurable manager will need a picker designed specifically because they do not create records that will appear on logs; they exist only as part of a fund sheet or cost sheet. For these cases, you will need to design a picker in the same way you would design a log. See Designing a Picker. |
Data Picker(s) For: A Code and Records-based manager The Shell Manager | (Optional) If you are designing these managers, data pickers will help users locate and pick the correct business process records across manager classes and shells within a 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 a manager class or shell hierarchy. See Creating a Data Picker Definition. |
Log (standard or advanced) | 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. Picker logs support data pickers. An advanced log should be designed for any configurable manager class, or shell hierarchy. (For more information on data pickers, see About Data Pickers.) For instructions on creating a log, see Designing a Log for a Manager. |
Last Published Monday, June 3, 2024