Want to maximize your usable real estate? Click the vertical divider to the left or press [ on your keyboard.

Release 68 (Pulse) Notes

Owned by Tony Hayes
Last updated: Jun 08, 2018
9 min read

The following items have been completed in this release:

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


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 provide a 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.

  

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. 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.

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.


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.


Workflow Channel Replace Field Options (Server Data Procs) ENHANCEMENT

The workflow channels functionality has been enhanced, including three new server data stored procedures to be used when merging Employee and Employment type data.  These stored procedures and the available merge fields are as follows:

Employment (peo_server_data_employment)

  • FirstName
  • LastName
  • MiddleInitial
  • EmployeeIdentifier
  • Address1
  • Address2
  • City
  • State
  • ZipCode
  • EmploymentStatus
  • EmploymentType
  • HireDate
  • ClientNumber
  • ContractType
  • ContractEffectiveDate

Employee (peo_server_data_employee)

  • EmploymentStatus
  • EmploymentType
  • HireDate
  • ClientNumber
  • ContractType
  • ContractEffectiveDate


PrismHR Event (peo_server_data_prismhrevent)

Schema = Employee:

  • FirstName
  • LastName
  • MiddleInitial
  • EmployeeIdentifier
  • Address1
  • Address2
  • City
  • State
  • ZipCode
  • EmploymentStatus
  • EmploymentType
  • HireDate
  • ClientNumber
  • ContractType
  • ContractEffectiveDate

Schema = Company:

  • ClientNumber
  • ContractType
  • ContractEffectiveDate

Joinder - Add the ability to push locations into Prism ENHANCEMENT

The PrismHR API has been enhanced, allowing the system to push location information into PrismHR.  If a ClientSpace location does not exist in PrismHR, that location will be created in the Prism System.  Two new business rules have been added to accomplish this:

Client Master - CM.ExportLocationsToHRP

  • Creates all locations in a workspace in PrismHR
  • Not on Add, and CM.ClientNumber must exist
  • Updates the Export Status and Export Log fields on each Location form, saves via Biz Logic ("HRP" pipeline)
  • Will NOT set the ImportID on the Location(s), Import ID setter proc should be used


Client Location - LOC.ExportLocationToHRP

  • Creates the current location in PrismHR
  • Not on Add, and CM.ClientNumber (on associated Client Master) must exist
  • Will NOT set the ImportID on the Location(s), Import ID setter proc should be used
  • In rule configurations
    • Provide the AppCode of the PrismHR API Configuration form to use
    • Must be active and meet the requirements of v1.12+

General Info

  • Locations must have Location Code provided or an error will occur
  • Client must exist in PrismHR
  • Exports the following fields:
    - Location.ClientNumber
    - Location.LocationCode
    - Location.LocationName
    - Location.GeoCode (PrismHR derived from ZipCode)
    - Location.AddressLine
    - Location.AddressLine2
    - Location.ZipCode
    - Location.ZipSuffix (not in ClientSpace, set to empty)
    - Location.State (sets PrismHR Location WorkCompState field)
    - If successful:
    • Export Status set to "Location Export Complete"
    • Export Log set to "Successfully created Location 'LOC4212' in PrismHR"

- If unsuccessful:

  • Export Status set to "Location Export Failed" or other API related lookup value
  • Export Log set to the error message from PrismHR, e.g.  "You cannot create another location with an existing code for the client 254"


New PrismHR Code Tables ENHANCEMENT

The HRIS system has been enhanced, adding Employment code tables to match the Employment records in PrismHR

New 'Job Code' Dataform:

  • Job Code as Text
  • Job Name as Text

New 'Division Code' Dataform:

  • Division Code as Text
  • Division Name as Text

New 'Department Code' Dataform:

  • Department Code as Text
  • Department Name as Text

New 'Shift Code' Dataform:

  • Shift Code as Text
  • Shift Name as Text

New 'Pay Group Code' Dataform:

  • Pay Group Code as Text
  • Pay Group Name as Text 
  • Pay Group Frequency as Lookup (use Pay Frequency lookup group)

On Employment the following parent form fields have been added, to take advantage of these new code tables:

  • new "Job" (parent field). Drop list should show the Job Name.
  • new "Division" (parent field). Drop list should show the Division Name.
  • new "Department" (parent field). Drop list should show the Department Name.
  • new "Shift" (parent field). Drop list should show the Shift Name.
  • new "Pay Group" (parent field). Drop list should show the Pay Group Name.

All parent fields are filtered to the current workspace only.


Performance tune peo_cs_employee_s_dashboard_search ENHANCEMENT

The underlying stored procedure for the employee search dashboard has been performance tuned to optimize performance.



32658

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.
32027

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....."
32364

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.
32101

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).
32737

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.
32960

PrismHR Events, error when an employee CREATE event is processed

Resolved an issue where PRismHR Event creation would cause errors due to "Create" Events being sent for an Employee that did not exist in the system yet due to the timing of the PrismHR_Ongoing import and the Event scheduled process.
32612

Unhandled Exception on Case Escalation creation

Resolved an issue in the SetCaseCategory business rule where attempting the add a Case escalation without a case category or type would cause an exception to be created. The SetCaseCategory rule will now only be triggered on Add if the Case Type is not blank.
32514

Icon on Case Discussion page is tiny

Icon size for attachments on the Case Discussion form has been increased to increase visibility.