Template

Goal

The goal of template is to provide a logical relationship that can be used to construct an entire Project or its components. The RPM web services provide
one method that can be used to create objects from template in the Application interface: createObjectFromTemplate

Source

All classes related to templates are located in the wbs and scopemanagement packages.


Information

The API currently supports three types of templates: Project Templates, WBS Element Templates and Scope Management Templates. Loading a template is done following the XPATH architecture by specifying the @published=ProjectPublishedType.ToTemplate for WorkElement and @published=PublishedType.ToTemplate for the rest. Alternatively, creating  an object from template requires the use of the Application interface method: createObjectFromTemplate.

Here is the rundown of how it is done in the api:

  1. Once the createObjectFromTemplate is called from the Application interface, the managerCaller.createObjectFromTemplate is called with all the parameters: (SessionID, InputObject, TemplateObject, Scope)
  2. The managerCaller then evaluates the inputObject to choose which manager to call, either the WbsManager or the ScopeManager.
  3. The manager createObjectFromTemplate method is called.
  4. In the case of GenericProject  and WorkElement templates, the WbsMethodCheckPoint is called to do various validations such as:  
  5. In the case of AbstractRequest and AbstractScope templates, the ScopeMethodCheckPoint is called to do various validatios such as:

GenericProject Template

Manager: WbsManager

Classes:

SP_Calls:

WorkElement Template

Manager: WbsManager

Classes:

SP_Calls:

AbstractRequest Template

Manager: ScopeManager

Classes:

SP_Calls:

AbstractScope Template

Manager: ScopeManager

Classes:

SP_Calls:


Parent topic: Architecture Index
Template Usage: Template Concepts
Template Code Samples: Java code samples