Sprint Began: 5/1/2018 Sprint Ended: 6/6/2018
The following items have been completed in this release:
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 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:
==Available Links==
==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 ==
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.
The contacts system has been enhanced to synchronize the default assigned to user with the associated organization.
The activity detail has been enhanced, adding a link to the action center which enables you to open the associated dataform
Tasks within the application have been enhanced to make them more organized and easier to use. These changes include the following:
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.
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.
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.
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).
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.
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.
All workflow condition fields for dataform checkboxes now have value dropdowns containing Unchecked and Checked.
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.
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.
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.
Additional indexes have been added to several system tables, making accessing the tables more efficient. These tables include:
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.
The user ImportID will now save. If not provided it will be set to the username
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....."
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.
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).
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.
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.