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 78 Notes

The following items have been completed in this release.


Sprint Began: 3/1/2019     Sprint Ended: 3/31/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.

User Management (Case 30265)  ENHANCEMENT


User management has been enhanced. When a user account is set to Inactive, the email address is updated with the text "inactive." prepended to the account (inactive with a period). The prepend value ensures that system emails are not sent to inactive user accounts (inactive.bobSmith@test.org). If an account is re-activated, the "inactive." is removed from the email address, ensuring the user receives system emails.


Condition description for Email Templates (Case 32079)  ENHANCEMENT


In Email Template creation, the step description has been updated for Step 4 (Conditions). Previously this description simply stated: In This Step: Set up your conditions.

The statement has been updated with a more helpful description:

In This Step: What additional conditions would you like to have met for this Email Template to be triggered? Add one or more conditions below and they will be used to determine the criteria for when the template will be triggered. This allows for 'AND' as well as 'OR' Conditions utilizing the Condition Expression feature. Using the Label field on the Condition, you can combine trigger conditions into more complex expressions, overriding the default 'OR' behavior - for example (Condition1 AND Condition2) OR (Condition3 AND Condition4) OR Condition5.


Link to triggering form via Email Templates (Case 34438)  ENHANCEMENT


Email Templates have been enhanced. New field replace values have been added that make it easy to encode clickable links within your correspondence. The following new replacement values have been added to the field replacement function in Email Templates :

  • {AppURL} - Embeds a clickable link to the application which, when clicked, would go to the application homepage.
  • {LinkToTriggeringForm} - Embeds a clickable link to the application which, when clicked, would go to the dataform from which the email was triggered.


Case assignment (Case 35021)  ENHANCEMENT


The case system has been enhanced with a link for moving a case between workspaces. This enhancement includes:

  • A link that opens a dialog to select a new workspace (from detail page).
  • A soft error (SE_ValidateMoveCase) to validate the move and warn the user if fields are cleared (if the employee is not in the new workspace, a soft error is provided).
  • A business rule (MoveCase) to change the workspace (set new Assigned To based on case type and new workspace).

The Move Case rule is pre-configured to run at the appropriate time during the dataform save process.


 Triggerable fields (Case 35344)  ENHANCEMENT


The Dataform field, Workflow Channel, and email systems have been enhanced to allow for customization of triggering fields.

  • Dataform Field Admin: A Triggerable check box has been added to the dataform field admin that allows administrators to selectively mark dataform fields as "triggerable" fields. Only fields marked in this manner are available for selection as triggering fields or conditions in Workflow Channels or Email Templates.
  • Workflow Channels: The Triggering Field and Conditions areas, where workflow triggering is configured, have been updated to accommodate the Triggerable flag on dataform fields.
  • Email Templates: The Trigger Field and Conditions areas, where Email Template triggering is configured, have been updated to respect the Triggerable flag on dataform fields.
  • For system included workflows and templates where triggering fields are used as well as commonly used fields, a script has been created to set the IsTriggerable flag.
  • If a field has been previously configured as a trigger condition and for some reason is not marked as Triggerable in dataform field admin, a message is displayed: "The selected triggering field or one of the fields used as part of a triggering condition needs to have the "Triggerable" property set in Dataform Admin." For more information about this functionality or assistance configuring this for your installation, create an Extranet case.


Assume User (Case 35440)  ENHANCEMENT


The Assume User functionality in System Admin has been enhanced to alert system admins when they attempt to assume an inactive or expired user. The message is "This user is expired or inactive and cannot be assumed." Previously the system would hide the Assume User button for these individuals, which could be confusing.


Email Templates (Case 35912)  ENHANCEMENT


The Email template system has been enhanced to include user typeahead type fields in triggering conditions. This allows the configuring administrator to use a typeahead method when selecting the Trigger Value for a condition that is using a user datatype as the Trigger Field, so they no longer need to know or look up the User ID for use in a text field.

The typeahead fields perform in the following manner:

  • Typeahead returns user values (Last Name, First Name) for active users only.
  • Typeahead returns "(expired)" behind the user name if the user record is expired.


Workflow Channel and Email Template typeahead fields (Case 36247)  ENHANCEMENT


Workflow Channels and Email Templates have been enhanced to use typeahead fields when configuring triggering based on Lookup or Parent form type fields. Previously a text field was provided for use.

  • Typeahead fields were implemented for lookup fields and parent form fields on the Conditions step.
  • The typeahead allows you to select from a defined list for the field, or click into the typeahead and begin typing your selection.
  • The behavior of these typeahead fields closely mimics the field response of a lookup or foreign key field on a dataform.
  • Check boxes and HdrAction conditions do not use the new typeahead. They are still native select dropdowns.


HRPAPI_Users (Case 36920)  ENHANCEMENT


The HRPAPI_Users import has been enhanced to recognize the Active field in PrismHR. The import process updates the ClientSpace Pulse user record so that when users are inactivated in PrismHR, they are inactivated in Pulse.


ClientSpace Help (Case 37010)  ENHANCEMENT


Three new help items have been added to the user profile using video lightbox/guide technology:

  • Add Modules to your user profile (Guide): This guided walkthrough takes you step-by-step through the process of adding modules to your profile and teaches you how to put the modules you use most right at your fingertips.
  • Enable Out of Office for your profile (Guide): Walks you through setting up your out-of-office profile and helps you to configure a backup user to cover for you when you are away.
  • Personalizing your user profile (Lightbox): This 3-minute video provides an overview of the user profile, explaining at a high level how you can customize the profile to suit your specific needs.


Employee Portal Case Widget rebranding (Case 37065)  ENHANCEMENT


The Employee Portal Case Widget has been updated with styling to more closely match the Employee Portal application.


Client Service Workspace (Case 37101)  ENHANCEMENT


A new Client Services Department workspace has been added as a repository for cases and other records where a matching Client or Employee number cannot be found.


Client Locations: Salesforce API (Case 37110)  ENHANCEMENT


Business rules have been enhanced to include workspace creation logic when Organizations and Workspaces are updated from the Salesforce API.

These changes include:

  • New Client Master rule SetupClientProspect. Similar to CM.ProcessNewClient, the SetupClientProspect rule is configured to run AFTER ProcessNewClient. It is used in situations where an Org and Workspace already exist (typically via ProcessNewClient) but will set up other basic workspace forms. This rule is triggered when:
    • Client Master is added via the Salesforce API pipeline (hardcoded, cannot be configured via the rule 'Save Action' setting).
    • A Workspace already exists.
    • An associated Organization already exists.

When the rule SetupClientProspect is triggered, it will:

  • Attach the associated Organization to a Workspace.
  • Set the Org Primary Project.
  • If the Contract Type field is empty, sets the default value.
  • Configurable
    • Create Primary Location (if Primary Location exists, will skip).
    • Create Sales User Commission.
    • Create Collateral (if Collateral form exists will skip).
  • Default settings as scripted:
    • Pipeline: SalesforceAPI (new Pipeline added).
    • Create Primary Location checked.
    • Order '15' (after ProcessNewClient at '10').
    • Inactive.


Employee Portal (Case 37144)  ENHANCEMENT


The “Can we help” dialog in the Employee Portal has been enhanced with typeahead functionality for the employee name. When logged in as a worksite manager, the typeahead function filters the list of employees based on the characters typed. If no connection can be made to PrismHR to retrieve employee names, the field functions as a text field.


Dataform field properties (Case 37189)  ENHANCEMENT


A Cloneable check box has been added to table metadata, allowing fields marked as such to be cloned as part of a workflow channel. These include fields such as the Delete field on cloneable workflow tasks, allowing for the creation of notification tasks which then automatically delete themselves.


Employee Portal Case Widget (Case 37201)  ENHANCEMENT


The Employee Portal Case Widget has been enhanced to include more detailed information about the PrismHR user/employee logging a case. The case widget includes the configured cell phone (or work phone if unavailable) for the current user's employee detail in Pulse, as well as their configured work email. If this information is unavailable, the system attempts to retrieve information from the PrismHR payroll system. If none of this is available, the created case will include the login ID of the Employee Portal user that submitted the case.


Employee Portal Case Widget (Case 37231)  ENHANCEMENT


The Employee Portal Case Widget has been enhanced with more helpful error messages. The error message now displays: "Unfortunately, the service is currently unavailable. Please try again later. [Message ID: {Error Code}]"

For an explanation of the Error Code that accompanies the error message, refer to the following list.


Error CodeMeaningMessage
Error [10002](no "peo_id" or auth "key" in querystring)"Unable to validate User in ClientSpace, insufficient credentials provided. Please contact your ClientSpace Administrator."
Error [10003](no AppCode matching PEOID)"Unable to validate User in ClientSpace for PeoID '{0}'. Please contact your ClientSpace Administrator."
Error [10004](could not retrieve APIConfig by AppCode) "Unable to connect to obtain an API Configuration for validation. Please contact your ClientSpace Administrator."
Error [10005](could not obtain a LoginClient via APIConfig endpoint)"Unable to connect to obtain a PrismHR Login Client for validation. Please contact your ClientSpace Administrator."
Error [10006](could not obtain a LoginResponse object)"Unable to connect to PrismHR for validation. Please contact your ClientSpace Administrator."
Error [10007](obtained a LoginResponse but the errorCode != 0, bad login to PrismHR) "Unable to log in to PrismHR, Error = '{0}'. Please contact your ClientSpace Administrator and report this error."
Error [10008](successful LoginResponse from PrismHR but did not contain a PrismHRSessionID) "Unable to obtain a valid Session from PrismHR. Please contact your ClientSpace Administrator."
Error [10009] (no SignOnResponse when validating Token)"Unable to validate this User's Authentication Key, no response from PrismHR. Please contact the System Administrator of the system from which you are trying to log in."
Error [10010](obtained a SignOnResponse but the errorCode != 0, invalid Token)"Unable to validate User in PrismHR, Error = '{0}'. Please contact your ClientSpace Administrator and report this error."
Error [10011](not a valid TPA user)"This User or your Server is not configured for Single Sign On in ClientSpace. Please contact your ClientSpace Administrator."
Error [10012](Exception, loglevel2, bad endpoint)"Unable to validate User in ClientSpace, a severe error occurred during processing. Please contact your ClientSpace Administrator and report error '{0}'"
Error [10013](Exception, loglevel1, bad endpoint)"Unable to validate User in ClientSpace, a severe error occurred during processing. Please contact your ClientSpace Administrator and report error '{0}'"
Error [10014](Exception, but no APIConfig available)"Unable to validate User in ClientSpace, a severe error occurred during processing (no API Configuration form). Please contact your ClientSpace Administrator."
Error [10015] (ProcessTrustedLogin failed)"Unable to log in to ClientSpace. Please contact your ClientSpace Administrator."



Salesforce API (Case 37775)  ENHANCEMENT


The Salesforce API has been enhanced with the following functions:

Import/Export of FK mappings to Org and Contact forms

The API was enhanced to translate Organization and Contact foreign key fields into related account fields in Salesforce. For example, if there is a foreign key to the Organization on the Client Master, the Salesforce API can now be configured to take the foreign key to the Org, look up the Salesforce objectID using this key, and update the appropriate Salesforce object.

Import - Convert multi-lookup formats to the appropriate system (!.!x!.!y!.! to x,y and x,y to !.!x!.!y!.!)

The API was enhanced to convert values stored in Salesforce picklists into valid multi-lookup content in ClientSpace. The import configuration compares the Salesforce data to the ImportID of the lookup record to find the matching code value(s) to be stored in the multi lookup field.

Import/Export, decimal datatype fields should be 'sforce.soapType.sxddouble' type:

Resolved an issue where decimal or money values exported to Salesforce would not maintain the proper formatting. Decimal values now maintain appropriate formatting when exported to or imported from Salesforce.



34530

Removing Client Template removes too many users

Resolved an issue in which removing a user from a Client Template inadvertently removed other workspace access from the user that had been manually added to their account. The system now records that the user access has been added from the template, and when the user is removed from the template, the system uses this flag to determine if the workspace should be removed.

34645

Case Notification Email Template cleanup from R71

Removed deprecated Email Templates CSCINT and CSEXT from the system. Replaced the templates with configurable Case Email templates. Deprecated the related inactive business rule on the Case SendNotifications.
36074Remove default task category

Removed the deprecated functionality of setting a default task category by dataform from the dataform admin area.

36697Show Attachments on Email AdminResolved an issue where email attachments were not available either through the Notifications dashboard or the Email Admin control panel. The system now displays a paperclip in the Notifications inbox and an Attachments Action item in Email admin that allows access to the email attachments.
37043Deprecate unused Incident Clone Keys

The following Incident clone keys and related code have been deprecated from the system:

  • COI_Approve_Email
  • COI_Approve_Fax
  • COI_Approve_Mail
  • FirstPayroll
  • IMP-->Complete 
  • PB_*  (any that starts with this)
  • PC_*  (any that starts with this)
  • PS_*  (any that starts with this)
  • biz_claim_MissingWCCode
  • biz_treatmentdetails_doctorapptreminder
  • LEADSCORE_DECLINED
  • LEADSCORE_IMPROVED
  • Benefits Renewal
  • CRMDupOrgReview 
37060Field display and multiple rules in NEXTResolved an issue for configured field displays when multiple field display rules were configured for the same SOURCE field. Previously only one of the rules was followed. The system now follows each of the configured field display rules. The system also validates the rules on Save to ensure that conflicting rules are not created.
37063Unable to clear values in primary or secondary trigger fields on business rules

Resolved an issue where the system would not allow the page to be saved if you attempted to clear existing trigger values from a business rule. The system now allows you to clear both primary and secondary trigger fields.

37077Set pipelines for Business Rules

Resolved an issue where Cases could be created with a null (or 0) Case Number, due to several business rules being created without appropriate pipelines in place.

37116% Search on Custom Logic Rule Quick search is brokenResolved an issue where the quick search on Dataform Name or Dataform from the Custom Logic Rules SysAdmin control panel would return no results.
37145Core change for defaulting Time Tracker CategoryAdded code that will allow the default time tracking category to be set when creating a time tracking record from a task.
37284Case Escalation

Resolved an issue in Case Escalation when a case escalation record with a matching case type and category cannot be found. The system would ignore an escalation record that matched only on priority. 

37317Workspace groupsDeprecated the classic interfaces for Workspace Groups functionality and replaced with new code that performs the same function.
37482Configure import field error

Resolved an issue where canceling out of field import mapping without saving would cause an exception. This would occur when a user attempted to add a new record but then decided to cancel without saving. Clicking X or Cancel would cause an application error.

37541Application error while trying to create Workflow Channel

Resolved a bug when adding conditions (Step 4) to a scheduled workflow channel caused an error.

37545Cannot save Template Task (Classic)

Corrected an issue in Classic when saving a Template Task caused an error and the task was not updated.







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