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 68 ( CORE )

Owned by Tony Hayes
Last updated: Jun 18, 2018
8 min read

Sprint Began: 5/1/2018     Sprint Ended: 6/6/2018

The following items have been completed in this release:

We moved the cheese!

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

Convert Merge Admin ENHANCEMENT

The merge admin management console and detail page has been implemented in our cross platform application (NEXT/Pulse).  The system has also been enhanced to store the merge template files using our FileUpload element that uploads the file to the database. The merge execution has been updated as well to retrieve the merge templates from the database during the server side merge process.  Finally a scheduled process has been created to extract existing merge templates and upload them to the database.

== SEARCH PAGE ==
Quick Search:
   Merge Name

% Search:
   Merge Name
   Description

More Search:
   Merge Name
   Description
   Merge Type

Columns:
   Merge Name
   Description
   Merge type

== DETAIL PAGE ==

The Merge Detail page Includes the following elements:

  • Name - Name of the Merge - this appears in lists throughout the application such as when creating custom links.
  • Template File - Upload control used to store the associated template in the database.
  • Description (optional) -Use this field to store a brief description of the merge and how it works.
  • Type - Output type for the merge.  This is validated against the file extension of the template file on save.
  • Password - Used for password protected merges.
  • Procedure - Select the stored procedure that will provide the data for the merge.  (optional for PDF merges - see Business Logic below).
  • Flatten - For PDF merges only select whether the merge fields will be editable (unchecked) after merging or static (checked).
  • Output Type - For Word merges only select whether to output as a word or pdf file - pdf files are static.

==Available Links==

  • Show Procedure Fields - Displays a list of the fields that will be output from the selected stored procedure.  The copy function outputs these fields in a useful comma separated list.
  • Show PDF Fields (pdf only) - Displays the actual field names from the pdf template file.

==Security == 

Merge security has been modeled on other Action center Security options such as on the Organization Detail. This allows you to secure any merge so that it is only available to certain roles and the associated users.

== BUSINESS LOGIC ==

  • Type Validation - As previously noted there is logic in the code that validates the file extension of the file that was uploaded to make sure it's valid for the selected Merge Type.
  • Stored Procedure generation (pdf only) - For PDF merges there is code that can generate a stored procedure. On add, if the selected Merge Type is PDF and the stored procedure is left blank, the system will generate a stub stored procedure using the fields from the PDF document.


Dataform: Unlock Row Security ENHANCEMENT

The ability to "unlock" individual dataform rows such as with secured case types has been added to the application.  Secured records are indicated by a lock   in the action center icons.  Administrators can navigate to the individual secure record and unlock that record by clicking the lock icon in the action center, removing security for that record. 


Default Contact Owner ENHANCEMENT

The contacts system has been enhanced to synchronize the default assigned to user with the associated organization.

  • When creating a new contact, the system will now default the contact Assigned To, matching it to the Org Assigned To. 
  • When Org Assigned To changes, the system updates all associated contacts synchronizing the Assigned To user with the Org. 


Activity Dataform Linking ENHANCEMENT

The activity detail has been enhanced, adding a link to the action center which enables you to open the associated dataform

  • An action center link has been added to the Activity details , when applicable, which on click will open the related dataform record as a separate work item below the activity in the Work Center. 
  • A filter has been added to the Activity module allowing the user to filter the list by the associated dataform.


Task Enhancements ENHANCEMENT

Tasks within the application have been enhanced to make them more organized and easier to use.  These changes include the following:

  • All of the task detail fields have been organized into a "General" fieldset.
  • The Related Form field has been moved to the top left and the "Send Notification" checkbox has been moved to the top on the right making it easier to use when saving the form.
  • An "Administrative Fields" fieldset has been addded below the "General" fieldset - similar to the Administrative fieldset on dataforms. It will include all of the same fields as dataforms, excluding Import ID and Workspace but adding the "Date Updated" and "Updated By".  Only global admins can see this fieldset.
  • The Task "Archive" checkbox has been updated to use the "Is Active" format, like dataforms, and most everywhere else in the application. This checkbox has been moved out of the fieldset area, to the bottom left of the form, with the label "Is Active". This is a cosmetic change to make the task functionality consistent with the rest of the application - the underlying data structure is being preserved so as to not affect existing reports which rely on the "Archive" flag.  All existing logic that Archives a task when completed has also been preserved.


Workspace level Recurring Tasks ENHANCEMENT

Workspace level recurring tasks  have been added to the application.

This functionality allows you to add a task at the workspace level that will be generated on a configured schedule,  like a recurring calendar event using a system scheduled process.  For more information about recurring tasks review the video - Configuring Recurring Tasks.


Recurring Task Enhancement - Validate Start Date & Due Date ENHANCEMENT

The start and due date offset field on the task recurrence configuration dialog has been enhanced, adding validation to insure the Due Date Offset cannot be inadvertently misconfigured to be less than the start date of the recurring task. Additionally a visual indicator has been added to mark these fields as required when cleared.

  

Workflow Channels- Start channel via schedule  ENHANCEMENT

  

The workflow system has been enhanced to allow Workflows (both task and dataform cloning) to be triggered on a schedule based on a date field from the triggering form.  A scheduled process (Generate Scheduled Workflow) compares the current date to the triggering date field of each scheduled workflow as well as any additional triggering conditions to determine whether the task or dataform will be cloned. The triggering determination can be modified using a date offset and supports a Grace period should all the triggering conditions not be immediately met.  For more information regarding Configuring and using scheduled workflows review the document Configuring Scheduled Workflows.


Email Templates - Slack ENHANCEMENT

The Email Template system has been enhanced, providing the ability to send automatic notifications to slack users or channels as well as via email all at the same time. Slack notifications will display the Subject line of the email template and support field replacement, allowing you to include dataform and workspace information in your message. Slack notifications are automatically set to "To" addresses when selected, the Address field should be set to either the Slack channel name (for example #notify_ClientService) or the slack user (@bill). 


Need to Trigger More Than 1 Item From the Main Workflow Channel ENHANCEMENT

Workflow channels have been enhanced to separate the workflow channel from all of the workflow items, allowing for true concurrent workflow items to be generated from the initial triggering event. Previously an initial task would need to be attached to the triggering event and all dependent items would be fired from the triggering task. By separating the workflow channel from the workflow items the system can now generate multiple independent workflows simultaneously from the same triggering event. Workflow tasks can then spawn dependent workflow items allowing you to create cascading workflow events. Each of the triggered workflow items share a triggering Form, but can have unique triggering fields and events, providing for much more robust configurations.


Workflow Notifications on User-based Fields  ENHANCEMENT

User notifications have been added to Workflow Channels. You can now select user fields on a system dataform containing a user type field when configuring workflow notifications by selecting the option "From a field on Form". This displays a list of forms within the system which contain user fields. Once a form is selected a list of user type field on the form is available for selection. When notification occurs the email address for the user in this field will be looked up and a notification sent.


Boolean Field Types on Workflow Channels ENHANCEMENT

All workflow condition fields for dataform checkboxes now have value dropdowns containing Unchecked and Checked.


Workflow Channel Replace Field Options ENHANCEMENT

Server data stored procedure information for SDP1 and SDP2 have been added to Field replacement in Worfklow channels. These custom stored procedures can be used to return data from other workspace dataforms that can then be used when generating system notifications.


User Workspaces ENHANCEMENT

The user profile has been enhanced, adding a new Admin option to the Action items to Add Workspaces  

This option allows the admin to easily add and remove workspaces from an individual user profile.  The list of workspaces available for admin is limited to those where the admin is already a member of the project users.


Next: prevent log in from Template User accounts ENHANCEMENT

User security has been enhanced to remove the ability to log into the system as a Template user. When a template user account is used to log in the attempt will fail with the error:

•This user account cannot be used to login to the system. Please contact the system administrator.


Monthly ClientSpace Index Tuning - Core ENHANCEMENT

Additional indexes have been added to several system tables, making accessing the tables more efficient.  These tables include:

  • tblImportQueue (API Imports)
  • tblWorkflowItemLinking (Workflow Channels)
  • tblCalendarEventAttendee (Calendar Attendees)
  • tblCalendarEvent (Calendar Events)
  • gen_ClientServiceCase (Cases)
  • gen_CompClaimFinancial (Claim Financial records)
  • The employee search dashboard has also been performance tuned, adding an index to the Employment table as well as improving the method of collecting the total record count.


Email Admin Issue 

Resolved an issue in the Email Admin control panel where the counts for Sent and Unsent did not match expected numbers. Email admin now accurately reflects the number of Sent, Unsent and all emails available.


Can't update the Import ID for a user 

The user ImportID will now save. If not provided it will be set to the username


Dataform Object Reference Exception 

Resolved an issue where an Object Reference Exception is thrown when attempting to navigate to a dataform record that no longer exists.  If you attempt to open a record which no longer exists the system will now present the message:  "The dataform you requested was not found or no longer exists. If you navigated here from BI....."


Widget Conditions 

Resolved an issue where filtered lookups used in widget condition expressions would return no values, making them unusable as triggering fields for widget layouts. A filtered lookup will now return all possible values available to that lookup field when used as a triggering condition for widget layouts.


Izenda Reporting 6.10.0.30 Update

The Izenda business intelligence reporting engine has been updated to the latest version, 6.10.0.30 which resolves a reported issue with formatting on exported excel reports where dates were not formatted as dates.  Dates are now appropriately formatted when exporting to excel.  More information about the latest Izenda reporting release can be found in the Izenda Release notes (http://wiki.izenda.us/Release-Notes).


Exception when trying to assume expired user

Removed the ability to assume an expired or inactive user account as this could cause system exceptions. If there is a need to assume an expired or inactive user it is recommended you change their password, activate and assume them, then inactivate or expire the user once done.


Sunset Message Boards 

The Classic message board has been deprecated. After review of it's use it was found that this object was primarily used for notification of import exceptions.  This can be accomplished though a scheduled BI report using tblImportException.  For more information about generating this report contact your staff consultant.




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