Difference between revisions of "Combining bxp and Microsoft Project"

From All n One's bxp software Wixi

Jump to: navigation, search
(Created page with "= Overview = bxp has the power to be able to integrate and work with Microsoft Project structures. It is important therefore to understand the underlying data structures in...")
 
Line 9: Line 9:
  
 
So the first data structure is the Project table.
 
So the first data structure is the Project table.
 +
 +
 +
 +
 +
  
  
 
{| class="wikitable"
 
{| class="wikitable"
−
! Microsoft Table
 
 
! Microsoft Name
 
! Microsoft Name
 
! Microsoft Description
 
! Microsoft Description
−
! bxp Equivalent
+
! bxp Field
 
! bxp Notes
 
! bxp Notes
 
|-  
 
|-  
−
| Project fields || Areas Impacted || The Areas Impacted field contains examples of areas that could be affected by a proposal, as selected in the Areas Impacted lookup table, which is shipped with Microsoft Project Server and can be modified to reflect the organization’s specific areas. This field is controlled by the workflow.  ||  ||  
+
| '''bxp primary fields''' || || ||
 +
|-
 +
| || || intProject_Id|| unique Id for each project system managed
 +
|-
 +
| || || strProject_Active || Control variable to show / hide projects.
 +
|-
 +
| || || strProject_Name || The name for the project
 +
|-
 +
| || || strProject_Description || Reminder summary notes for what the project is
 +
|-
 +
| || || strProject_Location || Text box description of where the project is physically for
 +
|-
 +
| || || strProject_Group || Reporting project grouping field
 +
|-
 +
| '''bxp control options''' || || ||
 +
|-
 +
| || || strProject_ShowPrice || Control setting to use the costing aspects of a project
 +
|-
 +
| || || strProject_ShowProposalPrice || Control setting to allow Project owners add Proposal Price but hide from resources delivering the project.
 +
|-
 +
| || || strProject_ShowPriority || Control setting to allow resources delivering elements see priorities
 +
|-
 +
| || || strProject_ShowIssueTimeFrame || Control setting to allow client views see Service Level Agreement time frames.
 +
|-
 +
| || || strProject_ShowProposedWorkingTime || Control setting to use the proposed time engine. (useful when delivering a project to hide the proposed times).
 +
|-
 +
| || || strProject_ShowActualWorkingTime  || Control setting to use the actual delivered working time.  (useful to hide when delivering only a proposal)
 +
|-
 +
| || || strProject_ShowCustomerProducts || Control setting to allow only projects where a client has a contract for an agreed project.
 +
|-
 +
| '''work control options''' || || ||
 +
|-
 +
| || || strProject_Preassigned || Enable / disable the task preassigned engine
 +
|-
 +
| || || intProject_PreassignedTo || If preassigned is used, to whom the tasks are preassigned.
 +
|-
 +
| || || intProject_TeamId
 +
|-
 +
| || || intProject_TeamMemberId
 +
|-
 +
| '''bxp notification options''' || || ||
 +
|-
 +
| || || strProject_OnProjectCloseNotify  || When a project hits milestones or is completed, should a notification be sent?
 +
|-
 +
| || || strProject_EmailOnUpdate ||
 +
|-
 +
| || || intProject_MailAccountId || To which email addresses should notifications be sent.
 +
|-
 +
| '''Project task creation limitations''' || || ||
 +
|-
 +
| || || strProject_GeneralOrCustomer
 +
|-
 +
| || || strProject_PreventByWarranty || Control setting to only allow projects if the customer has a product in warranty
 +
|-
 +
| '''Microsoft fields''' || || ||
 +
|-
 +
| Areas Impacted || The Areas Impacted field contains examples of areas that could be affected by a proposal, as selected in the Areas Impacted lookup table, which is shipped with Microsoft Project Server and can be modified to reflect the organization’s specific areas. This field is controlled by the workflow.  ||  ||  
 
|-
 
|-
−
| Project fields || Assumptions || The Assumptions field contains key assumptions for the current proposal. This field is controlled by the workflow. ||  ||  
+
| Assumptions || The Assumptions field contains key assumptions for the current proposal. This field is controlled by the workflow. ||  ||  
 
|-
 
|-
−
| Project fields || Business Need || The Business Need field is used to specify the business requirement for the current proposal. When you add information, be sure to be as specific as possible. This field is controlled by the workflow. ||  ||  
+
| Business Need || The Business Need field is used to specify the business requirement for the current proposal. When you add information, be sure to be as specific as possible. This field is controlled by the workflow. ||  ||  
 
|-
 
|-
−
| Project fields || Committed Planned End Date || The Committed Planned End Date field specifies the finish date of the project as committed to in a Portfolio Selection Scenario during resource constraint analysis.  ||  ||  
+
| Committed Planned End Date || The Committed Planned End Date field specifies the finish date of the project as committed to in a Portfolio Selection Scenario during resource constraint analysis.  ||  ||  
 
|-
 
|-
−
| Project fields || Committed Planned Start Date || The Committed Planned Start Date field shows the beginning date of the project as committed to in a Portfolio Selection Scenario during resource constraint analysis. || ||  
+
| Committed Planned Start Date || The Committed Planned Start Date field shows the beginning date of the project as committed to in a Portfolio Selection Scenario during resource constraint analysis. || ||  
 
|-
 
|-
−
| Project fields || Committed Portfolio Selection Decision (Cost) || The Committed Portfolio Selection Decision (Cost) field shows the result of a cost constraint analysis on a project. You can choose Selected, Unselected, Forced-In/Out, or Custom Forced-In/Out. ||  ||  
+
| Committed Portfolio Selection Decision (Cost) || The Committed Portfolio Selection Decision (Cost) field shows the result of a cost constraint analysis on a project. You can choose Selected, Unselected, Forced-In/Out, or Custom Forced-In/Out. ||  ||  
 
|-
 
|-
−
| Project fields || Committed Portfolio Selection Decision (Schedule) || The Committed Portfolio Selection Decision (Schedule) field shows the commitment date of a Portfolio Selection Scenario as determined during schedule constraint analysis.  ||  ||  
+
| Committed Portfolio Selection Decision (Schedule) || The Committed Portfolio Selection Decision (Schedule) field shows the commitment date of a Portfolio Selection Scenario as determined during schedule constraint analysis.  ||  ||  
 
|-
 
|-
−
| Project fields || Committed Portfolio Selection Decision Date (Cost) || The Committed Portfolio Selection Decision Date (Cost) field shows the commitment date of a Portfolio Selection Scenario as determined during cost constraint analysis. ||  ||  
+
| Committed Portfolio Selection Decision Date (Cost) || The Committed Portfolio Selection Decision Date (Cost) field shows the commitment date of a Portfolio Selection Scenario as determined during cost constraint analysis. ||  ||  
 
|-
 
|-
−
| Project fields || Committed Portfolio Selection Decision Date (Schedule) || The Committed Portfolio Selection Decision Date (Schedule) field shows the result of a schedule constraint analysis on a project. You can choose Selected, Unselected, Forced-In/Out, or Custom Forced-In/Out.  ||  ||  
+
| Committed Portfolio Selection Decision Date (Schedule) || The Committed Portfolio Selection Decision Date (Schedule) field shows the result of a schedule constraint analysis on a project. You can choose Selected, Unselected, Forced-In/Out, or Custom Forced-In/Out.  ||  ||  
 
|-
 
|-
−
| Project fields || Compliance Proposal || The Compliance Proposal field indicates whether the current proposal is for a project that helps meet a compliance goal, that is, whether the project is required by law, regulation, or other requirements.  ||  ||  
+
| Compliance Proposal || The Compliance Proposal field indicates whether the current proposal is for a project that helps meet a compliance goal, that is, whether the project is required by law, regulation, or other requirements.  ||  ||  
 
|-
 
|-
−
| Project fields || Goals || The Goals field contains the measurable goals of the current proposal. This field is controlled by the workflow.  ||  ||  
+
| Goals || The Goals field contains the measurable goals of the current proposal. This field is controlled by the workflow.  ||  ||  
 
|-
 
|-
−
| Project fields || Post Implementation Review Date || The Post Implementation Review Date field indicates when the Post Implementation Review meeting was or will be held. This field is controlled by the workflow.  ||  ||  
+
| Post Implementation Review Date || The Post Implementation Review Date field indicates when the Post Implementation Review meeting was or will be held. This field is controlled by the workflow.  ||  ||  
 
|-
 
|-
−
| Project fields || Post Implementation Review Notes || The Post Implementation Review Notes field stores review meeting notes or a link to a meeting notes publication for the post-implementation review. This field is controlled by the workflow. ||  ||  
+
| Post Implementation Review Notes || The Post Implementation Review Notes field stores review meeting notes or a link to a meeting notes publication for the post-implementation review. This field is controlled by the workflow. ||  ||  
 
|-
 
|-
−
| Project fields || Primary Objectives || The Primary Objectives field contains the primary objectives for the current proposal, as selected in the Primary Objective lookup table, which is shipped with Microsoft Project Server and can be modified to reflect the organization’s specific objective statements. This field is controlled by the workflow.  ||  ||  
+
| Primary Objectives || The Primary Objectives field contains the primary objectives for the current proposal, as selected in the Primary Objective lookup table, which is shipped with Microsoft Project Server and can be modified to reflect the organization’s specific objective statements. This field is controlled by the workflow.  ||  ||  
 
|-
 
|-
−
| Project fields || Project Departments || The Project Departments field contains the name of the department with which the selected project is associated, as selected in the Department lookup table, which is shipped with Microsoft Project Server and can be modified to reflect the organization’s specific department names. ||  ||  
+
| Project Departments || The Project Departments field contains the name of the department with which the selected project is associated, as selected in the Department lookup table, which is shipped with Microsoft Project Server and can be modified to reflect the organization’s specific department names. ||  ||  
 
|-
 
|-
−
| Project fields || Proposal Cost || The Proposal Cost field stores the estimated cost for the proposed project. This field is controlled by the workflow.  ||  ||  
+
| Proposal Cost || The Proposal Cost field stores the estimated cost for the proposed project. This field is controlled by the workflow.  ||  ||  
 
|-
 
|-
−
| Project fields || Proposed Finish Date || The Proposed Finish Date field contains the estimated end date for the current proposal. This field is controlled by the workflow.  || ||  
+
| Proposed Finish Date || The Proposed Finish Date field contains the estimated end date for the current proposal. This field is controlled by the workflow.  || dteProject_End || Also used in menu listing to only show relevant active projects.
 
|-
 
|-
−
| Project fields || Proposed Start Date || The Proposed Start Date field contains the estimated beginning date for the current proposal. This field is controlled by the workflow.  || ||  
+
| Proposed Start Date || The Proposed Start Date field contains the estimated beginning date for the current proposal. This field is controlled by the workflow.  || dteProject_Start || Also used in menu listing to only show relevant active projects.
 
|-
 
|-
−
| Project fields || Workflow Phase Name || The Workflow Phase Name field specifies the current workflow phase for a selected project. A phase represents a collection of stages grouped together to identify a common set of activities in the project life cycle. Typical workflow phases are Create, Select, Plan, and Manage, although these phase names may be customized. This field is a component of the Microsoft Project Server workflow framework.  ||  ||  
+
| Workflow Phase Name || The Workflow Phase Name field specifies the current workflow phase for a selected project. A phase represents a collection of stages grouped together to identify a common set of activities in the project life cycle. Typical workflow phases are Create, Select, Plan, and Manage, although these phase names may be customized. This field is a component of the Microsoft Project Server workflow framework.  ||  ||  
 
|-
 
|-
−
| Project fields || Workflow Stage Info || The Workflow Stage Info field describes the current workflow stage for a selected project. A stage represents a single step within a project life cycle, and one or more stages can make up a workflow phase. This field is a component of the Microsoft Project Server workflow framework.  ||  ||  
+
| Workflow Stage Info || The Workflow Stage Info field describes the current workflow stage for a selected project. A stage represents a single step within a project life cycle, and one or more stages can make up a workflow phase. This field is a component of the Microsoft Project Server workflow framework.  ||  ||  
 
|-
 
|-
−
| Project fields || Workflow Stage Name || The Workflow Stage Name field specifies the current workflow stage name for a selected project. A stage represents a single step within a project life cycle, and one or more stages can make up a workflow phase. This field is a component of the Microsoft Project Server workflow framework.  ||  ||  
+
| Workflow Stage Name || The Workflow Stage Name field specifies the current workflow stage name for a selected project. A stage represents a single step within a project life cycle, and one or more stages can make up a workflow phase. This field is a component of the Microsoft Project Server workflow framework.  ||  ||  
 
|-
 
|-
−
| Project fields || Workflow State || The Workflow State field indicates a selected proposal or project’s current workflow state—for example, Waiting For Approval or Completed. This field is a component of the Microsoft Project Server workflow framework.  ||  ||  
+
| Workflow State || The Workflow State field indicates a selected proposal or project’s current workflow state—for example, Waiting For Approval or Completed. This field is a component of the Microsoft Project Server workflow framework.  ||  ||  
 
|-
 
|-
 
|}
 
|}

Revision as of 14:26, 8 July 2017

1 Overview

bxp has the power to be able to integrate and work with Microsoft Project structures. It is important therefore to understand the underlying data structures in Microsoft Project first.

Microsoft provide the following specification of their fields. https://support.office.com/en-us/article/Available-fields-reference-615a4563-1cc3-40f4-b66f-1b17e793a460

2 Structure

So the first data structure is the Project table.




Microsoft Name Microsoft Description bxp Field bxp Notes
bxp primary fields
intProject_Id unique Id for each project system managed
strProject_Active Control variable to show / hide projects.
strProject_Name The name for the project
strProject_Description Reminder summary notes for what the project is
strProject_Location Text box description of where the project is physically for
strProject_Group Reporting project grouping field
bxp control options
strProject_ShowPrice Control setting to use the costing aspects of a project
strProject_ShowProposalPrice Control setting to allow Project owners add Proposal Price but hide from resources delivering the project.
strProject_ShowPriority Control setting to allow resources delivering elements see priorities
strProject_ShowIssueTimeFrame Control setting to allow client views see Service Level Agreement time frames.
strProject_ShowProposedWorkingTime Control setting to use the proposed time engine. (useful when delivering a project to hide the proposed times).
strProject_ShowActualWorkingTime Control setting to use the actual delivered working time. (useful to hide when delivering only a proposal)
strProject_ShowCustomerProducts Control setting to allow only projects where a client has a contract for an agreed project.
work control options
strProject_Preassigned Enable / disable the task preassigned engine
intProject_PreassignedTo If preassigned is used, to whom the tasks are preassigned.
intProject_TeamId
intProject_TeamMemberId
bxp notification options
strProject_OnProjectCloseNotify When a project hits milestones or is completed, should a notification be sent?
strProject_EmailOnUpdate
intProject_MailAccountId To which email addresses should notifications be sent.
Project task creation limitations
strProject_GeneralOrCustomer
strProject_PreventByWarranty Control setting to only allow projects if the customer has a product in warranty
Microsoft fields
Areas Impacted The Areas Impacted field contains examples of areas that could be affected by a proposal, as selected in the Areas Impacted lookup table, which is shipped with Microsoft Project Server and can be modified to reflect the organization’s specific areas. This field is controlled by the workflow.
Assumptions The Assumptions field contains key assumptions for the current proposal. This field is controlled by the workflow.
Business Need The Business Need field is used to specify the business requirement for the current proposal. When you add information, be sure to be as specific as possible. This field is controlled by the workflow.
Committed Planned End Date The Committed Planned End Date field specifies the finish date of the project as committed to in a Portfolio Selection Scenario during resource constraint analysis.
Committed Planned Start Date The Committed Planned Start Date field shows the beginning date of the project as committed to in a Portfolio Selection Scenario during resource constraint analysis.
Committed Portfolio Selection Decision (Cost) The Committed Portfolio Selection Decision (Cost) field shows the result of a cost constraint analysis on a project. You can choose Selected, Unselected, Forced-In/Out, or Custom Forced-In/Out.
Committed Portfolio Selection Decision (Schedule) The Committed Portfolio Selection Decision (Schedule) field shows the commitment date of a Portfolio Selection Scenario as determined during schedule constraint analysis.
Committed Portfolio Selection Decision Date (Cost) The Committed Portfolio Selection Decision Date (Cost) field shows the commitment date of a Portfolio Selection Scenario as determined during cost constraint analysis.
Committed Portfolio Selection Decision Date (Schedule) The Committed Portfolio Selection Decision Date (Schedule) field shows the result of a schedule constraint analysis on a project. You can choose Selected, Unselected, Forced-In/Out, or Custom Forced-In/Out.
Compliance Proposal The Compliance Proposal field indicates whether the current proposal is for a project that helps meet a compliance goal, that is, whether the project is required by law, regulation, or other requirements.
Goals The Goals field contains the measurable goals of the current proposal. This field is controlled by the workflow.
Post Implementation Review Date The Post Implementation Review Date field indicates when the Post Implementation Review meeting was or will be held. This field is controlled by the workflow.
Post Implementation Review Notes The Post Implementation Review Notes field stores review meeting notes or a link to a meeting notes publication for the post-implementation review. This field is controlled by the workflow.
Primary Objectives The Primary Objectives field contains the primary objectives for the current proposal, as selected in the Primary Objective lookup table, which is shipped with Microsoft Project Server and can be modified to reflect the organization’s specific objective statements. This field is controlled by the workflow.
Project Departments The Project Departments field contains the name of the department with which the selected project is associated, as selected in the Department lookup table, which is shipped with Microsoft Project Server and can be modified to reflect the organization’s specific department names.
Proposal Cost The Proposal Cost field stores the estimated cost for the proposed project. This field is controlled by the workflow.
Proposed Finish Date The Proposed Finish Date field contains the estimated end date for the current proposal. This field is controlled by the workflow. dteProject_End Also used in menu listing to only show relevant active projects.
Proposed Start Date The Proposed Start Date field contains the estimated beginning date for the current proposal. This field is controlled by the workflow. dteProject_Start Also used in menu listing to only show relevant active projects.
Workflow Phase Name The Workflow Phase Name field specifies the current workflow phase for a selected project. A phase represents a collection of stages grouped together to identify a common set of activities in the project life cycle. Typical workflow phases are Create, Select, Plan, and Manage, although these phase names may be customized. This field is a component of the Microsoft Project Server workflow framework.
Workflow Stage Info The Workflow Stage Info field describes the current workflow stage for a selected project. A stage represents a single step within a project life cycle, and one or more stages can make up a workflow phase. This field is a component of the Microsoft Project Server workflow framework.
Workflow Stage Name The Workflow Stage Name field specifies the current workflow stage name for a selected project. A stage represents a single step within a project life cycle, and one or more stages can make up a workflow phase. This field is a component of the Microsoft Project Server workflow framework.
Workflow State The Workflow State field indicates a selected proposal or project’s current workflow state—for example, Waiting For Approval or Completed. This field is a component of the Microsoft Project Server workflow framework.
Retrieved from ‘https://www.bxpsoftware.com/wixi/index.php?title=Combining_bxp_and_Microsoft_Project&oldid=7550’