8.34.2 enableHR Tactical Release (16 December 2019)

Display of 'Objectives and Development' broken in eSS

Background (ENAB-3338)

There was an issue lodged with Self Service where Self Service users had lost the ability to view their own objectives and create new ones by submitting them through the Add an Objective form. Existing and newly created objectives in that the page were not loading for view and eSS people couldn’t add new objectives in Self Service as the form wouldn’t submit.

This was an eSS only issue as objectives could still be added and were still visible within the main application as per normal.

Update

This issue has now been fixed and the display and addition of Objectives and Development Items (in eSS) has now returned to normal.

Please note: if you are still seeing the issue, you may have a cached browser. Please press CTRL+SHIFT+DELETE and clear your cached images and files to before trying to login again to see the changes.

Broken letterhead functionality on document generation for account-level templates

Background (ENAB-3327)

As a part of release 8.33.6, we released additional functionality as a part of ENAB-2015 to give users more finite control over which letterhead to use for generated documents (the one defined at the branch the user is looking at or the letterhead defined at a higher level)

This new functionality works great for a majority of our standardised templates which almost always have a branch defined (associated to the record you are generating the document for) so the system can reference the new rules but we found that it doesn't work well for templates that don't have an associated record (such as in the case of our WHS templates which are about the account or the organisation as whole) which means the system can't reconcile which branch the account belongs to (because it doesn't belong to one) and therefore, can't reference the new rules about letterheads we set in place.

Update

Moving forward, we’ve taught the system an additional rule to work by: if the template is about the account (where no clear "branch" is defined), ddefault to using the account level letterhead instead.

This rule has been extended to cover any situations for templates where the system can’t identify which letterhead to use (as the very last fall-back point, use the account’s defined letterhead) 

Parent branch cannot be selected at the parent branch field when creating a new branch

Background (ENAB-2926)

As a part of account set-up, clients will usually initially sit down and create a number of branches to more closely resemble their own organisation and allow for data segregation by branches. When creating branches, we noticed that if you had selected another branch before clicking the New Branch button (happens when a user is trying to reference information from another branch and is usually auto-selected if creating another new branch prior), the branch selected would not appear as an option when choosing a Parent Branch.

Instead, users would be required to first create the new branch before going back and updating the branch's Parent Branch to the desired selection. This meant that if you were creating a number of branches, it would result in more administrative time spent in the Branches section of the account adjusting the structure before it was correct.

Update

Moving forward, this issue has now been fixed. You should be able to select the desired Parent Branch even if you were creating multiple branches or if you had the desired parent selected.

Issues with users toggling between branches

Background (ENAB-2886)

More information has been documented in-depth in the article: The Updated "Cookie Crumb" Branch Navigation Method however, the summary of the issue is that prior to the release, branch navigation for users with access to sub/child branches but no access to parent branches was difficult through the branch "Cookie Crumb" navigator. 

Update

Moving forward, the "Cookie Crumb" navigator has been updated to compile a user's options towards the left. Clicking on any of the buttons will allow the user to by-pass the parent branch that the user doesn't have access to and will navigate the user straight to the branch that they do have access to.