SubmitOlapEprExport
Rate Limiting
In order to protect our servers from inadvertent service overuse or intentional attack, and to fairly distribute services to all our customers, we have implemented a rate limiting algorithm. When fully deployed, this new algorithm will cause services to either succeed with new warnings or fail with new errors when services are consumed at too high a rate. Programs that consume Projector services should be enhanced to handle rate limiting errors so that they can continue functioning properly. For more information please visit: Projector Rate Limiting Behavior.
Request
The service request contains:
Name | Data Type | Required? | Default Value | Discussion |
---|---|---|---|---|
CostCenterReferenceSystemId | string(20) | no | Limit exported records to this cost center and every cost center under it. If not specified, then all cost centers are exported. | |
ActivitySinceDate | date | yes | Only include engagements with activity on or after this date. | |
CutoffDate | date | yes | Last date for which actual data is used. After this date projected data is used. | |
BillableOnlyFlag | boolean | no | true | If true then ony records for billable projects are exported. |
Include Requests Flag | boolean | no | false | If true then include pending requests in projected person hours. |
IncludeUnnapprovedFlag | boolean | no | false | If true, then include submitted (but unapproved) time and time off. |
IncludeUnnapprovedExpensesFlag | boolean | no | false | If true, then include expense on submitted (but unapproved) expense reports. |
ProjectLevelFlag | boolean | no | false | If true, then return one record per project. If false, then return one record per engagement. |
ReportingCurrencyCode | string(3) | yes | ||
UseWholeDayRdcFlag | boolean | no | false | If true, then RDC is fully allocated to each project. |