The following items have been completed in this release:
Sprint Began: 6/5/2018 Sprint Ended: 6/29/2018
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. |
The PrismHR API has been enhanced with INITIAL and ONGOING Client Code Import processes for Client Job, Department, Division and Shift
Import Maps (Configure Import)
Initial:
Classes of Data, Import API mapping
Ongoing:
- Ongoing imports will create queue records for available Events
- Ongoing Events are monitored, PrismHR Subscription forms must be updated to include these Client Codes
On the Client Master Subscription, add the following classes:
All PrismHR Client Code classes are available. See "https://api-docs.prismhr.com/1.11/clientmaster/get-code-tables-for-the-specified-client" for a list of available Client Codes that can be imported. The "Option" is the "Class" which must be added to the Client Master Subscription in order to monitor change Events
When configuring the Import Detail API path mappings use the following formats:
These import configurations will be pushed as Inactive and must be activated before use. For help configuring the subscriptions, contact Support
Lookup and Lookup group administration has been converted to our cross browser compatible application. The dataform action center has also been enhanced with the ability to manage the lookups specific to the dataform you are using through the "Show Lookups" action. For more information about configuring lookups and lookup groups, review "Adding or Configuring Lookups"
Create Workspace functionality has been added to the workspace search and secured using the "Can Create Workspace" option on the user profile. When clicked the system will:
For more information about the Create Workspace functionality, log an extranet case.
Workflow channels have been enhanced, adding the ability to clone Parent form fields, so that the foreign key relationship between forms based on Parent form fields can be preserved. An example of this could be as follows:
Previously Parent Form fields were not workflow cloneable in this way and did not appear in the selection list.
FkParentform fields (such as the Employee field in the case) will be available as "Parent field on a form"
Primary key fields such as the key of the Employee record which triggered the case will be available to select as "The Source Form". For more information about foreign key relationships and how to configure workflow channels, contact support.
Workflow Channels has been enhanced to make it more robust and easier to use, including:
The Workflow Channels system has been enhanced to trigger workflows based on File Upload type fields. Previously these fields were not available as a triggering field.
Help links have been configured for a number of non-dataform target types, including
Help for each of these items in now available from the help icon in the header
32676 | Employee Type Ahead Display & Inactive Employee Searching | Resolved an issue where when entering data in an Employee Type Ahead fieldonly the last name was displaying instead of the selection text - the system will now show the same information that is shown in the drop down list so that you know exactly which employee is selected. This was especially a problem, when more than one employee has the same last name which is common. Enhanced the system for the Employee Type Ahead field type to add the ability to search for inactive employees using the tiled (~) as a prefix, avoiding the issue of temporarily activating the employee record to select it then having to remember to inactivate it again. |
33425 | PrismHR Client Team Initial Imports | Resolved an issue where the Initial Client Team import could cause some importid's to be improperly generated. |
33451 | PrismHR Queue Intial Clients | Resolved an issue where when processing Client initial data, if a Client failed the getClientMaster call, it would cause all clients after that to fail. Now if an individual Client fails, that Client will be logged in the PrismHR API Log report, ignored, and the next Client will be processed (prior to this change the entire Client import process would abort). |
31760 | Recurring Calendar Message Display Issue | Resolved an issue where viewing a recurring calendar message in the inbox or email admin dashboard would display the raw vcalendar file. The system now displays the nicely formatted message as it does for non-recurring calendar items. |
31951 | WFC: Add Default User on Assigned To option | Resolved an issue where workflow tasks that were triggered from the API/Import, when the Task was triggered that it would be assigned to the "Public Anonymous" user. If no user is available such as at time of import the user fields will be set to the owner of the Triggered Workflow. |
33091 | Recurring Tasks available from Template Workspaces | Resolved an issue where recurring tasks were configurable on Template Workspaces, allowing the potential for these recurring tasks to be cloned inadvertantly. |
33103 | WFC - Initial Task does not email Assigned to User | Resolved an issue where workflow tasks would not email the Assigned to user if the current user who triggered the workflow was being set as the assigned to. |
33189 | Workflow generated Task not setting appropriate Start Date | Resolved an issue with Workflow tasks where the Start Date of the Workflow task was not being set properly if the field was configured to use "A field on a form", but always being set to the Create Date of the task. Start date is now properly set based on the configured method. |
33191 | Scheduled Process, post run update | Resolved an issue where a scheduled process with a next run date in the past would not correctly update the "Running" flag to "No" when completed, causing this flag to have to be manually reset before running the process again. "Running" flag is now appropriately set when the scheduled process completes. |
33283 | Email Template Recipient | Resolved an issue where if a recipient stored procedure is selected as the Source for Email Template addresses, the Type field would not be filled in, but it was required to move forward and save the email template configuration. The system now allows the configuration to be saved when recipient stored procedures are used. |
33443 | Error on save - Department Description Field | Resolved an issue where if any of the non-required fields on the Department record were left blank an error would occur as the database did not allow NULL values to be saved into the fields. System now allows the Department records to be saved without these non-essential fields. |