Release 121 Notes

R121 Sprint: 10/5/2022 to 11/04/2022. To learn about product features that you may not recognize, contact ClientSpace Professional Services.

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Click to view the R121 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for ClientSpace Professional Services.

Sprint 10/5/2022 to 11/04/2022
Upgrade groups	Date of upgrade	Tentatively occurs on
Group 1	First Tuesday of the month	November 8, 2022
Group 2	Second Tuesday of the month	November 15, 2022
Group 3	Third Tuesday of the month	November 22, 2022

ClientSpace Premium

Case	Enhancement
56830	Added _SetFieldFromLookupMetadata Business Rule Method A new _SetFieldFromLookupMetadata business rule method has been added that sets a dataform field value on the triggering dataform from a field value on an associated metadata dataform when a lookup is selected that contains metadata. The source and target data types must be compatible. Metadata field to Target field validation prevents you from specifying mismatched data types. Note: If there is no metadata available when the rule is triggered, the rule is skipped. See Business Rule Methods.
57230	Added Ability to Insert Custom Salesforce Objects Previously, you could update fields on Salesforce objects with field data from ClientSpace dataforms but you could not create new Salesforce objects from ClientSpace dataforms and fields. Now, you can use the Salesforce Export API (SFORCE_export_mapping*.csv) to map ClientSpace forms and fields to Salesforce objects and fields and export the data from ClientSpace to Salesforce to create new Salesforce objects. See Inserting Custom Salesforce Objects.

Case

Enhancement

56830

Added _SetFieldFromLookupMetadata Business Rule Method

A new _SetFieldFromLookupMetadata business rule method has been added that sets a dataform field value on the triggering dataform from a field value on an associated metadata dataform when a lookup is selected that contains metadata. The source and target data types must be compatible. Metadata field to Target field validation prevents you from specifying mismatched data types.

Note: If there is no metadata available when the rule is triggered, the rule is skipped.

See Business Rule Methods.

57230

Added Ability to Insert Custom Salesforce Objects

Previously, you could update fields on Salesforce objects with field data from ClientSpace dataforms but you could not create new Salesforce objects from ClientSpace dataforms and fields. Now, you can use the Salesforce Export API (SFORCE_export_mapping*.csv) to map ClientSpace forms and fields to Salesforce objects and fields and export the data from ClientSpace to Salesforce to create new Salesforce objects.

See Inserting Custom Salesforce Objects.

General Enhancements

Case	Enhancement
48491	Added Ability to Rename Single Files on the Docusign Email Template Previously, you could only use "rename" functionality on the Docusign Email Template to prepend an identifier to an original document name when one of the following settings was applied on the Attachments tab of a Docusign Email template: A mail merge document was identified in the Mail Merge field. The Merge All Documents checkbox was selected (to combine all single documents into a single merged document). This functionality has now been enhanced to allow renaming of returned and signed single documents by typing an identifier in the Rename column located in the Add section on the Attachments tab. If a value is entered in the Rename column, the returned file name will have the following format: COMPLETED_{Rename field value}_{Original File Name}. If no value is entered in the Rename column, the returned file name has the following format: COMPLETED_{Original File Name}. Note: The Renamed Signed Document field label has been changed to Renamed Signed Merge. Mail Merge and Merge All Documents? rename functionality still works the same. If the Mail Merge field contains a value or the Merge All Documents? field is checked and you enter a value in the Rename Signed Merge field, the signed and returned merge document will be renamed using the following format: COMPLETED_{Renamed Signed Merge field value}_{Original File Name}. See Step 5: Attachments.
50642	Added the Ability to Set a Workflow Item Multi-Lookup Value from Another Multi-Lookup Field You can now create a workflow item that sets a multi-lookup field value on a dataform or task from another multi-lookup field when triggered. Also see related Case# 58084. Note: Multi-lookup fields from a multi-form only display if it is the triggering form. A multi-lookup field must be set as a workflow cloneable field in Dataform Admin (System Admin > Advanced > Dataform Admin) in order to display as an available workflow item field. Multi-lookup fields from other forms must also be within the same workspace as the triggering form and they must all have the same Lookup Group. Three options are available on the Workflow Channel Content tab when you click next to a lookup field: None: This is the default initial state. When the workflow item triggers, any multi-lookup field set to None will be blank on the new or updated dataform or task. The only exception is when the field is a required field (designated by red text). You must set a value for required fields. Specific Value: When the workflow item triggers, the multi-lookup field value that you select will be set in the corresponding field on the new or updated dataform or task. From a Field on a Form: When the workflow item triggers, the set value from the multi-lookup field of the form you select auto-fills the corresponding field on the new or updated dataform or task. The From a Field on a Form option is only available when there are multi-lookup fields on other forms in the same workspace that have the same Lookup Group. Note: Tabbed form multi-lookup fields have the following naming convention to help you determine where the multi-lookup field you are selecting is located: *<Dataform Tab Name> -- <Field Label>(FieldName). See the example image below showing two multi-lookup fields in the Field selection. The first field is located on the home form (i.e., the parent form). The second field is located on a tabbed extension of the parent form (i.e., is a child form of the parent form) and uses the aforementioned naming convention. See Step 2: Content.
58084	Added the Ability to Set a Workflow Item Lookup Value from Another Lookup Field You can now create a workflow item that sets a Lookup field value on a dataform or task from another Lookup field when triggered. Also see related Case# 50642. Note: Lookup fields from a multi-form only display if it is the triggering form. A Lookup field must be set as a workflow cloneable field in Dataform Admin (System Admin > Advanced > Dataform Admin) in order to display as an available workflow item field. Lookup fields from other forms must also be within the same workspace as the triggering form and they must all have the same Lookup Group. Three options are available on the Workflow Channel Content tab when you click next to a lookup field: None: This is the default initial state. When the workflow item triggers, any Lookup field set to None will be blank on the new or updated dataform or task. The only exception is when the field is a required field (designated by red text). You must set a value for required fields. Specific Value: When the workflow item triggers, the Lookup field value that you select will be set in the corresponding field on the new or updated dataform or task. From a Field on a Form: When the workflow item triggers, the set value from the Lookup field of the triggering form you select auto-fills the corresponding field on the new or updated dataform or task. The From a Field on a Form option is only available when there are Lookup fields on other forms in the same workspace that have the same Lookup Group. Note: Tabbed form Lookup fields have the following naming convention to help you determine where the Lookup field you are selecting is located: *<Dataform Tab Name> -- <Field Label>(FieldName). See the example image below showing two Lookup fields in the Field selection. The first field in the Lookup is located on the home form (i.e., the parent form). The second field is located on a tabbed extension of the parent form (i.e., is a child form of the parent form) and uses the aforementioned naming convention. See Step 2: Content.
56713	Enhanced DocuSign Failure Notifications The following new replacement fields are available for you to add to the Docusign Failure Notification template: {ProjectID}, {WorkspaceName} and {LinkToTriggeringRecord}. The {LinkToTriggeringRecord} replacement field adds a link to the workspace that generated the failure. Adding these fields can help troubleshoot where an error occurred. See Step 2: Content.
56834	Updated Multiple Task Drop Down Lists to Work the Same as Other ClientSpace Lookups Previously, any default lookup values that were set to auto-fill Category, Priority, Type and Workflow fields when adding a new Task record did not populate. Now these fields will auto-populate the default value on Add, if a default value is configured for the lookup. Additionally, any default values that were set to auto-fill these fields when adding a new Task record via an email template, workflow channel or custom link did not populate. Now, when a Category, Priority, Type or Workflow list value is added, changed, or removed in Lookup Details, the changes are reflected on the Task form and More search drop down lists. Triggered default values are also now being populated.
56942	Added Filtering by Filter Source to Multi-Lookup Field Configuration Previously, you could configure a multi-lookup field by Filter Value (i.e., a single value or a group of comma-delimited values in a text field) but not by Filter Source (i.e., values from another standard lookup field). You can now configure a multi-lookup by Filter Source. Once configured, dataform lookup fields display only the lookup values with filters that match the Filter Source on the dataform field configuration plus any lookup values in the lookup group that do not have a filter set. Note: You can configure a multi-lookup to filter by Filter Value or Filter Source, not both. If you enter both a Filter Value and a Filter Source, Filter Value will be ignored. The following validation is present on the Filter Source field related to multi-lookup fields: You cannot set another multi-lookup field as the Filter Source. (This includes a check to make sure you do not select the current multi-lookup field as its own Filter Source.) You can only set another standard lookup field as the Filter Source. You cannot use a field name that does not exist on the dataform as the Filter Source. If you change multi-lookup field filter settings after a user has already made a dataform selection using a value that no longer displays, their selection will be preserved. However, if they delete the selected value from the field, they will not be able to reselect it as it will no longer appear in the list of available choices. (This does not apply to the Lookup (core) and Lookup Type Ahead datatypes. For those datatypes, if the filter settings are changed, a user's selection may be cleared if the new filter settings no longer contain their selection.) See Advanced filtering: Using contents of another field and Filter Source.
57066	Enhanced Creating Email Integration Cases by Contact Process Previously, when the Email Integration scheduled process ran, the "From" email address from external emails were first compared to all employee email addresses (personal and work). If a match was found, a new Client Service case was created in the workspace of the associated employee. If a match was not found, contacts were searched for an email address that matched the "From" address and if found, the matching contact's project ID was used to identify the workspace for the new Client Service case. However, the contact on the newly created Client Service case was not updated with the contact information from the matching contact record. Now, ClientSpace automatically sets a contact on the newly created Client Service Case using the "From" email address from the matching contact record. Note: If the Always Use Default Workspace setting is set, the process described above for identifying the correct workspace is overridden and the Client Service case is always created in the default workspace. See Email Integration Processing.
57138/ 59442	Added Automatic Archiving of Business Intelligence Reports A new "Auto Archive BI Reports" scheduled process has been added that automatically archives reports that have not been run in a specified number of days (Archive Limit) based on the "Last Run Date". The "Auto Archive BI Reports" scheduled process is being distributed as "Active" with the following default settings in place. Default Archive Limit: 120 Default "Auto Archive BI Reports Scheduled Process Configuration": Frequency = 1, Frequency Type = Monthly, Next Run Date = End of the next month following this release, Next Run Time = 1:00 a.m. You can access archived reports from the Business Intelligence Admin dashboard and restore them. The following reports are exempt from archiving: Reports manually flagged for exclusion A Do Not Archive setting has been added to the Business Intelligence Admin dashboard (System Admin > Outputs > Business Intelligence) that allows you to flag reports that should never be archived. Widget reports Datasource reports Dashboard reports See Configuring the Auto Archive BI Reports Scheduled Process and Business Intelligence Admin Dashboard.
57618	Updated API Path for "LastDateWorked" on Inactive Employment API Import Map Header Detail Records With this release, the API Path for "LastDateWorked" will be updated to Employee/compensation/lastWorkedDate on inactive ongoing and initial Employment HRP API Import Map Header Detail records.
57678	Added the Ability to Exclude Inactive Records from Scheduled Workflows A new Include When Inactive checkbox has been added to the Channel tab of Workflow Channels configuration for Scheduled workflows. When the checkbox is checked, triggering of the scheduled workflow will occur for both active and inactive triggering forms. When the checkbox is unchecked, triggering of the scheduled workflow will only occur for active triggering forms. See Configuring Scheduled Workflows.

Fixes

Case	Issue summary	Resolution
57702	Create Link on an Organization Did Not Work After Clearing Hard Error	Previously, when you clicked any Create link on an organization, if a hard error displayed and you cleared it by entering the missing information and saving, the Create link remained disabled. Now, once you save the missing information, the Create link is available.
57742	Deleting a Workspace Not Deleting External Source Linking Records	Previously, when you clicked the Delete Workspace link on the workspace dashboard, associated external source linking records (System Admin > Imports > External Source Linking) were not being deleted along with the workspace. This issue has been corrected.