Anonymous, bureaucrat, administrator
7,528
edits
Changes
no edit summary
= 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
= Structure =
So the first data structure is the Project table. Where in Microsoft Project desktop versions the data is stored in a file, the Professional and Enterprise versions can be stored in a centralised database.
bxp is able to mirror the key fields of the server thus allowing direct mapping solutions. There are more fields in bxp than Project for a number of key communications and customisation reasons.
[[Bxp_and_Microsoft_Project_-_Project_table_fields]]
A project in bxp has an Id which is used system wide rather than a name.
In Project there are then key elements that can be assigned to the project.
{| class="wikitable"! Microsoft NameType! 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 Task and task-timephased fields || 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 Task fields show task-related information and can be displayed in task views such as the project life cycle. Typical workflow phases are Create, SelectGantt Chart, PlanTask Sheet, and Manage, although these phase names may be customized. This field is a component of the Microsoft Project Server workflow frameworkNetwork Diagram views. || ||
|-
| Workflow Stage Info || The Workflow Stage Info field describes the current workflow stage Task-timephased fields show information for a selected projecteach task as distributed over its duration. A stage represents a single step within a project life cycle, and one or more stages These fields can make up a workflow phase. This field is a component be displayed in the timephased part of the Microsoft Project Server workflow frameworkTask Usage view. || ||
|-
| Workflow Stage Name Resource and resource-timephased fields || The Workflow Stage Name field specifies Resource fields show information for each resource, including summarized information about all tasks assigned to each resource. They can be displayed in resource views such as the current workflow stage name Resource Sheet and Resource Usage views.| || Resource-timephased fields show information for a selected each resource as distributed over the duration of resource availability on the project. A stage represents a single step within a project life cycle, and one or more stages These fields can make up a workflow phase. This field is a component be displayed in the timephased portion of the Microsoft Project Server workflow frameworkResource Usage view. || ||
|-
| Workflow State Assignment and assignment-timephased fields || The Workflow State Assignment fields show information for each assignment. They can be displayed in the sheet portion of the Task Usage and Resource Usage views and at the bottom of the Task Form and Resource Form views. You can change the assignment field indicates a selected proposal that appears at the bottom of the Task Form or project’s current workflow state—for exampleResource Form view by clicking in the area, Waiting For Approval or Completed. This field is clicking the Format tab, and then clicking a component of the Microsoft Project Server workflow frameworkcommand. || || Assignment-timephased fields show information for each assignment as distributed over its duration. These fields can be displayed in the timephased portion of the Resource Usage and Task Usage views.
|-
|}