Access to the DPS SOAP-based API is now controlled with a role-based security setting. To enable or disable SOAP API access rights for a role, use the Allow Access to SOAP API check box on the General tab of the Roles form in Settings » Security » Roles in the desktop application. This setting does not affect access to the DPS REST-based API.

 

When DPS 1.1.17 is installed, the Allow Access to SOAP API check box is automatically selected for all existing roles. When you create a new role in 1.1.17 and going forward, the Allow Access to SOAP API check box is not selected by default for a role.

Defect 1026431: When you transferred billing expenses in Interactive Billing that had wire or direct debit fees (from AP Payment Processing), no general ledger transaction was created for the cash-basis side.

Defect 1033070: When a TDM file that contained an apostrophe in its name was uploaded and saved on the Files and Links tab, a 401 error (Unauthorized: Access is denied due to invalid credentials) displayed if you clicked the link to open the file.

Defect 1033011: When you selected Washington in a State/Province field in any hub, if you had not first selected United States in the Country field, the State/Province field changed to Western Australia when you moved off the State/Province field.

DPS now uses the WAU code for Western Australia instead of WA.

Defect 1023650: When opened from the Projects hub, the Employee Card displayed as a blank page.

Defect 1030952: The Employees hub would not load when the CRM module was not installed.

Defect 1035058: When you added a new project in the browser application by creating it from an existing project that was originally created in the desktop application, and you selected the option to copy the existing project's plan, two plans were created for the new project. You would see both plans listed if you selected the new project in Project View, and you would see duplicate assignments in Resource View for resources assigned to the new project.

Defect 1023316: If the Primary Client, Project Manager, and Principal fields in the Projects hub were locked using Screen Designer, the fields were not locked on the Edit Project Structure form when you were adding a new project. Primary Client appeared to be, and was, available for entry. Project Manager and Principal appeared to be locked, but you could double-click in the field and select an entry.

Defect 1030861: In some cases when a user's security role was set up with access to projects, and that acces was restricted by settings in the Record Level View or Record Level Update fields on the Record Access tab of the Roles form in Security Settings, the user received an error beginning with text similar to the following when they tried to work in the Projects hub: "The Multi-part identifier 'LEVEL.ProjMgr'...."

Defect 1030394: If you added a credit card charge to an expense report or entered an amount for a manually-added expense report line and then selected the Travel expense category, the credit card amount for the line item disappeared.

Defect 1024770: If Allow User to Edit was set to Yes on the Expense Categories dialog box in Settings » Expense » Categories, and you used the Account lookup dialog box to change the account for an overhead project category on an expense report, the new account saved correctly but the default account still displayed on the Expense Report form.

Defect 1023427: When Allow User to Edit was set to No for an expense category on the Expense Categories dialog box in Settings » Expense » Categories, you were still able to change the account on an expense report after you selected that category. 

Defect 1037375: You were able to save a timesheet containing a value for hours in the end date. This could cause duplicated timesheet master and approval workflow records.

Defect 1032045: When viewing a report with multiple drilldowns using a Chrome browser, you were not able to drill down to the second-level and subsequent report details.

Defect 1030950: When you ran the Labor Resource Planned and Actual report with Billing Amount selected in the Format field on the General tab of the Labor Resource Planned and Actual Options dialog box, the report displayed planned hours, not the planned billing amounts.

Defect 1021734: When you selected the Firms grid type for the Project List report and included the Firms - Is Client column or Firms - Is Vendor column on the report, that column correctly displayed Y or N, as appropriate, at the project level of the work breakdown structure (WBS). However, the column was blank for associated firms on report rows for lower-level WBS elements.

Defect 1035195: If Method was set to No labor billing on the Labor tab of the Reporting Default Terms form (Settings » Billing » Reporting Default Terms in the desktop application), the Project Detail report incorrectly showed no billing amounts for labor. However, if you viewed the same projects in Interactive Billing, they had labor billing terms and had labor transactions with hours, rates, and billing amounts.

Defect 1032040: When you display the plan for a project in the Projects hub, the first calendar period column on the Labor, Expenses, and Consultants tabs should default to the time period in which the current date falls. In some cases, that calendar period incorrectly defaulted instead to the time period in which the plan start date falls.

Defect 1032569: If you deleted a stage from the Opportunity Stage list on the Opportunity Stage Settings dialog box and clicked Save, the stage appeared to be removed but was not actually deleted from the database. If you displayed the Opportunity Stage Settings dialog box again, the stage was still in the list.

Defect 1033126:  The Application Access grid on the Record Access tab in Settings » Security » Roles did not contain a row for the Contacts hub when using a CRM database with Resource Planning enabled.

Defect 1034000: You received a "Column: Type does not exist" error when the employee records of new hires were imported from Talent Management to DPS and the employee system label was configured with the following settings on the Numbering tab in Settings » General » General System in the desktop application:

• The Auto Number Source field was set to Expression.

• On the Expression Configuration dialog box that displays from the Auto Number Format field, the Item field was set to EMAIICompany.Type.