Primavera Unifier: uDesigner — Lesson 2: Upper forms, detail forms, line items, validation, formulas, pickers, and reference processes

Learning Objectives

• Translate a realistic requirement into an executable approach for Upper forms, detail forms, line items, validation, formulas, pickers, and reference processes.
• Use configured form package and field-validation test to verify completeness, access, and process behaviour.
• Explain how to recover safely when a formula calculating correctly for one currency but not another occurs.

Detailed Topics

• Upper forms
• Detail forms
• Line items
• Validation
• Formulas
• Pickers
• And reference processes
• Decision ownership, prerequisites, and acceptance evidence for Upper forms, detail forms, line items, validation, formulas, pickers, and reference processes
• Relevant access, data, integration, performance, recovery, and support considerations

Instructor Demonstration

Using realistic data and role assignments, the instructor demonstrates Upper forms, detail forms, line items, validation, formulas, pickers, and reference processes. Key checkpoints are captured in configured form package and field-validation test, with discussion of alternatives, side effects, and the conditions required for an acceptable result.

Hands-On Exercise

Work through a role-based scenario involving Upper forms, detail forms, line items, validation, formulas, pickers, and reference processes. Validate the expected path, test the failure case “a formula calculating correctly for one currency but not another,” choose the safest corrective action, and capture the reasoning and outcome in configured form package and field-validation test.

1. Define the requirement and identify dependencies before changing the environment.
2. Create a baseline result that can be compared with later changes.
3. Reproduce the exception and test one hypothesis at a time.
4. Complete the evidence record and obtain peer or instructor review.

Scenario Analysis

• Clarify the business trigger, affected roles, required records, and acceptable result for Upper forms, detail forms, line items, validation, formulas, pickers, and reference processes.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how configured form package and field-validation test should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

For a failure in Upper forms, detail forms, line items, validation, formulas, pickers, and reference processes, separate access, setup, data, integration, and timing causes. Compare the observed sequence with configured form package and field-validation test; if “a formula calculating correctly for one currency but not another” is confirmed, make the smallest reversible correction and document why broader changes were rejected.

Validation Checklist

• Configuration and source data used for Upper forms, detail forms, line items, validation, formulas, pickers, and reference processes are versioned or otherwise traceable.
• Configured form package and field-validation test shows both the baseline and the accepted result.
• Security, performance, integration, and operational side effects have been considered where relevant.
• Recovery steps and handover notes are usable by a support practitioner.

Lesson Outcome

Learners can apply Upper forms, detail forms, line items, validation, formulas, pickers, and reference processes, explain the decisions made, and defend the result with configured form package and field-validation test.