Difference between revisions of "Template:July2023Upgrade"

From SmartWiki
Jump to: navigation, search
(Updated Workflow Behavior)
(updated workflow change of behaviour)
Line 33: Line 33:
  
 
====Updated Workflow Behavior====
 
====Updated Workflow Behavior====
Updated the behavior of workflows to run in a linear manner instead of generating new threads when the '''Run Asynchronously''' option is toggled off. This change will reduce the likelihood of two workflows running simultaneously on the same record. After the upgrade, the task process order will be:
+
Updated the behavior of workflows to run in a serial, single-threaded manner where child workflows are triggered during the processing of a workflow. Previously when stepping through a workflow, if another workflow was triggered, a new thread would be created to process the child workflow simultaneously and asynchronously, as the original system thread would then return to the original workflow and continue to step through its tasks without waiting on the child workflow to complete. This could lead to inconsistent results if the system was configured to run multiple workflows against the same object, or if the order of operations of their tasks needed to be preserved, but results would vary due to race conditions of the workflows.
 +
 
 +
After this upgrade the default behavior of workflows has now been changed to instead process multiple workflows in a serial synchronous fashion so that their order of operations and behavior are more consistent and predictable. Now when a workflow triggers another workflow, the system will process all child workflows fully to completion in the original system thread rather than passing each new workflow to a new separate processing thread. This means that child workflows will be processed in a serial fashion, and their order of tasks will be preserved, before the system returns back to working on the original workflow. This may impact systems where workflows are configured to launch other child workflows, and you may now experience an increase in the runtime of such workflows. If the areas in your system that trigger multiple workflows, do so with different target objects for each of the workflows, then it should be safe for you to revert back to the previous mode of operation by enabling the new [Run Asynchronously] toggle that is now available inside the configuration of a workflow, and to enable this option on the initial workflows that are instantiating child workflows.
 +
 
 +
Examples and notes. After the upgrade, the task process order will be:
  
 
# If the workflow is a trigger workflow task, go to the trigger workflow
 
# If the workflow is a trigger workflow task, go to the trigger workflow
Line 40: Line 44:
  
 
Workflow completion time may be affected and can vary depending on the configuration.
 
Workflow completion time may be affected and can vary depending on the configuration.
 
Previously when stepping through a Workflow, if another Workflow was triggered, it would be run in a new thread simultaneously and asynchronously, and the system would return to the original Workflow and continue to step through its Tasks. This could lead to inconsistent results if the system was configured to run multiple Workflows against the same object, and if the order of operations of their Tasks needed to be preserved due to race conditions of the Workflows. 
 
 
After this upgrade the default behavior of Workflows has now been changed to instead process multiple Workflows in a serial synchronous fashion so that their order of operations and behavior are more consistent and predictable. Now when a Workflow triggers another Workflow, the system will process all sub-Workflows to completion in the original thread rather than starting them in a new thread. This means that sub-Workflows will be processed in a serial recursive fashion before the system returns back to working on the original Workflow.  This may impact systems where you may now control this behavior with the new option '''Run Asynchronously''' that has been introduced on the Workflow configuration screen. If the areas in your system that trigger multiple Workflows, do so with different target objects for each of the Workflows, then it should be safe for you to revert back to the previous mode of operation by enabling the '''Run Asynchronously''' toggle on Workflows that trigger other sub-Workflows.
 
  
 
In general, "chained" workflows that are triggering against the same object should remain synchronous. For example, if the Level 1 record triggered workflow A and one of its task triggers workflow B on the same Level 1 record, then the workflows should remain running synchronously. Therefore, do not toggle on the '''Run Asynchronously''' option). However, if the Level 1 triggers workflow A and then one of its tasks is to trigger workflow B on all of the associated contacts on the Level 1, then this workflow can run asynchronously and the '''Run Asynchronously''' option should be enabled on workflow B to optimize performance.
 
In general, "chained" workflows that are triggering against the same object should remain synchronous. For example, if the Level 1 record triggered workflow A and one of its task triggers workflow B on the same Level 1 record, then the workflows should remain running synchronously. Therefore, do not toggle on the '''Run Asynchronously''' option). However, if the Level 1 triggers workflow A and then one of its tasks is to trigger workflow B on all of the associated contacts on the Level 1, then this workflow can run asynchronously and the '''Run Asynchronously''' option should be enabled on workflow B to optimize performance.

Revision as of 15:45, 1 February 2024

Contents

Overview

Watch this video to get a general overview of the new features in this release.


To watch this video in full screen, please click on the full screen button on the bottom right.

Global System Upgrades

The new features listed below are enhancements to the SmartSimple system and will be immediately available to SmartSimple users upon the application of the upgrade to their server:

Major Updates

Password Variables to be Deprecated in November

Main Article: Password Variables to Set or Reset User Passwords

In the upcoming November 2023 release, password variables will be deprecated for improved security. Instead of using the soon to be deprecated password variable (@password@) which sends a password in the email, all systems will be required to use the following activation link variable to send the user to a page where they can enter their desired password:

https://@url@@activationlink@

Therefore, the following variables will be deprecated and will not work after the November upgrade: @password@, @checkportalpassword@, @checkactivatedpassword@, @randompassword@, and @passwordresetlink@.


If you need help updating email templates for new users or password resets, reach out to our Support team. These email templates are located at Menu Icon > Global Settings > Security tab > Password and Activation Policies > Activation Emails tab. Clicking the Sample Template link will update the templates with the desired variable. Make sure to check any existing workflow emails for these soon-to-be deprecated variables.

Depending on how your user signup pages are configured, you may also need to update signup page templates for new users which can be found at Menu Icon > Global Settings > Communications > System Email Templates. You can filter the list by searching for “Signup”.

Clicking the Sample Template link on the New User email will provide you will the variable that will return a link to a page where users can enter their desired password. The @password@ and other variables will no longer work after the November release.

Updated Look of File Uploader

In the upcoming November 2023 release, the user interface of the file uploader will change slightly throughout the platform. To try this feature before November, you can enable the new uploader by going to Menu Icon > Global Settings > Branding tab > Toggle on Enable New File Uploader.

The look of multiple file upload fields will change slightly in November. For example, you will be able to drag and drop files inline, instead of opening a modal window.

Updated Workflow Behavior

Updated the behavior of workflows to run in a serial, single-threaded manner where child workflows are triggered during the processing of a workflow. Previously when stepping through a workflow, if another workflow was triggered, a new thread would be created to process the child workflow simultaneously and asynchronously, as the original system thread would then return to the original workflow and continue to step through its tasks without waiting on the child workflow to complete. This could lead to inconsistent results if the system was configured to run multiple workflows against the same object, or if the order of operations of their tasks needed to be preserved, but results would vary due to race conditions of the workflows.

After this upgrade the default behavior of workflows has now been changed to instead process multiple workflows in a serial synchronous fashion so that their order of operations and behavior are more consistent and predictable. Now when a workflow triggers another workflow, the system will process all child workflows fully to completion in the original system thread rather than passing each new workflow to a new separate processing thread. This means that child workflows will be processed in a serial fashion, and their order of tasks will be preserved, before the system returns back to working on the original workflow. This may impact systems where workflows are configured to launch other child workflows, and you may now experience an increase in the runtime of such workflows. If the areas in your system that trigger multiple workflows, do so with different target objects for each of the workflows, then it should be safe for you to revert back to the previous mode of operation by enabling the new [Run Asynchronously] toggle that is now available inside the configuration of a workflow, and to enable this option on the initial workflows that are instantiating child workflows.

Examples and notes. After the upgrade, the task process order will be:

  1. If the workflow is a trigger workflow task, go to the trigger workflow
  2. If the connector is connected to a task, go to that task
  3. If the connector is connected to a workflow, go to that workflow

Workflow completion time may be affected and can vary depending on the configuration.

In general, "chained" workflows that are triggering against the same object should remain synchronous. For example, if the Level 1 record triggered workflow A and one of its task triggers workflow B on the same Level 1 record, then the workflows should remain running synchronously. Therefore, do not toggle on the Run Asynchronously option). However, if the Level 1 triggers workflow A and then one of its tasks is to trigger workflow B on all of the associated contacts on the Level 1, then this workflow can run asynchronously and the Run Asynchronously option should be enabled on workflow B to optimize performance.


Minor Updates

Added Ability to Resize Media During Playback

Added the ability to resize the media player docking well when using the Media Library. If you scroll away while the media is playing, a window will appear which can be resized by clicking and dragging the bottom right-hand corner.

When video is playing in the docking well, you can resize the video by dragging the bottom right corner.

Updated Verification Settings for Australian Organizations

Updated the organization signup page verification settings for the Australian Business Number (ABN) to return and allow field mapping for ACNC registration, TCC status (which exempts charities from having to pay income tax) and DGR1 status (for charities that are endorsed as a deductible gift recipient).

Signup pages using the verification settings for the Australian Business Number (ABN) will now return more information. Hover over the desired result and click the Details button.

On-Demand System Upgrades

The following features are available immediately with the application of the upgrade, but must first be enabled or configured by a Global Administrator:

Major Updates

Added AI Features

Main Article: AI

SmartSimple Cloud +AI integration gives you the ability to utilize large language models (LLM) from within our business process automation platform. LLMs are often utilized to improve productivity, processes, and outcomes. This integration has two modes: interactive and automation.

  • Interactive Mode: This mode of operation occurs on a single object such as a grant application or review. In this scenario, the user can interact with the AI in a call-and-response kind of model. The user might ask the AI to help them rewrite content, translate content into another language, or make content more concise. The user can ask questions (prompts) and follow up with more related questions. The user can also be presented with optional predefined templates to streamline common tasks.
  • Automation Mode: This mode of operation can occur in various areas of the platform, such as web page views or workflows. In this scenario, the system is configured to automatically interact with your chosen 3rd party LLM vendor to do something with or without manual intervention. For example, the system can be configured to automatically generate an executive summary of an application or a summary of the reviewers’ comments. Applications could be prescreened and recommended or the AI could suggest reviewers with subject matter expertise related to the application. In this mode, prompts may be pre-configured and responses may be stored inside your system.

Using the +AI integration requires your own license and an associated fee. Reach out to your account manager or email Platform Solutions for more information. Once +AI is enabled, you will need to enter the third-party AI service license (such as ChatGPT) at Global Settings > Integrations tab > Integration Key Management.

To set up interactive mode, go to the desired UTA > Configuration Settings > Level 1, 2, or 3 tab > AI. You can create AI templates and set appropriate permissions. Once set up, open a record such as a Level 1 grant application and go to Tools > Work with +AI. This will launch a modal window where you can select pre-configured prompts (templates) or enter improvised prompts for the AI.

For automation mode, use the following syntax for prompts in web page views and workflows:

AI Syntax Format.png

These parameters are explained as follows:

  • AI service: The AI service being used. If left empty, OpenAI will be used as default.
  • AI function: Set the intended use of the input text. If the text is meant to be static, set the value to "text". If the text is meant to be edited by the AI, set the value to "edit".
  • temperature: Set the desired level of randomness of the generated text, where a value of "0" is the most conservative while a value of "9" is the most random.
  • instruction: Optional parameter when using the edit AI function.

Note: If the AI function parameter has been set to "edit", you must pass instructions to the instruction parameter on how the text should be edited in natural language. For example, "fix the grammar", "make this in the style of a poem", or "translate this into Japanese". For additional help with testing syntax, open a record in Configuration Mode and select the Variable Syntax Helper.

Users with permission may access the interactive AI mode from record pages via the Tools menu.
In the interactive mode users can enter prompts using natural language, refine the responses by asking follow-up related questions in a conversational format. Users may also select from predefined prompts.

Added Ability to Delegate Users

Added ability for users to assign delegates who will be able to emulate them within the system for a set period of time. For example, if you will be out of office for vacation, maternity leave, or some other temporary absence, you can now select a delegate (such as a manager or coworker) who will gain the ability to emulate your account and execute your tasks for a set time period. This means you no longer need to temporarily modify role permissions or assign other users to specific records to oversee your tasks. Additionally, this feature is not limited to internal users. External users, such as applicants, could designate a co-applicant to assist with the process of filling out an application on their behalf. Once a user is delegated, they will receive an email notification that they have been selected as a delegate. Once they login, the user will see a new icon in the global header that allows them to temporarily emulate another user.

To configure this setting, go to Global Settings > Security tab > System Feature Permissions > Features tab. "Under the Delegation - Roles That Can Delegate" section, set which roles will have the ability to delegate users to temporarily emulate them. Under the "Delegation - Roles to Delegate to" section, set the roles that can be selected as delegates. To use this feature, the roles that have permission to delegate can go to User Menu > Personal Settings > Other tab > Toggle on Enable Delegation. You will be required to choose the specific users who may emulate you and a date range. Additionally, you can specify a message that will appear on your user profile letting people know who your delegate is and how long you may be out of office.

Note:

  • Global Administrators can only delegate to other Global Administrators and internal users can only delegate to other internal users.
  • Delegation is not visible in Emulation Mode.


Users with permission may go to personal settings and delegate to another user while they are out of office.
Users may optionally enter an out of office message that will show up on their profile.
If you have permission to temporarily emulate a specific user, you will see a new Delegation icon in the header. Select the specific user you would like to emulate.

Added Ability to Group Multiple Submit Buttons

Some business processes require many submit buttons which can take up a lot of room in the submit bar. We have added the ability to group multiple action buttons under a single button group. To see this feature, go to UTA > Configuration Settings > Level 1/2/3 tab > Submit and Save Buttons > Edit a button. There is a new setting called Button Group Name. If multiple buttons are given the same Button Group Name, they will appear on the record under a single button group.

Group multiple submit buttons under a single button group to save space and organize the buttons that appear in your submit bar.

Added File Upload Feature to Autoloader

Added the ability to upload specific files to specific records via the autoloader in bulk. Previously, if you had several files across multiple records that needed to be updated within a specific UTA, user, or company, finding each record and manually uploading those files would be tedious, especially if the files needed to be updated on a regular cycle. Now you can upload all the files in bulk and the system will unpack and distribute those files to the fields you specified accordingly.

To use this feature, follow these steps:

  1. Create a CSV file containing mandatory columns (File Name and Custom Field ID) and the relevant identifier columns for the records.
  2. Create a ZIP file that contains the files you want to upload or replace. Make sure the ZIP file and the CSV file have the same name.
  3. Go to Menu Icon > Autoloaders > Create or edit an autoloader > Select the desired Processing Folder.
  4. Set the File Type to “CSV, Text”.
  5. Under Record Type, select the desired record type you want to target ("UTA", "People", or "Company").
  6. Under Item, select the new “File Upload” option. If you selected a UTA as a your Record Type, you will be prompted to select the desired Level 1, 2, or 3.
  7. Configure the column mappings as usual.
  8. Upload the CSV and ZIP file to the processing folder you selected in Step 3.

Note: This new option does not create new records or update other columns. The “File Upload” item only uploads files.

Use the new "File Upload" option to have the autoloader unpack a ZIP file and upload/replace files to specific upload fields as specified in a CSV file.
The CSV file must have the same name as the ZIP file and it must specify the record ID, upload field ID, and file name.

Minor Updates

Added Ability to Edit Default From Address

Added a setting that allows users to modify the From Address when a default From Address has been globally set. Therefore, you can now choose to lock the From Address to restrict any emails sent to come from the same address or you can give users the flexibility to change the From Address on an email-by-email basis. To use this feature, you must have Enable Default Address toggled on. To turn this feature on, go to Menu Icon > Global Settings > Communications tab > Email Options and Security > Toggle on Allow users to edit the From Address when composing emails.

The default From Address is typically locked to prevent users from editing it. However, a new setting allows the default From Address to be edited by users if needed.

Added Custom Search for Aggregate Shortcuts

Added the ability to link an "Aggregate" type shortcut to a section within a portal. This allows aggregate shortcuts to link the user to a list view with customized search criteria options.

Aggregate shortcuts with Link to List View toggled on, will open the list view and display the default portal search.
Aggregate shortcuts with Link to List View toggled off can be set to point to a list view section that has custom portal section search setup. The custom search allows you to specify which columns you want a user to be able to search on.
If you are configuring an Aggregate shortcut and you do not select Link to List View, you can have the shortcut open a portal section that contains a list view with a custom search.

Added Role Permissions to Shortcut Visibility

Added an easier way to set role permissions for the visibility of shortcuts on the Common portal role. Previously, visibility conditions had to be set in order to show or hide shortcuts based on role. To set permissions, go to Menu Icon > Global Settings > Users tab > Portals > Select the Common portal > Click the Shortcuts button in the top action bar > Edit a shortcut > Permissions tab > Set roles for Allow Access or Deny Access.

Added role permissions for shortcut visibility on shortcuts created under the Common portal role. Previously you had to write your own visibility conditions.

Added Portal and Draft Portal Buttons to Shortcuts

Updated the configuration pages for portal Shortcuts to include the Portal and Draft Portal buttons in the top action bar. These new buttons will help the user easily navigate to the appropriate portal from the shortcut configuration screen.

Easily navigate from the editing shortcuts to editing the associated portal.

Added Ability to Batch Add Notes in List View

Added ability to add notes to records in batch from UTA Level 1/2/3, User and Organization list views. To turn this feature on, go to the desired list view settings and toggle on Enable Add Note. When multiple records are selected in the list view, the Add Note button allows you to enter a single note for all selected records.

Add a note in batch to several records from the list view.

Added Access to Record Notes on SmartCards

Added ability to quickly view notes on records from within SmartCards. If a user navigates to SmartCards under the User Menu, there will now be a note icon in the right-hand corner of each record which allows users to view notes on that record in a modal window without having to open the record. Additionally, a new note can also be added in this modal window. To enable this feature, go to Global Settings > System tab > Toggle on Open record notes directly from SmartCards.

Optionally open record notes directly from SmartCards

Added Ability to Batch Update Organization Fields

Added the ability to batch update the Owner and the Parent Company fields from the organization list view. The associated role permission to give access to the feature is found at Menu Icon > Global Settings > Security tab > System Feature Permissions > Organization tab. The settings are Enable Batch Update and Enable Batch Update Owner. Once permissions have been set up, go to Menu Icon > Organizations > Select the desired organizations > Click the Assign Owner button.

Notes for Admins

Added API Logs to SmartConnect Configuration Page

Updated SmartConnect API configuration page to display API logs. To see the API logs, go to Global Settings > Integrations tab > SmartConnect API > Click the API Logs button in the top action bar. You can also edit a function or user to see the API logs filtered for that function or user.

View the API logs by function or by user.

Added Ability to Delete Multiple Upload Files from API

Added the ability to delete files from Upload - Multiple Files Storage fields using the SmartConnect API. This new option can be seen by going to Global Settings > Integrations tab > SmartConnect API > Edit a function > Action Type. A new option has been added called “Files - Delete”.

Added Ability to Allow Access to API Functions by Role

Added the ability to allow access to an API function by role. To see this feature, go to Global Settings > Integrations tab > SmartConnect API > Edit an API > Allow Access. If this field is left empty, everyone will have access by default.

Added Ability to Send Signed Authentication Requests to Identity Provider for Service Provider-Initiated Single Sign-On

Added support for X.509 signing certificate for single sign-on (SSO) authorization requests. If you are using a service provider-initiated SSO, a signed authentication request embedded with the signed value and the X.509 certificate will be sent to the identity provider (IdP). The new setting is located at Global Settings > Integrations tab > Single Sign-on > Edit a SP-initiated SSO and toggle on Sign authentication request sent to identity provider (IdP).

Added a Warning to Upload - Multiple Files Storage Custom Field around Value Storage

Added a warning on the Upload - Multiple Files Storage custom field in the event a user attempts to configure storing files to another field when there are existing files already uploaded in the current field. Configuring the “Value Storage” section on an upload field should be done before files are uploaded to prevent the loss of visibility of files already uploaded.

Added Everyone Role Option within Portals

Added ability to add the Everyone option within portal role permissions. Previously, some portal permissions contained the All option. The Everyone role option is more advantageous as it allows admins to set permissions to every existing user (present and future) regardless of their role. The All option was problematic as it only added current roles in bulk and therefore required periodic amending when new roles were added to a system.

Added Field IDs to Report Builder

Added Field IDs as a row in the Report Builder. Also added Object IDs to the following pages for easier configuration: company category, UTA L1/L2/L3 list view settings, user role.

Added New Setting to Increase Server File Upload Limit

Added a new setting called File Upload Limit that may be used to increase the default 2GB server-wide file upload limit. This is only available to managed dedicated environments. To see this setting navigate to Menu Icon > Gort Automation > Under the Server Details tab > The new setting is called File Upload Limit. Once this setting has been adjusted to something greater than 2GB, navigate to an Upload – Multiple Files Storage custom field to adjust the maximum file upload size to be greater than 2GB.

Added New Options for New Activity Workflow Tasks

Added three new workflow options to the “Create New Activity” workflow task. By default the new settings are either toggled on or off based on existing behavior. The three new settings are:

  • Check Status Trigger: By default, this setting is off. If enabled, any Status Triggers associated with the new record status will run as part of this workflow.
  • Trigger Formulas: By default, this setting is enabled so any formulas on the record will run as part of this workflow.
  • Trigger Activity Level Workflow: By default, this setting is enabled so activity level workflows set up to run on the new activity record status will run as part of this workflow.

The new settings can be found at Menu Icon > Workflows > Task tab > Open a task with a Task Type set to “Create New Activity”. The 3 toggles appear under Activity Status.

Updated Default End Date for Level 2/3 Workflows

Updated the behavior of workflows with tasks of the "Create New Activity" type. Specifically, if Disable Default Date is toggled on for the UTA level 2/3, then the start and end dates will be empty. If Disable Default Date is toggled off for the UTA level 2/3, then the start and end dates will be populated with the current date.

Updated Record Lock to Be Toggled On by Default

Updated platform behavior to lock UTA records by default so two users cannot modify the same record at the same time and potentially overwrite each other’s changes. The record lock owners’ names will also be anonymized by default. This change will only apply to newly created systems where the record lock setting will no longer be an option. The anonymized record lock owner role permission can be found at Global Settings > Security tab > Anonymize Record Lock Owner for Organization and User Records. Within the UTA, it can be found at UTA > Configuration Settings > Security tab > Anonymize Record Lock Owner.

Updated ORCID Integration

Updated ORCID (research publication) integration to retrieve additional information from each “work” record, including contributors.

Updated Upgrade Email Alerts to Use System Default From Address

Updated the upgrade email alerts to use the system's default From Address located at Menu Icon > Global Settings > Communications tab > Email Options and Security > Toggle on Enable Default From Address. Previously, these notifications came from donotreply@smartsimplemailer.com. After the upgrade, the emails will use the default From Address specified.

Updated System Security Summary

Updated the System Security Summary to flag any backup environments that have access open to all roles. To view the security summary, go to Menu Icon > Global Settings > System tab > System Security Summary. The role-based setting is located at Menu Icon > Global Settings > Security tab > System Feature Permissions > Feature tab.

Updated Personal Settings to Hide Common CV Field by Default

Updated the user personal settings to hide the Common CV field by default. This field was previously located at User Menu > Personal Settings > Other tab.

Deprecated Classic Options from Global Settings

Deprecated several classic options found at Menu Icon > Global Settings > Classic Options. The following features will no longer be available:

  • Use Classic Note Save Button
  • Use Classic Tooltip
  • Use Classic Association Entry View
  • Enable Copy to Existing Records
  • Use Classic Shortcut Panel
    Note: If you do not see icons on your shortcuts, navigate to Global Settings > Users tab > Portals > Edit the desired portal > Shortcuts > Edit the desired shortcut > Pick an Icon Style (Light /Regular/Solid/Brands) > Select an icon and click Save.
  • Use Classic Status or Type Coloring for List Views
    Note: The status/type color will be displayed as a band on the left-hand side of each row within the list view. If you also have the type icon displayed, the color will also correspond to the status/type color.
    A list view where the status color is displayed both in the band and in the type icon.


The following features are no longer supported and will not be available to new systems. However, if you have any of the following already enabled, they will continue to work as normal:

  • Disable Global Use of Pre-Defined Select Options for State/Province Fields
  • Enable Pandora
  • Disable Sub-Fields from Main Custom Fields List View
  • ObjectSync Settings

Deprecated Global Search

Deprecated the Global Search feature which formerly appeared under the “Tools” heading of the Menu Icon if enabled.

Service Packs

October 19th 2023 (202310.02)

Fixes

  • Fixed an issue with the display of Google reCaptcha where the window was not resizing as expected.
  • Fixed an issue where the GuideStar Charity Check option was not showing up under the Tools menu.

Other Changes

  • Updated default translation message in Spanish and Catalan for mandatory fields.

October 12th 2023 (202310.01)

Fixes

  • Fixed visual alignment issues with the display of the Display - Countdown Timer custom field.
  • Fixed an issue with the System Performance Summary page where the list syntax was not properly highlighted. The custom field ID was also added after the custom field name under the Category column.
  • Fixed an issue where a double alert message was displayed when using a custom batch update button.
  • Fixed an issue where deleted Level 1 records were not being displayed in the listview of deleted records.
  • Fixed an issue with the user’s personal language setting where selections were not always saved.


Other Changes

  • Updated email access settings located at Menu Icon > Global Settings > Communications > Email Options and Security. Prior to this release, there were only disable settings for email and instant messaging access. These older settings have been replaced with two new settings, an Allow permission and a Deny permission. After this release permission will need to be explicitly granted to access email and instant message functionality.
  • Added the option to assign people when creating a task of the type “Update Standard field” on L3 workflows.
  • Updated the Special - Basic Data Table custom field to no longer use Angular JS.

September 21st 2023 (202309.02)

Fixes

  • Fixed an issue with Level 3 workflows failing to trigger.

Other Changes

  • Added the ability to specify an alternate login page ID for the activation link variable. This new activation link mimics the login action from the specified alternate login page while carrying over attributes after activation such as primary role. The variable will take on the format @activationlink(1234)@ where “1234” is the page ID of the alternate login page. Such variables can be called from workflow emails.

September 14th 2023 (202309.01)

Fixes

  • Fixed an issue with the Lookup - Autocomplete Options custom field where only date fields were available under the Option Caption Field dropdown.
  • Fixed an issue with Quick Edit where date fields were not saving properly.
  • Fixed an issue with PDF generation from a Special – Web Page View field when the file name contained single or double quotes.
  • Fixed an issue where user records, created using the SmartConnect API, would not open as expected from the organization hierarchy.
  • Fixed the duplicate check screen when creating an Organization to use standard field language translations for the Name, City, and Phone captions.

Other Changes

  • Updated Guidestar Charity Check and Charity Navigator Check workflow task types to be available only for Workflow Type of "Company".
  • Updated the Field Change History Log so users with permission to see the change log will now be able to view the details of that log as well.
  • Updated System Performance Summary to restrict note creation to Global Administrators.
  • Updated the Report export in JSON format to return file paths as relative links.
  • Added accessibility improvements to tabs, search, jump to menu, and the text color in the non-production banner.
  • Updated available language options. Translations can now be added for 187 languages.
  • Updated CSI Web Integration endpoint and calls.
  • Updated available region options for Denmark.

August 17th 2023 (202308.02)

Fixes

  • Fixed an issue where workflows calling RESTFUL API requests were not working as expected after the August 10th 2023 Service pack.
  • Fixed an issue with the search where a wrench icon would appear inside the ‘Recent Searches’ box.

Other Changes

  • Updated behavior of workflows so that when an initial workflow triggers a new workflow, a new thread will be created if the subsequent workflow is set to be asynchronous.

August 10th 2023 (202308.01)

Fixes

  • Fixed an issue where the From Address was still set to a default address on the “Compose Email” page when Enable Default From Address was toggled off.
  • Fixed an issue where the Sort Order tab was locked on personal list views if the System Configuration Lock was toggled on.
  • Fixed an issue with the Paper Size setting on web page views.
  • Fixed an issue where a file uploaded on the organization level wasn't displayed in the Level 1 list view for records connected to the organization.
  • Fixed an issue where users saw an "Invalid Login Token" message on the login screen when the page was idle for too long.

Other Changes

  • Added support for “Lookup - Organization and People” to the custom fields that can be copied.
  • Updated the font size of the contact suffix to be the same as the contact name on user profile records for easier readability.
  • Updated the autoloader to execute one query to update/import all the custom fields per record. In addition, updates were made for efficiency.

August 4th 2023 (202307.03)

Fixes

  • Fixed an issue where portal file links for files were not rendering when the setting Ignore Field and Record Permissions When Serving Files was toggled on.

July 27th 2023 (202307.02)

Fixes

  • Fixed an issue where fields with visibility controlled by Dynamic Visibility Field Controls would not display when the record was in View Mode.
  • Fixed an issue with the delegation feature to improve system load times.
  • Fixed an issue that was causing authentication problems with DocuSign.
  • Fixed an issue where a workflow task to generate PDFs was stuck in a pending status.