NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm

Release 77 Notes

The following items have been completed in this release.

Sprint Began: 2/1/2019     Sprint Ended: 2/28/2019

We moved the cheese!

Mmmmm - Cheese! The cheese icon  denotes a change in functionality. So, when we move the cheese and change the way something works, you will know about it.

Certificate of Insurance report (Case 35343) ENHANCEMENT


The Certificate of Insurance report has been modified to use the report signature stored under System Admin > Branding > Reporting Signature. If this branding file has not been set or is removed, the system defaults to the previous method of using the Signature file stored in the custom images directory. This ensures that clients who are already using custom signature files are not affected.


Import External Source Linking Records for Third Party Integrations (Case 35455) ENHANCEMENT


The API system now has a supporting import that will import External Source Linking records into tblExternalSourceLinking. This imports NEW records only, and will not update existing records. The primary purpose of this import is to seed the external source linking record in preparation of implementing an integration (e.g., Salesforce).

This import is based on the following configurations:

  • Uses PEO staging form gen_ImportExternalSourceLinking
  • Rule CreateExternalSourceLink must be configured on form gen_ImportExternalSourceLinking
  • No soft/hard errors are available during the import process

This configuration imports the following five columns:

  • ClientSpaceTableName (ClientSpace Table, tblOrganization, tblContact, gen_Whatever, etc.) [Text]
  • ClientSpaceID (ClientSpace RowGUID for the ClientSpaceTableName table) [Text RowGUID]
  • fkAPIConfigurationID (API Config associated with this record) [PK]
  • ExternalObject (External Object Type, e.g., "Account") [Text]
  • SourceID (External Object ID) [Text]


PrismHR API (Case 36086) ENHANCEMENT


API functionality within the application has been updated to be compatible with version 1.15 of the PrismHR API. No API configurations in the application will be updated at this time. If your PrismHR installation has been updated to version 1.15 and you would like to update the API connection to take advantage of this, contact Professional Services.


HRPAPI_Users (Case 36605) ENHANCEMENT


Updated the HRPAPI_Users (ongoing) import to eliminate extraneous users from being imported from Prism. Prism users who are not Service Provider user types are not imported into Pulse via the HRPAPI_Users initial and ongoing imports.


Import configuration (Case 35461) ENHANCEMENT


Import Configuration has been enhanced to allow the Record Source Column to use the primary key (pkDataformID) of the record. When the record Source Column is set to use the primary key, only updates will be allowed. To insert records, the Record Source Column needs to be ImportID.


Email integration (Case 36232) ENHANCEMENT


The email integration function has been enhanced to include both an employee's work or personal email when determining the related employee to select when creating a case. This compares both the personal and work email addresses for a match. If multiple records are matched, the system selects the most recently updated active record based on Date Updated admin field.


Email add-in (Case 35529) ENHANCEMENT


The email add-in has been enhanced to include the organization name when selecting additional contacts as part of the process of creating activities in the system through the add-in. This helps to eliminate confusion where multiple contacts may have the same name, or where one person exists as a contact on multiple organizations.


Case discussions: Work or personal email (Case 36234) ENHANCEMENT


Case Discussions have been enhanced, allowing you to choose an employee's work or personal email when configuring an employee as a discussion recipient.

  • When an employee has only a work email, the recipient list displays Employee name and work email by default.
  • When an employee has only a personal email, the recipient list displays Employee name and personal email by default.
  • When an employee has both a work and personal email, the recipient list displays Employee name and work email by default. When the employee is selected as a recipient, the right pane of the selector provides the option of selecting either the work or personal email as the discussion recipient.
  • If no emails exist for the employee, the system displays the existing error message that states this Employee cannot be selected because there is no email.


Workflow Channels business rule (Case 35832) ENHANCEMENT


Workflow Channels have been enhanced with the _WorkflowTaskAutoComplete business rule, allowing a series of tasks to be automatically closed by a specified trigger event. This rule is designed to complete all tasks on the associated dataform that were cloned from a comma-separated list of Workflow Items configured as parameters on the business rule.

This rule contains three parameters:

  • WorkflowItemList (required) - Insert a comma-separated (no spaces) list of Task Workflow Channel Item IDs. These can be retrieved by going to System Admin > Workflow Channels and opening the appropriate workflow channel. The associated Item IDs can be found in the leftmost column of the Workflow Items in this Channel list at the bottom of the page. Subsequent child items are also closed if their IDs are added to this list. 
  • SendNotification (optional) - Select this checkbox to ensure that notifications are sent when tasks are automatically closed by this rule.
  • EntireWorkspace (optional) - This rule closes task workflow items associated with the triggering dataform by default. Selecting this checkbox allows the rule to close task workflow items on any dataform in the workspace whose ID has been added to the WorkflowItemsList.


Workflow Channels user datatypes available as conditions (Case 35859) ENHANCEMENT


Workflow Channels have been enhanced to allow workflow triggering from User fields on dataforms. These user fields can be used both as the primary trigger for a workflow as well as additional triggering conditions so that when a user field changes, such as the Payroll Specialist, the system can route that change to an internal team member to execute a business process. 


 System Admin fully converted (Case 36664) ENHANCEMENT


ClientSpace Classic code has been deprecated. The following classic system admin interfaces have been removed from the system:

  • Classic: Email Admin
  • Classic: Email Integration/Email Template
  • Classic: Exception Log
  • Classic: Field Audit Trail/User Audit Trail
  • Classic: Scheduled Process Admin
  • Classic: Time Tracker


Dataforms subscriptions (Case 29035) ENHANCEMENT


Dataform subscriptions have been enhanced to allow subscription notifications to be sent to:

  • Internal users only
  • External users only
  • Both internal and external users

These notification options are available from the Address step in Email Templates when the Include Dataform Subscribers as 'CC' Recipients checkbox is selected.

Saved Search actions (Case 37059) ENHANCEMENT


Saved Search functionality has been enhanced from a single button (to save a search) along with the option to restore the system default, which also removes any search customization.


Immediate Supervisor (Case 37244) ENHANCEMENT


The IMPORT_user*.csv import has been enhanced to include Immediate Supervisor and Default workspace. These fields will be imported on both insert and update for internal users, and updates to external users (External users cannot be created via import).




34259Stopping Timer clears unsaved field changes on Time records

Resolved an issue when creating a time tracking record from a dataform with unsaved changes. Saving the time tracking record would lose the unsaved dataform changes.

34885Email Integration Email Templates do not respect Publish flagResolved an issue in which Email Integration was not respecting the Publish/Unpublish flag for email templates when generating automatic email responses on dataform creation.
36735List refresh removes Inactive list item formattingResolved an issue where a list refresh could cause the Inactive record formatting (Bold and italicized) to be removed from the inactive records.
36909Notification WidgetCorrected an issue where the CanResize flag of the Notification widget was set to True, which the widget does not support, causing unexpected behavior in the widget when an administrator would resize it in a layout.
36914Email Template Recipient Address is case sensitiveResolved an issue where the duplicate checking was case sensitive. For example, billq@prismhr.com and Billq@PrismHR.com and billq@Prismhr.com were all seen as different email addresses. This has been changed so that it is no longer case sensitive.
36922Task link is brokenCorrected an issue with several misconfigured system templates that caused unexpected behavior.
36990Salesforce API issueResolved an issue when importing an Opportunity from Salesforce. If an associated Organization did not exist in ClientSpace, the process would attempt to create that Organization to house the Opportunity data and fail. In some cases, the ID used to retrieve the Account was incorrect. This would only occur with a very specific setup in which the Opportunity was only mapped to Organization and Org Other Info.
37009Remove Case Category metadata dataform from WorkspacesRemoved the Case Category metadata dataform from any workspace. This form is only accessible via the Case Category Lookup group. Fixed the Workspace Type Multiple Select dataform type, removing the ability to use the Form Searchable checkbox. A javascript error would be thrown when loading the search page for the dataform, and the loading spinner would spin endlessly.
37011Error in Workflow ChannelResolved an issue where the Workflow Channel Name typeahead validation would break in the presence of special characters, causing a 401 Unauthorized error during the validation call.
37068Orgs and Workspaces not coming overResolved an issue where the Assigned to User on the Organization (OwnerId in Salesforce) was not being created on new Account inserts, causing the Salesforce export to fail for certain Organizations and Workspaces.
37085Task badge count incorrectResolved an issue with the Task Action item badge counter that displayed an incorrect value for inactive tasks under certain circumstances.
37152Case Type changesResolved an issue where the Backup User field on the Client Service Case Type dataform was set to use an incorrect role, which left the backup user field blank so that case type changes could not be saved.
37155Error when saving a workflowResolved an issue where saving changes to a child item of a scheduled workflow would cause the system to generate an unspecified server error.
37184Salespeople and underwriting cannot add surcharges in the pricing console.Resolved an issue where the Add Surcharges dialog would not respect associated contract type, causing surcharges to be missing from the add dialog.  The add dialog now properly presents all active surcharges with no contract type or with a matching contract type when Hide in Surcharge Quick Selector is not selected.
37198Client Visit Search on TemperatureResolved an issue where the Temperature filter of the Client Visits module would cause an error to be thrown and not filter the list properly.
37202Unable to access the notes in the Activities section of the workspace.Resolved an issue when opening activities from the Activities Workspace Landing Page widget would throw an error.
37215Pricing Console surcharges

Removed the double-click functionality for Surcharges Add dialog. Surcharges can still be selected by clicking the Select checkbox.

37264Home with Cases (Classic)

Updated the Home with Cases dashboard to replace the deprecated Messages quadrant with an Events quadrant in the classic interface.

37314"Audit This field" option does not save in Dataform Admin NEXTCorrected an issue which did not allow the "Audit this Field" checkbox to be saved. Checking the box and saving the record would clear the checkbox. The system now properly saves this flag, and triggers field auditing for the checked records on dataform save.







NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm