Release 84 Notes

Workflow Channels: Tabbed dataform options (38090) 

Workflow Channels now include all active tabbed forms on the Conditions step of a workflow item when the triggering form is the home form of a tabbed set.

• The Source list now includes all active tabbed forms in the tab set. In the Source list, the primary tabbed dataform precedes the child tabbed forms. The child tab names are prepended with a dash (–).
• The Field list is filtered based on the selected Source.
• Condition Expressions also follow AND/OR/NOT across the tabbed dataform conditions, enabling complex triggering conditions.

Workflow Channels: User source for tabbed dataforms (39529) 

The user type fields on workflow item tasks and dataforms now include any child forms in a tab relationship with the available selected dataform when the user source option of From a Field on a Form is selected. These tab form fields appear in the Field list below the primary form in the tabbed relationship and are formatted as follows:

*<ChildFormName> — <UserFieldName>

The asterisk denotes that the configuration is configured for a form that is not the triggering form. For example, if Form One is in a tabbed relationship with Forms Two and Three, and each form contains user fields, Form One displays in the Dataform field. The fields for Form One are at the top of the Field selector and fields from the child forms are available below the primary form in the following format:

• *Form Two -- User By Role (fkUserByRoleID)
• *Form Two -- Specialist User (fkSpecialistUserID)
• *Form Three -- Other User (fkOtherUserID)

For more information about this new functionality, review the article Workflow Channels and tabbed dataforms in our Knowledge Base or open a case with our Professional Services department. 

Email Templates: Tabbed dataform options (38671) 

Email Templates now include options for dataforms configured as tabs of the triggering dataform.

• In the Addresses step, the Source list includes all tabbed forms included in the tabbed set. These appear immediately below the triggering form in the list and are preceded by a dash (–).
• In the Conditions step, the Primary Trigger Field list only displays fields associated with the triggering dataform and includes the ability to Add Untriggered Field (as it currently does).
• In the Conditions step, the Trigger Field list also enables you to Add Untriggered Fields dynamically as well as current, active, triggerable fields from the source. 

Workflow Channel Visualizer (38710) 

The Workflow Channel Visualizer was enhanced to complement the new item level publishing of Workflow channels. Unpublished workflow channel items now display in a different color in italics to denote their unpublished status.

Workflow Channel item level publishing (38711) 

Workflow Channels now enable you to publish and unpublish channel items. A Publish option was added to Step 4 Conditions that enables the administrator to selectively enable and disable portions of workflow channels, without unpublishing the entire channel when adding new workflow items, the new option defaults to selected (On). 

New Business Rule (38922) 

A new business rule method _SetFieldFromProc enables you to set dataform fields based on information provided by a custom stored procedure. You can configure this rule to set a field on a triggering multiform using #thisform as the TargetForm. For information about implementing a custom stored procedure, contact Professional Services.

Workflow Channel multi-lookups as conditions (38994)  

Workflow Channel configuration now uses multi-lookup fields as triggering conditions. You can add each value from the multi-lookup as a separate "=" condition. This enhancement supports complex AND, OR, and NOT conditions.

Current Workflow Channel claim financial record (39036 and 40278) 

39036: The Workflow Channel claims system now contains logic to set the most recent claims financial record (based on VAO date and Date Created) as the current record. This helps to optimize reports that rely on the most recent financial record when calculating claim amounts.

40278: An index was added to the Claim Financial record to optimize the new current record feature.

Claim payment tracking (39039)  

A new Workers' Compensation Claims management dataform, Work Comp Claim Payment, tracks payments with the following configuration:

• The form is a multi-form child of Workers' Compensation Claim
• The form is secured to enable
  • Read-only access for the role PEO Employees 
  • Edit access for the role Risk_Member

The form fields are:

• Payee (text)
• Date Paid (date) 
• Paid Amount (money)
• Status (lookup with values of Pending (default), Scheduled, Paid, Cancelled)
• Pay Method (lookup with values of  Check, Online, Cash, Other)
• Payment Reference (text) - used for the check number
• Category (lookup with values of Indemnity, Expense, Medical, Legal)
• Category details (text wide)
• Exported (lookup: Yes/No default is No)
• Notes (text area)
• WCClaim - parent form; links to Workers' Compensation Claim from which the payment was created

The CalculateTotals business rule on the Claim Financial record now uses a new field on the Claim Financial form: Calculate Paid Totals (Yes/No lookup where blank = No)

• No: Calculates Financial record totals as it did before this enhancement, using the fields on the Financial form.
• Yes: Updates the Paid fields on the Current Financial record from the sums of the Claim Payments in Paid status, then sums the Financial amounts.

See Claim Payment tracking dataform.

Payroll Batch Dataform (39062)  COMING SOON

A new dataform stores payroll batch information. The Payroll Batch dataform is read-only and secured. By default, the form is secured with View rights for all users in the PEO Employees role. This new dataform contains the following fields:

All of the fields on this form are read-only and are filled using a PrismHR API Import. The Payroll Processor field is set using a new business rule that finds the Client Team form associated with the workspace and copies the Payroll Processor field information into the fkPayrollProcessor field. This rule is triggered when records are inserted either through a normal dataform save or from an import.  

Billing Voucher changes

A previous iteration of the Billing Voucher dataform contained some payroll batch information. With the addition of the Batch form, the batch level fields have been removed and a new field for Cost Amount (money) and Payroll Batch (fkPayrollBatchID - integer) was added. These Billing Voucher records break out the individual line item billing code entries associated with a payroll batch. A link was added to the Payroll Batch dataform to display the associated voucher records.

See Payroll Batch information.

Workflow Channel task triggering (39215) 

Workflow channel triggering conditions now enable you to trigger Task Workflow Channel items from the most recent parent dataform, even if the triggered Task is multiple levels deep. 

• On the Conditions step, the Source column includes the most recently referenced dataform that would trigger the initial task (single or multi).
• Condition Expressions operators (AND, OR, and NOT) work across multiple dataforms.
• IsDirty does not appear in the trigger operator list (since the task can be separated from the dataform by several other tasks, the dataform may not be dirty).
• The Add Untriggered functionality is available when adding fields from this source

If the most recent dataform is the main triggering dataform for the workflow, the condition source will be Channel Trigger: <NameOfTriggeringForm>.

If the most recent dataform is a cloned dataform workflow item, the condition source will be Workflow #<ItemNumber>: <ItemName>.

Email Templates: Multi-lookup conditions (39534) 

Email Template triggering now uses multi-lookup fields as triggering conditions (Step 4 Conditions). You can add each value from the multi-lookup as a separate "=" condition. This supports complex AND, OR, and NOT conditions as well.

Multi-lookup links (39535) 

The Custom Link configuration functionality now uses multi-lookup fields as triggering conditions. You can add each value from the multi-lookup as a separate "=" condition. This supports complex AND, OR, and NOT conditions.

Payroll Batch API/Import mappings (39583)  COMING SOON

Import Mappings were created in preparation for a future payroll batch import using the PrismHR API. This functionality relies on version 1.18 of the PrismHR API, which has not been released.

Notify External Employees from Client Service Case (39877) 

The Employee Address stored procedure was updated to include the work and personal email addresses of the employee associated with a client service case. In Step 3 Addresses, you can add the new fields (EmployeePersonalEmail and EmployeeWorkEmail) as either a To or CC address. You can use any email template created from the Case dataform.

Salesforce PEO process deprecated (40008) 

The older PEO Salesforce scheduled process has been deprecated in favor of the newer, more efficient CORE process. The functionality of the scheduled process remains the same.

Employee Benefits mappings (40019) 

In Employee Benefits, the following fields were added to the Employment form:

• Has Retirement: (Yes/No) - luHasRetirement
• Has Dependents: (Yes/No) - luHasDependents
• Enrolled Benefits: multi-lookup - mluEnrolledBenefits

The new fields have the following configured values for Enrolled Benefits options:

Code/ImportID - Decode

Field mappings for the new fields were added to HRPAPI_initial_employment and HRPAPI_employment import configurations.

The following fields were also marked as triggerable, enabling workflow channel and email template triggering to occur on changes to the following fields:

• mluEnrolledBenefits
• luHasRetirement
• luHasDependents
• isFICAexempt
• isFLSAexempt

Workflow Channels and Email Templates: Replace Fields from single dataform options (40023 and 40024) 

Field replacement on Workflow Channels now includes:

• Any active fields on the triggering dataform
• The active fields from any additional condition source dataform
• The active fields from the related Organization and Org Other Info
• Any fields returned by the Server Data Procs related to the triggering dataform  

Convert PrismHR API to REST (40052) 

The client and employee portions of the PrismHR API were converted to use a REST API from a SOAP API. The transition is seamless to the end-user and strengthens our ability to develop new import methods without having to rewrite the API connections each time.

Dataforms: Warning on removing child tab from dataform (40458) 

Dataform administration now performs a dependency check when you remove a child form from a tabbed dataform relationship. The dependency check ensures that the tabbed form is not used in triggering an email template or workflow channel. If there is a dependency, the system presents the message: 

	This dataform is used by the following System functions and cannot be removed as a tab while these dependencies are in place:

Additionally, the message provides a list of selectable links that are associated with email templates or workflow channels. The Delete button is disabled until all dependent processes with the related triggering conditions are removed.

Database table indexes (40543) 

The Time Tracking table now has indexes to optimize performance when managing time tracking.