| | | | | | | | | | | | | | | | | | | | Deltek for Professional Services 1.1.3 Release Notes |
| | | | | | Last Updated: October 27, 2017 |
| | | | | Welcome to the Deltek for Professional Services 1.1.3 Release Notes, which describe the new features and enhancements introduced in this release. |
| | | | | | | | | | Contents of Release Notes
These release notes address all of the modules associated with DPS 1.1.3, some of which your firm may not use. Skip the sections that do not apply to your implementation of DPS. |
| | | | | | | | | | | | | | Microsoft Outlook Add-in | Deltek Options
The Deltek Settings option has been removed from the Deltek group in the Outlook ribbon and in emails. In its place is the Account Information option. Previously, you clicked Settings to access the Account Information option. | My Stuff >> Timesheet | Updated Electronic Signature Lines
The name of the employee who submitted the timesheet and the date and time when it was submitted now display above the Signed line. The name of the employee who approved the timesheet and the date and time when it was approved now display above the Approved line.
The changes to the Signed and Approved lines display when: Employee Signature Required is set to Yes on the Option tab of Time Settings.
Use Time Approvals is set to Yes on the Time Approvals tab of Time Settings.
Employee Signature Required is set to Yes on the Option tab of Expense Settings.
Use Expense Approvals is set to Yes on the Approvals tab of Expense Settings.
If the above options are not selected, the report displays the employee name below the Signed and Approved lines.
These changes display in the following reports: Detailed Timesheet Report Summarized Timesheet Report
Summarized Expense Report
Timesheet Audit Detail (when the Include Signed/Approved report option is selected)
| Utilities >> Integration and Imports | Firm Number Added to the Contacts Import
When you import contacts into DPS from a .CSV file, you can now include a firm number to associate each contact with a firm in DPS.
How the import process handles the linking of contacts to firms depends on the following:
Whether or not the CRM Plus module is activated. If CRM Plus is activated, whether or not you have enabled lead qualification on the CRM Plus Settings form (Settings > CRM Plus). If you have enabled lead qualification, whether or not the status of the individual contact is New Lead, Qualified, or Disqualified.
If Lead Qualification Is Not Enabled
If the CRM Plus module is not activated, or if that module is activated but lead qualification is not enabled, one of the following occurs for each contact in the import file:
If your import file includes a valid DPS firm number for a contact, the contact is automatically associated with that firm. If the firm number included for a contact in the import file does not yet exist in DPS and you also included a firm name for the contact, the import process creates a new firm record using the imported number and name, and associates the contact with that firm. If the firm number included for a contact in the import file does not yet exist in DPS and you did not include a firm name for the contact, the contact is imported without an associated firm. If no firm number is included for a contact in the import file but a firm name is included, the import process searches for an existing firm with that exact name. If one is found, it associates the contact with that firm. (If multiple firms with matching names exist, the contact is associated with the first such firm that is found.) If one or more firm names in the import file do not match existing firms, the import process displays a list of those firm names so you can select the ones for which you want new firm records added. If no firm number is included for a contact in the import file and you did not include a firm name for the contact, the contact is imported without an associated firm.
If Lead Qualification Is Enabled and the Contact Is Qualified
If lead qualification is enabled, the import process handles firm numbers for qualified contacts exactly as described above.
Note that DPS considers a contact qualified if either the import field that is mapped to the Qualified Status field contains Qualified or if no value is imported for the Qualified Status field.
If Lead Qualification Is Enabled and the Contact Is a New Lead
If lead qualification is enabled, one of the following occurs for each contact in the import file for which the import field that is mapped to the Qualified Status field contains New Lead:
If your import file includes a firm number for a contact, you receive an error message indicating that the contact cannot be associated with the firm because the contact has not been qualified. If that occurs, the contact is not imported. If no firm number is included for a contact in the import file, the contact is imported without an associated firm.
If Lead Qualification Is Enabled and the Contact Is Disqualified
If lead qualification is enabled, one of the following occurs for each contact in the import file for which the import field that is mapped to the Qualified Status field contains Disqualified:
If your import file includes a valid DPS firm number for a contact, the contact is automatically associated with that firm. If the firm number included for a contact in the import file does not yet exist in DPS and you also included a firm name for the contact, the import process creates a new firm record using the imported number and name, and associates the contact with that firm. If the firm number included for a contact in the import file does not yet exist in DPS and you did not include a firm name for the contact, the contact is imported without an associated firm. If no firm number is included for the contact in the import file, the contact is imported without an associated firm.
Related Changes for the Contacts Import
These additional changes were made to the Contacts import:
The DPS Primary Firm field is now Firm Name. The DPS Firm Description field has been removed.
For qualified and disqualified contacts when lead qualification is enabled, the Firm Name field can be used to associate a contact with a firm. The same is true for all contacts when lead qualification is not enabled. For new leads when lead qualification is enabled, this field can be used to include a firm name or description in the contact record, as the Firm Description field was used previously, but in this case, the field is not used to associate the new lead with an existing firm.
Firm Number Added to the Opportunities Import
When you import opportunities into DPS from a .CSV file, you can now include a firm number to associate each opportunity with a firm in DPS.
If your import file includes a valid DPS firm number for an opportunity, the opportunity is automatically associated with that firm. If the firm number included for an opportunity in the import file does not yet exist in DPS and you also included a firm name for the opportunity, the import process creates a new firm record using the imported number and name, and associates the opportunity with that firm. If the firm number included for an opportunity in the import file does not yet exist in DPS and you did not include a firm name for the opportunity, the opportunity is imported without an associated firm. If no firm number is included for an opportunity in the import file but a firm name is included, the import process searches for an existing firm with that exact name. If one is found, it associates the opportunity with that firm. (If multiple firms with matching names exist, the opportunity is associated with the first such firm that is found.) If one or more firm names in the import file do not match existing firms, the import process displays a list of those firm names so you can select the ones for which you want new firm records added. If no firm number is included for an opportunity in the import file and you did not include a firm name for the opportunity, the opportunity is imported without an associated firm.
|
| | | | | | | | | | | | | | | | General | Defect 848955: When using the DPS Desktop application with Windows Authentication option selected, the login automatically used the user's Windows password but did not disable the User ID field. | Billing | Defect 856754: On the Expenses tab in Interactive Billing, when you transferred an accounts payable voucher, you received the following error: "Dynamic SQL generation is not supported against multiple base tables." | Hubs | Defect 849704: The Audit Trail - InfoCenter tables audit triggers had multiple Join to EM view instead of EMMain table which caused performance and blocking issues. | Hubs >> Projects | Defect 856250: If you tried to create a new phase for a project in the desktop application by copying an existing phase, the process indicator just kept spinning. Eventually, you received a timeout error. | Defect 854962: When loading a large number of records using the List view in the Projects hub, a timeout error occurred after approximately fifteen minutes. | Hubs >> Projects >> Planning | Defect 855935: When a user who did not have access rights to view cost rates and amounts updated and tried to save plan information on the Expenses tab or Consultants tab of the Projects hub (Plan mode), the save process indicator just kept spinning, and the message indicating that the save was complete didn't display. | My Stuff >> Expense Report | Defect 835298: This issue applies if you use an approval workflow for expense reports. When a stored procedure action was added in the Actions grid of the User Initiated Workflow form (in Settings»Workflow»User Initiated Workflows) for an expense report approval workflow, you received an "Incorrect syntax near the keyword 'ON" message when the stored procedure action executed. | My Stuff >> Timesheet | Defect 822847: When Autopopulate from Plan Assignments was set to Yes on the Options form for Time settings (Settings > Time > Options), an employee's labor code was not entered by default when they entered time. | Defect 853489: When an employee did not have a hire date entered on the Employment Details tab in the Employees hub, the Floor Check dialog box in Timesheets did not populate with any timesheets. You open the Floor Check dialog box by clicking Other Actions » Floor Check on the Timesheet form. | Payroll | Defect 849052: You received the following error message when you ran an adjustment or bonus payroll run if the Locale Method field was set to Follow Project Locale on the Payroll tab of Employees hub for any employee in the payroll run: "Column "RegHrsOverride' does not belong to the table. | Reporting | Defect 848463: The Project Earnings report used the active company as the basis for the computation for the ETC values instead of the company that was associated with the project plan. |
Resource Management | Defect 843038: When you opened Resource View and the current search results included many resources, it could take a long time to display the initial set of resources in the grid. There were also long delays when you scrolled the grid to the end of the current set of resources and the next set of resources was retrieved and displayed. | Transaction Entry | Defect 851354: When a journal entry’s transaction currency was different from the functional currency, and the transaction currency was not entered with precisely matched debits, a tolerance could occur. This was caused by rounding during the exchange from transaction currency to fuctional currency. | Utilities >> Integration and Imports | Defect 855837: When you ran the Project Assignments import process, it displayed a message that indicated the import was completed successfully, but no records were imported. |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
|
| |