Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
titlePwsTimeEntryProject
  • PwsTimeEntryProject
    • AllowAssignmentFlag: Boolean
    • AllowBookingFlag: Boolean
    • CanOpenFlag: Boolean
    • CloseDate: DateTime
    • DescriptionRequiredFlag: Boolean
    • OpenDate: DateTime
    • OpenFlag: Boolean
    • PmModuleEnabledFlag: Boolean
    • ProjectDescriptor: PwsProjectDescriptor
    • ProjectRateTypes: PwsProjectRateTypeSummary [???]
    • ProjectTaskTypes: PwsTaskType [???]
    • ProjectTasks: PwsProjectTask [???]
    • RoleCount: Int32
    • TaskCount: Int32
    • TimeCards: PwsTimeCardDetail [???]
    • Udf1Treatment: String
    • Udf2Treatment: String

Elements

 This structure contains key fields associated with a client 


Element

Data Type

Required?

Default

Description

Sample Data

AllowAssignmentFlag

Boolean

No

false



AllowBookingFlag

Boolean

No

false 



CanOpenFlag

Boolean

No

false 



CloseDate

DateTime

No




DescriptionRequiredFlag

Boolean

No 

false



OpenDate

DateTime

No




OpenFlag

Boolean

No

false



PmModuleEnabledFlag

Boolean

No

false



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


TaskCount

Int32

No


The number of tasks associated with the project


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. 


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. 


Usage Example(s)