Demand to project conversion

[Kalyan33]

This article is about what all OOTB entities that are copied or moved while creating a project from demand.

        When project is created few Demand fields, Assessment fields of demand, Stakeholders, Requirements will be copied from demand to project whereas few entities like RIDAC, Cost plans and Cost plan breakdowns, Benefit plans and Benefit plan breakdowns, Non-monetary benefit plans and Non-monetary benefit plan breakdowns, Resource plans and Demand budget are moved to project by changing the task reference from demand to project.

And few entities like Demand tasks, Baselines, Assessment instances/results and Expense lines will remain as it is on demand.

When "Create Project" UI action is clicked it triggers createProject() method of "DemandToProjectCreationHelper" Script include where the project is created and it is responsible for copying/moving underlying entities of demand.

Demand fields:  

        In createProject() method following demand fields are copied to project before creating project.

fields = ['short_description', 'description', 'primary_program', 'business_case', 'sys_domain', 'investment_class', 'investment_type', 'risk_of_performing', 'risk_of_not_performing', 'enablers', 'barriers', 'in_scope', 'out_of_scope', 'assumptions', 'goals', 'strategic_objectives', 'business_unit', 'department', 'impacted_business_units', 'business_applications', 'business_capabilities', 'cmdb_ci', 'company', 'priority', 'urgency', 'impact', 'rate_model', 'project_manager', 'project_currency', 'approved_start_date', 'approved_end_date','calculation_type', 'data_separated_by']

Resource plans:

        After project creation, "project" field on demand record is updated with the created project which triggers the BR "Update Resource Plan on demand approval" where Resource plans of a demand are moved to project by changing the task reference.

Requirements:   

        Once project record is created, all the requirements of demand are copied to project.

Updating Financial Records: 

_updateFinancialRecords() method will move all the Cost plans and cost plan breakdowns, Benefit plans and benefit plan breakdowns, Non-monetary benefit plans and Non-monetary benefit plan breakdowns and Demand Budgets by changing the task reference from demand to project.

Note: Here task reference is updated with setWorkflow(false) to avoid triggering business rules.

RIDAC :

        After updating financial entities, RIDAC entities are moved from demand to project similarly by changing the task reference. Here Risks, Issues, Decisions, Project actions, Request changes and RIDAC_m2m records are moved.

Assessment fields of demand:

        Demands fields related to Assessment data (Risk, Size, Value and Score of demand) are copied to the created project.

Note: Assessment Instances/Results still have reference to demand. Only the demand fields(Risk, Size, Value and Score) are copied.

Stakeholders:

        copyStakeHoldersFromDemandToProject() is used to create copy of stakeholder records on project from demand.

Project Currency Financial fields:

     if Multi currency plugin is active then calculateProjectCurrencyFieldsOnConvertedProject() will calculate all the project financial fields  based on project currency and reference rate.

[kaka_tyou]

Nice article!

It's really helpful!👏

[phil_bool_unifi]

There's lots of good information here, thanks!