This presentation is part of the Application Profile and Enterprise Application Accelerator Self-Study Course.
When you have entered the application data, the wizard displays a Review Application form that lists the records that will be built. Remember: You can use the left navigation panel to jump to any screen in the Application Accelerator tool to modify any information.
The RuleSets and classes will be built for the generalized class structure.
A Data Admin DB Table record will also be created that allows you to map the HR framework class group to a physical database table when the accelerator is finished.
Organization and Division Rules for Implementation
Organization and Division Rules for the implementation include the organization and division classes and RuleSets for the specialized class structure. These are based on the organization and division selected on the Base and RuleSets screen.
Work Pool Name and RuleSets
Work Pool Name and RuleSets include the Class group and RuleSet to represent the MyCo- implementation, as well as a Data-Admin-DB-Table record for database mapping.
Work Type includes the name of the work class to be created to represent work objects in the MyCo implementation.
Data Classes include a starting set of data classes for the HR Framework and MyCo implementation.
Applications displays the application rules to be created for the Framework and Implementation.
Finally, the review screen displays the remaining rule types that will be created including the Use Cases, Work Parties, Models, Harnesses, Sections and Flows.
Once you are satisfied with the records to be created, click the Create button to generate the application and class hierarchy.
Use Case Rules
By going to Rules by Type > Application Definition > Application UseCase, you will notice both Common and LeaveRequest use case rules. These are the use cases that were originally presented in the Profile that now become rules in our application. Upon opening one of the use case rules, you can see information related to the business objective, the actor information, the trigger, and the use case description. Click on the Implementation tab to look at the specific location in the flow where the use case resides. Each use case becomes a versioned rule, which is associated with the application.
The Application Rule provides an overview of application assets and quick access to use cases. To view this information, click on an application rule, such as HR. The Details tab pulls information originally from the Profile such as objective information, work types, categories, etc. The Use Cases tab details the use cases being bundled into the application. All of this is part of the documentation feature.
Finally, notice in the Application Explorer there is a new class group and the Leave request is a specialized work object. Looking at the display under the Application Explorer, notice the framework that was created has the leave request work class, followed by the Process and Report information.