Page Comparison

AllowAssignmentFlag

Boolean

No

false

If set to 'true', the project allows for roles to be assigned to a resource

true

AllowBookingFlag

Boolean

No

false 

If set to 'true', the project allows for scheduled hours

true

CanOpenFlag

Boolean

No

false 

If set to 'true', the project can be opened from the old employee portal

false

CloseDate

DateTime

No

The close / end date of the project

DescriptionRequiredFlag

Boolean

No 

false

If set to 'true', descriptions are required on time cards associated with this project

false

OpenDate

DateTime

No

The start / open date of the project

2018-01-01T00:00:00Z

OpenFlag

Boolean

No

false

If set to 'true', the project is currently open for time

true

PmModuleEnabledFlag

Boolean

No

false

If set to 'true', project management is enabled in this installation and, detailed task management can be enabled for the project

true

ProjectDescriptor

PwsProjectDescriptor

Yes

This structure contains key fields associated with a project

ProjectRateTypes

PwsProjectRateTypeSummary [???]

Yes

The rate types associated with the project

ProjectTaskTypes

PwsTaskType [???]

Yes

The task types associated with the project

ProjectTasks

PwsProjectTask [???]

Yes

The tasks associated with the project

RoleCount

Int32

No

The number of roles associated with the project

1

TaskCount

Int32

No

The number of tasks associated with the project

1

TimeCards

PwsTimeCardDetail [???]

Yes 

This structure contains the complete set of information about a time card. 

Udf1Treatment

String

No

User Defined Treatement for the first UDF associated with the time card:

• "R" for required – UDF should be displayed and requires a value. Yes/no UDFs never have this status, and always have a value of yes or no (checked or unchecked). There’s no third (i.e., null) state for yes/no UDFs.
• "A" for available—UDF should be displayed and null is a valid value (except for yes/no; see above)
• "N" for unavailable—This calls for displaying the UDF as read only if populated, and not displaying it at all otherwise. In the case of yes/no, only a value of yes/checked should cause the UDF to be displayed. <N> could be (a) UDF inactive flag = T, (b) Cost UDF expense type setting: Not available, or (c) Not enabled via Enterprise Configuration for a certain engagement type. 

A

Udf2Treatment

String

No

User Defined Treatement for the second UDF associated with the time card:

• "R" for required – UDF should be displayed and requires a value. Yes/no UDFs never have this status, and always have a value of yes or no (checked or unchecked). There’s no third (i.e., null) state for yes/no UDFs.
• "A" for available—UDF should be displayed and null is a valid value (except for yes/no; see above)
• "N" for unavailable—This calls for displaying the UDF as read only if populated, and not displaying it at all otherwise. In the case of yes/no, only a value of yes/checked should cause the UDF to be displayed. <N> could be (a) UDF inactive flag = T, (b) Cost UDF expense type setting: Not available, or (c) Not enabled via Enterprise Configuration for a certain engagement type. 

A