Smartstaff, administrator
3,723
edits
Changes
→Note on Vendor Changes
====New Rich Text Editor====
The new '''Rich Text Editor''' introduced in November 2024 will be enabled for everyone to ensure a secure editor experience. The classic rich text editor will be deprecated and permanently unavailable following the June 2025 upgrade. If the new rich text editor does not render as expected, it is likely related to browser caching. Reload the page (Ctrl + Shift +R on Windows). If that does not resolve the issue, clear the browser cache (Ctrl + Shift + Delete on Windows).
[[File:2025-02-ticket-167158-1.png|thumb|none|800px|The new '''<strong>Rich Text Editor''' </strong> is enabled for all clients.]]
<!-- 167158 - Enable New Rich Text Editor for All Users -->
<pre><!--hideifnotfound-->@fieldname.value@</pre>
<!-- 170020 - Copy of 170007 - Payment field issues -->
====February 20th 2025 (202502.03)====
* Fixed an issue where the enforced language setting (located at '''Global Settings ''' > '''Users Tab ''' tab > '''Default Personal Settings, ''') was not being enforced as expected in some scenarios.
<!-- 170033 - Copy of 169876 - Portal language issue when MFA is enabled -->
* Fixed an issue where some emails on hold went directly into the failed '''Failed''' tab and displayed the "Invalid address" error message Invalid address.
<!-- 170118 - Copy of 170028 - Failed Emails: Workflow Emails on Hold -->
====March 13th 2025 (202503.01)====
* Deprecated the Classic tab located under '''Global Settings''' > '''Branding''' tab > '''Colors and Styles'''. The '''Label Alignment''' setting remains available.
<!-- 119953 - Deprecate the branding, colors & styles, classic tab -->
* Updated the messaging for a batch update in progress so that it automatically hides a few seconds after the batch update completes.
<!-- 165645 - Hide batch update message after a few seconds -->
* Updated the '''Field Change History''' (found on Level 1 records under the '''Logs''' link) to include a "Source" column. This is useful for viewing where a change was initiated and for tracking changes that may not have been made directly by a user.
<!-- 165988 - Should field Change History include the Source value -->
* Added new variables to validate pages and word counts on documents uploaded to the multi-file and single file storage custom fields. For example, you can now use '''SmartCheck''' validation on application submissions to ensure a client uploaded a document that contains at least two pages of information or contains at least 100 words. File types that can be checked include Microsoft Word (.doc, .docx), Rich Text (.rtf) and Adobe Portable Document Format (.pdf). <br/>The syntax to retrieve this information from the uploaded files based on the field name is: <code>@field.pagecount@</code>, <code>@field.wordcount@</code>. <br/>The syntax to retrieve this information from the uploaded files based on the field ID is: <code>@#fieldid.pagecount#@</code>, <code>@#fieldid.wordcount#@</code>. <br /> <br /> '''Note:''' If there is more than one uploaded file, you will get an aggregate of pages and counts across all files. PDFs must contain searchable and selectable text. If using these variables in '''SmartCheck''' validation, custom field validation, browser scripts or comparisons, be sure to wrap the variables with the parse number syntax: <code>ssParseNum(@#fieldid.pagecount#@)</code>
<!-- 167042 - Add Page and Word Count Validation for Uploaded Word Documents -->
* Added a new option to exclude the date-timestamp from the file name on e-signature documents that are saved to an upload field after the signing process. To see the new setting, navigate to the "Special - Web Page View" custom field where the document is generated for e-signature. The new setting is called '''Append date-timestamp to signed document file name'''.
<!-- 167631 - E-signature downloaded file names -->
* Added the ability to specify the visibility of the "Special – Like Button Rating" custom field within SmartFields which is used to generate PDFs.
<!-- 168980 - Copy of 168047 - Like Button Rating does not have the ability to exclude from Smartfield -->
* Added new syntax to use the identity verification feature in DocuSign, allowing clients to request the recipients/signers verify their identity. <span data-teams="true">This includes options for ID verification using government IDs, bank IDs, phone authentication, access code authentication, and knowledge-based authentication.</span><br /><br />'''Note:''' Clients must configure workflows in their DocuSign account and update their existing Web Page Views with the new syntax, including the DocuSign identity verification workflow IDs. To learn more, read our article on identity verification for DocuSign: https://wiki.smartsimple.com/wiki/DocuSign#Identity_Verification
<!-- 169161 - DocuSign integration with Bank ID -->
* Added a count for invitations within the left-side panel of object pages.
<!-- 169248 - Copy of 169133 - Collaborator Count is Missing -->
* Updated the "i" icon tooltip on workflow task connectors to show conditions on hover.
<!-- 169334 - Copy of 169282 - Workflows and tooltip for Conditions -->
* Updated system uploads to check that the uploaded file's extension matches the actual file type.
<!-- 169698 - Copy of 169584 - Backup not receiving CSV file uploads in SmartFolders -->
* Updated single sign-on (SSO) with more precise and consistent date/time management across time zones.
<!-- 169879 - Copy of 169702 - B2C FHLBC -->
* Updated copy behavior so that when a record is copied, the associated media files are reprocessed automatically by the media library, allowing them to be played inline without manual intervention.
<!-- 170203 - Media library video files remain in an endless 'processing' state when a record is copied. -->
* Updated the autoloader to improve error handling when incoming data contains unexpected JSON data formats.
<!-- 170269 - Copy of 170205 - FHLBC - Salesforce Autoloader Stopped running. -->
* Fixed an issue with the <code>@objtoken_loginurl@</code> variable where it was not taking the user to the desired record if the user was not already logged in.
<!-- 167807 - Object token URL - not opening object when not logged in -->
* Fixed an issue where the axis was not displaying correctly when creating a custom field with the "Chart" type set to "Horizontal Bar".
<!-- 170180 - Horizontal Bar Chart Axis Labels Issue -->
* Fixed an issue where workflows were not automatically triggered when the status of a Level 1 record was updated using a P3 script.
<!-- 169595 - Copy of 169287 - PHEAA - P3 Script Status Change Not Triggering WF -->
* Fixed an issue with the rich text editor in workflow emails where the styles did not load as expected.
<!-- 170294 - Initializing new rich text editor -->
* Fixed issues around creating and updating associations using SmartConnect API version 1.
<!-- 170410 - Copy of 170395 - PHEAA - Issues in Organization Association API -->
* Fixed an issue where rich text fields were not rendering in '''Edit Mode''' when accessed through alternate login pages.
<!-- 170466 - Copy of 170200 - Rich Text fields value not editable when accessing through alternate login page -->
====March 20th 2025 (202503.02)====
* Fixed an issue where the first character of historical field values was being truncated in the stored data during updates made via API calls.
<!-- 171044 - PHEAA - Field history cutting off first character -->
* Fixed an issue with the new '''Data Exchange (DEX3)''' where packages failed to send with the error message: "Source import settings not found."
<!-- 171160 - Erroneous Data Exchange Emails Being Triggered -->
====April 10th 2025 (202504.01)====
=====Changes=====
* Updated the Candid integration used for verifications, demographics, and charity check to allow us to provide more data using their API. No configuration changes are required and no interruption of service is expected.
<!-- 169003 - Transition from Candid Essentials API to Foundant’s Due Diligence API by April 2025 -->
* The information returned from the legislative lookup integration has changed. This integration is accessed through the organization address standard field. As the Google Civic Information data source is no longer available, we can no longer provide Federal Legislator Data. If you are using the legislative lookup integration and have organization mappings with entries like “city\X” in the mapping column, those fields will stop returning data. We suggest you remove those mappings and hide the associated custom fields. This setting can be adjusted under: Global Settings > Organizations. The specific fields to review are listed in the "Custom Field" column. State-level Data will remain available and will not change. To learn more about this integration see https://wiki.smartsimple.com/wiki/Legislative_Information_Lookup.
<!-- 169987 - Legislative Information Lookup changes -->
=====Note on Vendor Changes=====
Our watchlist screening vendor Dun & Bradstreet has switched their data source to Dow Jones effective March 31st. Configurations using this service will need to be modified as the Syntax and the JSON data returned have changed.
Specifically, the new ssGet syntax will look like this
<code>@ssGet(D&B,dowjones;;subject=Enron;;subjectType=OrganizationName;;screeningMonitoringMode=OnlyMonitoring)@</code>
The parameters after "dowjones" are the search parameters used in the second call that pulls the Inquiry ID and should be delimited by two semicolons (";;").
The mandatory parameters that need to be included are:
* "subject" - D-U-N-S Number (or) 1 to 100 characters of the name of an organization or individual for the inquiry (ex. GORMAN MANUFACTURING COMPANY, INC.)
* "subjectType" - Type of subject to be screened
* valid values are: "IndividualName", "OrganizationName", "DUNS"
* "screeningMonitoringMode" - Screening monitoring mode for the inquiry
* valid values are:
* "DataAndMonitoring" (Screening data will be returned and Monitoring will be enabled for the inquired subject)
* "OnlyMonitoring" (Only Monitoring will be enabled and No screening data will be returned for the inquired subject)
* "NoMonitoring" (Screening data will be returned and No monitoring will be enabled for the inquired subject)
Other parameters that may be passed include:
* customerTransactionID
* customerInquiryID
* customerInquirySecondaryID
* subject
* subjectType
* birthDate
* addressCountry
* addressLocality
* addressRegion
* postalCode
* streetAddress
* notes
* customerReference
* isGlobalSearch
* screeningMonitoringMode,
* searchPrecision
* configurationID
Credentials for this service can be found at '''Global Settings''' >''' Integrations''' tab > '''Watch Lists''' > '''Dun & Bradstreet''' tab.
<!-- 170930 - Copy of 170496 - Watchlist Screening API Update -->