![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2024\/06\/Shift-Log_100.png\")
<\/p>\n<\/p>\n
Shift Log version 4.19 includes:\u00a0<\/p>\n
Note<\/strong>: Before upgrading, always make sure your Environment has met Explorer minimum hardware requirements, as these are constantly evolving as additional capabilities are added.<\/p>\n This applies to A-Plus Entry, Case Entry, Log Entry, and General Entry components, as well as the Summary Table component.<\/p>\n Exclusions<\/strong>: Does not apply to the following Shift Log components: Logsheets, Single Log Form, Report \u2013 Form, Report \u2013 Grid, Report \u2013 Summary.<\/p>\n In Workbooks, entry tables can be configured to publish a specific value to a variable when a user clicks a row in the table, or the entry table refreshes. This allows greater interactivity between components in a workbook, and provides information with greater context.<\/p>\n For example, when a user clicks a row in the table, the name of the entity can be published, which in turn could allow an embedded trend on the same page to be updated.<\/p>\n For entity type fields, the value that is published can be either the name or the display name.<\/p>\n For multi-select lists, a comma-separated list of values is published. For Entry fields (subforms), the ID of the entry is published.<\/p>\n You can also publish the value of a column that is hidden in the table view.<\/p>\n Note<\/strong>: The following field types cannot be published to a variable: User, Text \u2013 Multi Line, and Merrick Form.<\/p>\n Changes to entry table columns for on row click selection<\/p>\n Structural Changes<\/strong><\/p>\n To accommodate publishing of variables from an entry table, and to further simplify how the entry tables work, the following changes have been made to the structure of all entry tables:<\/p>\n Opening an Entry Dialog<\/strong><\/p>\n As a single click is now used to publish variables, the following options have been provided to open an entry dialog:<\/p>\n The Email action in the Rules Engine has been updated to support sending emails via an Azure email server.<\/p>\n Two new options have been added to the Rules Engine group in the ServerConfig.xml file to enable Azure Communication Service emailing:<\/p>\n MailServerType<\/strong>: Set this to AzureCommunicationServices<\/em> for Azure connections, otherwise set this to smtp<\/em>.<\/p>\n MailServerAzureConnectionString<\/strong> should be set to the URL to access the Azure email service, e.g. \"endpoint=https:\/\/mscoe-azure-communication-service.communication.azure.com\/;accesskey=PYYGrvhjhHKenLvRljzrosOJs0wSBQ==\"<\/p>\n In the Entry Post Processing<\/strong> Rule Type, we have improved the user experience by enabling HTML markup for emails so that they can be sent with coloured text and other markup.<\/p>\n In previous releases, the Rules Engine only allowed plain text emails. With the addition of HTML markup support in this release, more engaging emails can be sent to notify users of Sentinel events that may require their attention.<\/p>\n In the \u2018Send an Email<\/strong>\u2019 action editor, a toggle has been added to enable the rich text editor. This allows you to add the following markups:<\/p>\n Note<\/strong>: Images cannot be inserted, and markup is not applied to tokens.<\/p>\n In the Call Web Service action for Entry Post Processing<\/em> and Scheduled<\/em> rule types, we have added the ability to add HTTP headers to the URL call.<\/p>\n These are key-value pairs that are appended to the request header, and support all HTTP methods<\/a>.<\/p>\n When the web service is executed, these headers are attached along with request.<\/p>\n This allows third party services (such as Webex) to be used to push messages. For example, if a case has been updated or changed, a message can be sent to a Webex group that contains the relevant users who need to ensure shift checks are completed before the end of a shift.<\/p>\n In the Scheduled<\/strong> Rule Type, you can now use the Call a Web Service<\/strong> action. This means that at scheduled intervals, you can now use custom applications for things like creating Shift Handover PDFs.<\/p>\n
\nPublish Variables from Selected Row<\/h2>\n
![\"Publish](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2025\/02\/image001-1.png\")
<\/a><\/p>\n\n
\n
<\/a><\/p>\nRules Email Action Supports Azure<\/h2>\n
Rules Email Action HTML Rich Text Support<\/h2>\n
\n
<\/a><\/p>\nRules Web Service Action Header Values<\/h2>\n
<\/a><\/p>\nRules Scheduled Type Supports Web Service action<\/h2>\n