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

Release 79 (Pulse) Notes

Owned by Diane Hogan (Deactivated)
Last updated: Apr 30, 2019
7 min read

The following items have been completed in this release.

Sprint Began: 4/1/2019     Sprint Ended: 4/30/2019

We moved the cheese!

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


Workspace search (Case 30068) ENHANCEMENT

Workspace search functionality has been enhanced to improve the user experience.

  • When adding records outside of a workspace, such as from a dashboard, Template workspaces are removed from the workspace selector.
  • When adding a dataform from a dashboard, only workspaces that include that dataform are listed (this includes the recent workspaces and workspace typeahead).
  • When adding a non-dataform from a dashboard (e.g., calendar), all available workspaces are listed. Template workspaces are never listed (Project.Template = 1).
  • The Recent Workspaces list now has additional filters for excluding Template workspaces and excluding workspaces that do not have access to the ProjectType being added (if it is not a dataform, that filter is removed).


Email templates: Attachments (Case 30463) ENHANCEMENT

The email template system has been enhanced to add email attachments. The System Admin can configure an email template to include a static attachment along with an Email Template.

When you initially save a new Email Template, the Attachment panel displays in the Action Center. The recipient of the Email generated by the Template receives any attachments added to the Attachment panel when the template is triggered. The Descriptive text on Step 5: Attachments includes a sentence indicating that after saving the Email Template, the Attachments panel displays so static attachments can be included.


 Workflow Channels: Improved experience (Case 33340) ENHANCEMENT

Workflow channels have been enhanced to improve the user experience when creating or editing a workflow channel item. Previously, when you clicked Finish at the end of the workflow channel wizard, the record would save and return the admin user to the channel as if nothing had happened. You would then use Cancel to exit the workflow creation process. 

The system has been augmented with a more elegant finishing process. When the system admin gets to the end of the initial item of a Workflow Channel, now there are buttons for Back, Continue, and Finish.

  • Click Back to return to the previous step of the Workflow Item.
  • Click Continue for a prompt stating "This Workflow Channel is unpublished. Would you like to publish?" with an option for Yes and No. Either selection takes you to the first step of a dependent Workflow Item.
  • Click Finish for a prompt stating "This Workflow Channel is unpublished. Would you like to publish?" with an option for Yes and No.
    • Yes returns you to the Workflow Channel search with the new Workflow Channel in a published state. 
    • No returns you to the Workflow Channel search with the new Workflow Channel in an unpublished state.
  • When you reach the end of a dependent item in a Workflow Channel, you can now click Back, Continue, or Finish. 
    • Back or Continue behavior mirrors the previously stated behavior.
    • Finish returns you to the Workflow Channel Detail page (the one with the Item list for a specific Workflow Channel).

When you return to the list, the new workflow channel will be in either the published or unpublished state that was selected when prompted.


Workflow Channels: Unpublish (Case 36238) ENHANCEMENT

The Workflow Channel system has been updated to make the publishing of workflow channels more consistent with other publishing functions. The Workflow Channels list now displays published Workflow Channels by default when initially opened. Unpublished Workflow Channels can be viewed by clicking Unpublished in the More search or by toggling the Status chiclet to Unpublished. When viewing the Workflow Channels list, you can view both published and unpublished from More search > All. Alternatively, while viewing the list, you can remove the Status chiclet.


Workflow Channel: Visualize (Case 37021) ENHANCEMENT

The Visualize system in Workflow Channel creation has been enhanced. Child workflow items are now displayed in the visualizer in the following format:

#<Item Number>: <Item Name>

This format matches the format used in the header of the workflow item detail, making the system easier to use.


 Workflow Channel: Publish/Unpublish (Case 37029) ENHANCEMENT

Workflow Channels have been enhanced to simplify the publish and unpublish process. The Workflow Channel list now contains a Publish check box in the rightmost column. Select the Publish check box to publish the channel. Clear the Publish check box to unpublish a channel. The formatting changes to bold and italics for an unpublished state.


Case Discussions (Case 37283) ENHANCEMENT

Case Discussion has been enhanced, adding the ability to switch between an employee’s work and personal email after a discussion has been started. Previously when an employee was added as a discussion recipient, after the message was sent, that employee would need to be removed and added back if the user wanted to change their email from Work to Personal or vice versa.


Email Templates: Publish when Finish (Case 37390) ENHANCEMENT

The Email Template system has been enhanced to include auto-publish functionality. As a final step of email template configuration, when you click Finish, a dialog box opens with "This email template is currently unpublished. Would you like to publish?" Click Yes or No. 

  • Yes returns the admin to the Email Template search page with the Email Template in a published state. 
  • No returns the admin to the Email Template search page with the Email Template in an unpublished state.


Workflow Channels: Improved selection options (Case 37440) ENHANCEMENT

Workflow channels have been enhanced to improve the selection options when cloning a dataform user field. When cloning a user datatype in a workflow, the admin is now presented with a dialog box that provides the option to select Current User, Specific User, or From a Field on a Form:

  • When selected, From a Field on a Form includes the triggering form for that workflow.
  • If a user datatype is not configured in a workflow channel, it defaults to business logic for setting that field, if applicable.
  • On a Case, the system ensures if the Assigned To is not configured on a workflow channel, business logic configured on the corresponding Case Type is used to fill the field, including Back Up Assigned To for a Client Role.
  • Cloning a user datatype field with configuration does NOT take precedence over business logic unless a specific business rule is written to avoid overwriting values set by workflow. Specifically, the PEO client service case has a method called SetAssignedtoUser that should defer to the Assigned to user set by the workflow.
  • If a user datatype is cloneable, but not configured, it renders a None. The system then defaults to business logic and works as if it is not cloneable.


This development also includes a script to convert existing user field values to a SpecificUser type.


Modules: Email Addin configuration (Case 37451) ENHANCEMENT

The Modules administration area has been enhanced to configure Email Addin modules. Using the field Email Addin Configuration, you can configure email to dataform mappings to fill fields in the newly created case or task using data from the selected email. Case or task fields are paired with email fields (use a SystemField=EmailField format). The pairings are semicolon separated with no spaces between them and no ending semicolon.

For example: Subject=Subject;CaseInfo=Body;EmailAddress=Sender;z_ClientReportDate=DateSent

The following Email fields are available for use in the configuration:

  • DateSent
  • Subject
  • Body
  • Sender
  • Recipient


Address change notification (Case 37501) ENHANCEMENT

The recipient stored procedure peo_employee_emailtemplate_recipient_v2_proc has been updated to return employee information when an email template triggers from an Employee or an Employment form. Previously this stored procedure would only return employee data if triggered by the Employee dataform.


New Billing Code Lookup Group (Case 37560) ENHANCEMENT

A new lookup group and associated lookups and metadata have been created for the Billing Code information. The new lookup group resolves an issue where previously the same Lookup group was being used with Vouchers. The decode should and could be changed when using Payroll Batches, but when the same lookup is also used for importing pay vouchers, the decode should not be changed because it is used with the import mapping API path.


Configurable introduction and confirmation text for the Employee Portal Case Widget (Case 37701) ENHANCEMENT

Two new fields have been added to the third-party integration section of the configuration page of the admin workspace. 

  • Employee Portal Introduction message allows the system administrator to configure the message that appears at the top of the dialog when creating a case from the Employee Portal.  
  • Employee Portal Confirmation message allows the system administrator to configure the message that appears when saving a case from the Employee Portal.




33016Interval indicator on recurring task configurationResolved an issue where the interval indicator on recurring tasks is required but did not turn red when cleared, indicating it is a required field as the Start and Due Date offsets do. The behavior is inconsistent and has been updated to match the offsets, turning red when cleared as well as presenting the error that the configuration is invalid.
36406Subscribers List UX issuesTemplate users no longer appear in the Select Subscribers list on dataforms that allow notifications
37322, 37323, 37324, 37325, 37326, 37327, 37328, 37329Remove Enterprise Library: ConfigurationParameterRepository

Core systems have been refactored to use a newer data access function. These systems include:

  • ConfigurationParameterRepository
  • CustomFieldDisplayRuleRepository
  • DashboardUserRepository
  • EmailActionRepository
  • EmailRepository
  • CalendarRepository
  • ContactRepository
  • DataformRepository
37680Email process continually erroring

Resolved an admin issue where saving a system email template would set the FromEmailOverride to an invalid value, causing email send issues.

37871Cannot open workflow Items

Resolved an issue where the IsTriggerable functionality caused unexpected behavior in workflow channel task items.

38125Mark for Deletion not displaying on ContentWorkflow channel task cloning has been enhanced to recognize Mark for Deletion. The enhancement allows for the creation of tasks through workflow channel cloning, which is automatically deleted through a scheduled process.