Title: Release Notes For Version 11.5.54

0.1 Table Of Contents

Releases

1 Releases

1.1 11.5.0 August 23, 2023

Changes

Allow projects to be deleted without having to remove users first
- This was preventing properly-exported projects from being unexported.

1.2 11.5.1 September 8, 2023

Changes

Purge database of imported menus

1.3 11.5.2 September 13, 2023

Changes

Change error message when server detects possible bad permissions/algorithm
- When the permissions code detects a problem with shallow biskits preventing the permissions from being calcualted properly, it generates an error message explaining the situation.
- The message says the permission “may be badly defined (possibly in conjunction with other permissions).”
- A system event is recorded with this and extra information.
- We now store additional information to show more about the scenario so that the problem can be diagnosed later.
Add comment to rules
- There’s now a new tab shown in the rule editor where you put a description of the rule.
- If a rule has a description, then in the list of rules, the description will appear as a tooltip when the mouse hovers over it.
- Issue: 2433
Add workflow functions addResourceToBookmark & removeResourceFromBookmark
- addResourceToBookmark is a new workflow function that can be called to add a resource to a particular bookmark.
- removeResourceFromBookmark is a new workflow function that can be called to remove a resource from a particular bookmark.
- Issue: 2793

1.4 11.5.3 September 15, 2023

Changes

Add workflow validation that checks for non-deterministic execution order
- When a workflow event or action has multiple child actions, and those children all have the same sort order assigned to them, then it is not undefined what the order of execution will be.
- To make sure this is done correctly, the sort order on each action needs to be set to something different from all its siblings.
- There is now a check to look for this kind of thing so that anybody creating or editing workflows will be told when there’s a problem.

Bug Fixes

BUGFIX: Pairing a third or later shard leaves new UserFragment BiskitDef missing
- For each shard of number “N”, there should be a BiskitDef UserFragmentN that is a subtype of UserFragment.
- However, this was not happening.
- Issue: 3729

1.5 11.5.4 September 20, 2023

Bug Fixes

BUGFIX: Frozen-boot checker was prevented from running by frozen boot
- We sometimes have a problem with the boot sequence getting stuck.
- So there was some code added to dump all the stack traces to help understand what was wrong.
- However, it appears that while this worked in the development environment, it did not work in production when an actual problem occurred.
- We now change the way this works, and the way you must trigger it. To enable it:
  1. Enable verbose mode for com.springsolutions.exprodo.core.server.requestHandlers.DumpStackUtil
  2. Enable verbose mode for com.springsolutions.exprodo.core.server.requestHandlers.DumpStackUtil:showStacks
  3. In order to trigger an example problem for this to find, you can enable verbose mode for com.springsolutions.exprodo.core.server.requestHandlers.DumpStackUtil:test
- Note that if you want to enable it, then items 1 and 3 (if used) must be configured before restarting tomcat. Item 2 can be done on a running system without needed to restart tomcat.

1.6 11.5.5 September 24, 2023

Changes

Display request status on Enterprise Tools bakery items
- Add a column to each of the bakery items (validate biskit defs, update schema and reload db config) so show the current status of request in that row.
- Add a count that shows the number of currently executing requests.

Bug Fixes

BUGFIX: Boot sometimes fails and system does not work with message “Could not identify the request class I should build”
- Issue: 3926

1.7 11.5.6 October 3, 2023

Bug Fixes

BUGFIX: Remove false error message on importing a new user
- When a user is imported, a local fragment is created.
- That local fragment does not have the local fragment provided by the JSON coming from the main shard, and so it is not “JSON-provided”.
- However, as a fragment or a user, it’s a child biskit and so is considered as something that should generally be provided by the main shard.
- This is presented as an error, with a message saying jsonProvided != provided.
- But it’s really not an error - the code producing the error message just doesn’t understand what’s happening.
BUGFIX: SQL export of SortWorkflowAction fails
- If you create a workflow with a SortWorkflowAction and then use the workflow manager’s “Export” button to export the workflow to SQL, then this fails with a FreeMarker error complaining about the template.
- Issue: 3737
BUGFIX: Import of resource without specify Booking BiskitDef gives bad error
- Resources must have a Booking BiskitDef. You cannot create one without specifying this via the UI.
- However, if you use the CSV import to create a resource and do not provide the Booking BiskitDef, then you get a nasty error:
```
 Could not create resource: NullPointerException
```
- This is now replaced with a better message.
- Issue: 3739

1.8 11.5.7 October 5, 2023

Changes

Disable import approval button while import in progress
Add “quarter” and “yearQuarter” pseudo date properties
- In the same way that date and date-time properties have pseudo properties called year, month, hour, minute, yearMonth etc, they now have quarter (which is always valued from 1 to 4) and yearQuarter.
- The yearQuarter pseudo property produces values like 20234 (for the fourth quarter of the year 2023).
- Issue: 3740

Bug Fixes

BUGFIX: ShallowException on edit report and change systemWide
- This doesn’t go wrong the first time you do it, but it does thereafter.
- Edit a report in the report manager page, change the value of “System Wide” and save. This then gives an exception.
- Issue: 3709
BUGFIX: Remove group from exported Template Group and it can’t be imported
- Issue: 3734
BUGFIX: Export workflow with search action is bad if fetch from selected sources
- If you have an enterprise system, and create a workflow containing a SearchWorkflowAction, where the search is configured to use a selection of source shards (rather than search from all or search from local), then the generated SQL contains an error in the final set of comments.
- It shows that there was a problem generating the SQL, and that it could not produce something useful.
- It had the error message:
```
ERROR No table name for SearchWorkflowActionElement so I can't export instances
```
- Issue: 3735
BUGFIX: Booking formats come from current shard rather than resource home shard
- System settings specifies the default for the formats to use for the content and title of bookings on the calendar.
- Each resource can then override this by providing its own formats.
- So the system settings acts as a fallback.
- However, the format specifier might use any properties that are guaranteed to exist on the current shard, and this might not work for bookings that belong to a foreign shard.
- So now we use the fallback formats specified by the system settings on the shard from which the resource comes.
- Issue: 3736
BUGFIX: Export and Share buttons missing after logout/login
- When you view a biskit or a list of biskits, you might see a button labelled ‘Export’, for generating a SQL file that can be loaded into another system, or (on Enterprise) ‘Share’ and ‘Shareability’ buttons.
- If you log out, and then log back in, then these buttons do not appear.
- If you then refresh the browser, then they do appear.
- The types for which an Export button is displayed are:
  - Workflow
  - BiskitDef
  - Permission
  - Layout
  - UserWorkflowBiskitTypeButton
- Issue: 3741
BUGFIX: IssueTracker exception on search for issues with null type or status
- If you search for issues on the IssueTracker home page with either status “No status” selected or type “No type” selected, then the search gives an exception and provides no results.
- Issue: 3744

1.9 11.5.8 October 6, 2023

Changes

Prevent resources from being configured with iCal URL and requiring project
- Bookings imported from an iCal feed cannot set the project.
- Consequently, you should not be able to require a project on bookings for such a resource.
- Issue: 3477
Rename decodeId workflow function output “id” to “idNumber”
- It was not possible to access the “id” output value easily because it was confused with the output biskit’s primary key, which would always be zero.
- Issue: 3615
Add code to help debug CreateVariables bug
- There’s a bug that appears as though CreateVariables has no variables.
- This is only a display bug, as workflows continue to work normally while in this error state.
- This change is here to provide additional information the next time this error state occurs in order to help identify the cause of the problem
- Issue: 3711
Prevent the system user from being added to permission ‘Applies To’ tab
- Issue: 3716
Allow workflow function getBookingTemplates to use repeat bookings
- The workflow function getBookingTemplates finds all the templates covering either a booking, or a range of times.
- If you provide it with a booking, then it refuses if that booking is repeating.
- However, as of version 11.0, this is an unnecessary restriction now that repeats are handled differently.
- Issue: 3730

Security Fixes

SECURITY FIX: Update/Delete of things affecting perms do not refresh permissions
- Suppose:
  1. You have a permission that hides a resource if it’s a member of a particular resource group.
  2. You then modify the membership of that resource group
- Then the permissions continue to act as if the resource group had its previous contents.
- You can always work around this by doing any of the following:
  - Restarting tomcat
  - Reloading the DB config in the bakery
  - Edit/save any permission
  - Edit/save any user
  - Edit/save any user group
- Note that these last three items apply to editing an existing item, and not to either creating or deleting one.
- Issue: 3731,3732

Bug Fixes

BUGFIX: Export of Issue Tracker release notes workflow gives warnings in generated SQL
- The warnings relate to the SQL locating some biskits by their primary key when it should probably use a business key instead.
BUGFIX: Time interval grammatically incorrect when number is one
- For example, create a template and choose the far term template to be an alternative one.
- Then select “1” and “weeks”, and it shows the time duration as “1 weeks” whereas it should say “1 week”.
- The same is true for all time units, so it says “1 days” etc as well.
- Issue: 2384
BUGFIX: Cancel repeat template/booking drag to other resource not refresh
- If you drag a repeat template or booking and drop it on another resource, then the calendar immediately updates to show the dropped item in the column for the new resource.
- It then shows a pop-up asking which instances you want this change to apply to (this item, all items, or this and later).
- If you cancel that pop-up, then the calendar ought to move the dropped item back to where it started, but it doesn’t.
- Performing a refresh shows no change was made in the database, and it was just a display error.
- Issue: 3588
BUGFIX: Clicking on an ephemeral booking in a list shows ephemeral=false
- If you have a list of bookings that includes ephemeral bookings, and click on one to see the booking pop-up, then the pop-up will indicate that the booking is not ephemeral.
- Issue: 3605
BUGFIX: Last non-ephemeral appears in ephemerals in group report
- Suppose you create a daily repeat booking. Then with the system settings set to expand repeats for 90 days, it means the first 90 days will be stored in the database and beyond that, they are generated on-the-fly as needed from the last of those expanded bookings.
- Suppose you now create a group report showing the number of bookings by the ephemeral flag. Then click on the group where ephemeral is true.
- This shows all the bookings that are generated on-the-fly - those beyond the 90 days.
- But it also shows the last of the expanded bookings too.
- Issue: 3611
BUGFIX: Menu editor columns wrong defaults type for custom search page
- If you edit a menu and add a new item, and then set it to be a custom page and of type Customised Search Page, then the “Report Type” defaults to a group report.
- However, it shows the kanban property next to it instead of the group columns.
- Issue: 3635
BUGFIX: Name uniqueness not enforced or produces nasty error message
- Some things are named and should have unique names.
- In an Enterprise system, we require that it be a unique name per shard.
- However, some things had no uniqueness check on the name where it should, and some things would give a nasty error message when you tried to duplicate a name.
- This has been fixed for the items below, and for each item there is a marker to indicate its status from one of the following:
  - WG = Was good, and used custom code. Now uses generic code
  - NC = Not checked at all previously
  - BE = Bad Error message previously
- The changes have been applied to these types:
  - BookingDisplayFlag [WG]
  - BookingType [NC]
  - DownloadFormat [BE]
  - FAQCategory [BE]
  - LocalProjectType [BE]
  - LocalResourceType [BE]
  - LocalUserType [BE]
  - Permission [WG]
  - ProjectGroup [NC]
  - ProjectType [BE]
  - ReportType [BE]
  - Resource [WG]
  - ResourceGroup [NC]
  - ResourceType [WG]
  - ResourceUsageOutcome [BE]
  - UserGroup [NC]
  - UserType [BE]
- Issue: 3648,3649
BUGFIX: Contacts boot-time failure logged when APIServlet verbose setting not in DB
- The “Contacts” Exprodo application generates an exception at boot time if there isn’t a verbose setting stored in the database for the APIServlet class.
- This problem does not affect Calpendo, only the Contacts app.
- Issue: 3678
BUGFIX: “Repeats Affected” popup has extraneous comma
- When you edit a repeat booking, you get a pop-up that asks whether you want the change to apply to this item, this-and-later, or all items.
- There was a typo in the wording of the pop-up with an extraneous comma.
- Issue: 3704
BUGFIX: Newly created repeats not expanded enough if expand limit reduced
- If you reduce the number of days that repeats should be expanded, and then create a new repeat booking, then the new repeat booking will be expanded out to the number of days you asked for.
- But - since the system previously had expanded further, then it thinks everything is fully expanded out to a further date.
- This causes some problems where expansion does not happen where it should.
- Issue: 3705
BUGFIX: View old instances of ExprodoLicence gives exception
- Every time any Exprodo app boots or the system settings are modified, it creates an instance of the biskit “ExprodoLicence”.
- These then track what the licensing limits were at each point in time.
- It also tracks the version of the program installed and so it provides a good way to see when upgrades have been performed.
- However, if in version 11.0.0 you try to view an ExprodoLicence that was created in 10.1 or earlier, then it generates an exception.
- The message given is:
```
"Null value was assigned to a property of primitive type setter of
 com.springsolutions.exprodo.core.domain.ExprodoLicence.licenceServerInactivityGracePeriod"
```
- Issue: 3712
BUGFIX: Validation of biskit properties done too early
- In the bakery, you can indicate which properties are required, and what the min/max value of each property is (where appropriate).
- These limitations are checked after all automated properties have their values assigned.
- For example, if you specify the creator of a biskit should be stored in a particular property, then that would happen before the validation is performed.
- However, the validation was also being performed at an earlier stage, before these automated properties were set.
- Consequently, if you specify that the creator of a biskit is to be automated, and you indicate that it is required, then creating such a biskit would fail validation because it is checked before the creator is set up.
- Issue: 3713
BUGFIX: System broken if a permission set to apply to a system user
- If you configure a permission so that either the ‘Applies To’ or ‘Does Not Apply To’ tabs contain the system, then it causes mayhem.
- Only root users can log in, and the root user only sees an error when trying to view the permissions page.
- Issue: 3715
BUGFIX: Some parts of a workflow are assigned a new id every time the workflow is saved
- Each of the variables added to a Create Variables workflow action are stored in the database in their own row.
- Each time a workflow is saved to the database, those variables are assigned a brand new id number, when it would be better if they remained constant.
- Issue: 3717
BUGFIX: Add API method for returning name of the cookie that contains session ID
- Calpendo only uses one cookie, and it holds the user’s session ID.
- However, in an Enterprise system, each separate Calpendo shard within the federation has a different cookie name so that you can be logged in separately to each one.
- This means the format for the name of the cookie has changed in version 11.0, as it now includes the shard number in the cookie name.
- The name is now something like this:
```
session_id-407-Calpendo
```
- Most people won’t notice this change, although it does present a problem for anybody using the same API that our desktop app uses to log in and make direct calls.
- So there’s now an API call that will tell you the name of the cookie it’s using.
- The scripts at https://github.com/exprodo/api have been updated to use this new API method call (and are backwards-compatible if connecting to a Calpendo without it).
- Issue: 3718
BUGFIX: Automatic version number fails if prop name != column name
- If you configure automatic version numbering for a BiskitDef, and use a property whose name is different from its column name, then when you update an instance of this biskit, you will see an error pop-up briefly saying it can’t a column.
- The version number will also not be updated as it should be.
- Issue: 3721
BUGFIX: Menu editor group columns not editable on new custom search page
- If you add a new menu item to a menu, and set it to be a customised search page, then it shows an editor for the columns that you cannot edit.
- You have to click to another menu item and back again before it will let you edit the items.
- Issue: 3722
BUGFIX: Click on group in bookings group report can show nothing
- If there is any column where the property is found by a path through something else, rather than a simple property name, then clicking on a row in a group report shows nothing.
- For example, if there’s a column for dateRange.start.month, then it will fail.
- Or if there’s a column for owner.id, then it will fail.
- Issue: 3723
BUGFIX: Adding bogus property to booking content format breaks calendar
- One can customise the contents displayed on the calendar for a booking, either via system settings or resource-specific settings.
- It is entirely possible to provide a system setting for the displayed content that includes a non-existent property.
- When this happens, it was giving an exception so the calendar would display no bookings at all.
- Issue: 3724
BUGFIX: “Contains Member” condition relation allowed for tag set properties
- If you search for something that includes a tag set property, then when you add a condition on the tag set property, you are allowed to choose “contains member” and “does not contain member”.
- That has several problems with this:
  - Those relations are intended only to be used for groups
  - It’s confusing as it accepts relations “includes any” and “includes all”
  - It did not produce the result you might have expected
  - The wording suggests the value you select (“the member”) should be a single tag. However, the UI let you choose a set of tags.
- These relations are no longer selectable for a tag set property.
- Issue: 3725
BUGFIX: Dynamic notes waterfall fails with BiskitDef shallow exception
- Some (or possibly all) dynamic notes tabs, configured to display a waterfall of existing notes and enter a new note, give an exception when you view the tab.
- Issue: 3726
BUGFIX: Workflow created by root cannot be edited by others
- A workflow’s actions store the user roles that the action is empowered to run with. By default, it inherits these roles from the user that created the action.
- You can’t save a new version of a workflow if you do not have all the roles referenced by all the actions on that workflow.
- However, when a workflow is created by root, the roles sometimes include hidden values that are not displayable by the UI.
- So it may look like an action does not have any roles you don’t have, when it kind of does.
- I say “kind of” because this only applies where the value stored for the roles includes roles that are NOT defined as part of the current system roles.
- The root user created with Calpendo normally starts with all 32 possible roles, but the system will only display the 4 standard roles that exist.
- So these hidden roles can prevent you from modifying a workflow.
- Issue: 3727
BUGFIX: Export of workflow fails with SortWorkflowAction with null default
- If you export a workflow to SQL where the workflow:
  - has a SortWorkflowAction
  - where the sort action’s default weight is null
- then SQL file generation fails with an exception.
- Issue: 3735

1.10 11.5.9 October 13, 2023

Changes

Newly added workflow actions automatically choose a unique sort order
- It is the sortOrder property on a workflow action that is used to decide the execution order. If actions don’t have a unique value for the sort order then the execution order is no defined, and may be different from the display order you see in the UI.
- There is no an error generated when you view a workflow when there is a non-deterministic execution order.
- However, the likelihood of this happening should now be reduced. That’s because we previously created all actions with a default sort order of zero.
- Whereas now, we make sure the sort order is greater than the sort order of all siblings when a new action is added.
- This currently defaults a new action’s sort order to be at least 20 more than the maximum of its siblings, and always on a round number (divisible by 10).

1.11 11.5.10 October 26, 2023

Changes

Enterprise system settings set to reflect another shard’s settings can become out of sync
- In an Enterprise system, you can configure most system settings values to be taken from whatever the value is from another shard in the federation.
- However, it is possible for a shard’s idea of the remote setting to become out of sync.
- We now broadcast the system settings after a shard boots. This should make sure things remain in sync.

Bug Fixes

BUGFIX: Workflow function sendTwilioSMS had typo in argument name
- An argument was called “recepientNumber”, and this is now called “recipientNumber”.
- Issue: 3760
BUGFIX: Run predefined report on menu can erroneously fail owner perms check
- When running a report, it will check permissions for both the user running the report, and its owner.
- Sometimes, when this check is done, the owner details may be missing, so the server only has the user’s id number.
- Depending on how the permissions are defined, that may mean that the permissions check fails in Enterprise when it shouldn’t, so you get prevented from running a report that you should be able to run.
- Issue: 3762
BUGFIX: Deletion of foreign biskits from a report deletes nothing
- In an Enterprise system, if you have a list of biskits that includes some from a foreign system (because the report sources are set to include at least some other shards), then ticking one of those foreign biskits and clicking the “Delete” button would result in no action taking place.
- You would be asked whether you really want to delete it, but then it would not be deleted (indeed, the deletion would not be attempted).
- In a similar way, there are other actions that behind the scenes use the same code and also result in inaction:
  - Populating the resource usage calendar would only find local usage
  - Reordering bookmarks would only work on local bookmarks (although I’m not sure you’d ever have imported bookmarks, so maybe this doesn’t matter)
  - Updating the order of biskits displayed in a tree would ignore the foreign ones. This applies to the Rule Editor and Authentication Method editor.
- Issue: 3763
BUGFIX: Workflows are not deletable while they have associated events
- You can now delete workflows without having to edit them to remove all events first.
- Issue: 3764

1.12 11.5.11 October 31, 2023

Security Fixes

SECURITY FIX: Enterprise allowed you to add any role to users you can edit
- When you edit a user, if you are allowed to edit the fragment for one of the shards, then you could add a role in there.
- In non-Enterprise, there’s a rule that you can’t add a role to a user unless you have that role yourself.
- That was not applying to setting roles on user fragments, so that if you were an admin, you could edit your own account and upgrade yourself with the root role.
- Issue: 3772

Bug Fixes

BUGFIX: Enterprise Project “resource settings” resource filter for shard shows resource types, not shards
- When you create or edit a project, you can choose which resources appear in the resource settings.
- This provides various filters to let you narrow down the resources you can choose from.
- One of those filters lets you choose which shard the resource comes from.
- However, it doesn’t show the shards, and instead it shows resource types by mistake.
BUGFIX: Some biskit multi-selection drop downs were displaying unsorted
- In particular, the following showed a drop-down of options in an unsorted order:
  - On the booking search page, the resource drop-down.
  - On the actual usage calendar, the filter of outcomes.
  - Custom search pages displaying a multi-selector for a biskit-valued property.
- Issue: 3747
BUGFIX: Workflow subroutine calls forget arguments after restart
- Suppose you configure a workflow so that it will run a Call Subroutine action.
- Then after restarting tomcat, the subroutine will behave as if the arguments passed in were null.
- Editing the workflow and saving it will make it work again until tomcat is next restarted.
- Issue: 3767
BUGFIX: Record workflow that tries to sort an empty collection gives error
- This applies to both Sort Workflow Action and also Map Workflow Action.
- Both of these allow you to choose a collection of biskits that they operate on.
- In both cases, if you configure the workflow such that the collection they work on is empty (but not null), and you enable workflow debugger recording, then when the workflow runs, it generates an exception.
- Issue: 3769
BUGFIX: Reports use bad pluralisation grammar for number of things found
- In a non-Enterprise system, when you run a list report, it will say something like:
```
"Found 100 bookings"
```
  or “Found 1 bookings”
- In an Enterprise system, when you run a list report that fetches data only from the local system, then it will say something like:
```
"Found 100 bookings from 1 systems"
```
  or
```
"Found 1 bookings from 1 systems"
```
- Whereas on a non-Enterprise system, it should say:
```
"Found 1 booking"
```
  and an Enterprise system should say:
```
"Found 100 bookings from 1 system"
```
  and
```
"Found 1 booking from 1 system"
```
  and
```
"Found 1 booking from 5 systems"
```
- Issue: 3770
BUGFIX: Prevent “Shareability” buttons on booking, template & resource usage
- These types can never be shared in Enterprise, and so it makes no sense to have a Shareability button appear for them.
- Issue: 3771

1.13 11.5.12 November 2, 2023

Bug Fixes

BUGFIX: System fails to boot if any user is missing a fragment for their shard
- This bug was introduced in 11.5.11.
- If a user has been exported to a shard, but they have their user fragment for that shard missing (which means there’s no entry in the user_fragments table for that user and that shard) then the system would not boot.
BUGFIX: Could not add note to a dynamic notes area
- Trying to add a note would give an error:
```
"could not initialize proxy [BiskitDef#230822] - no Session"
```
- Issue: 3774
BUGFIX: Enterprise infinite loop exporting a user and re-exporting again
- Suppose you have:
  - an Enterprise Calpendo
  - with a custom property on Project that references a User
  - You have a user from shard #1 that is exported to shard #2
  - You create a project on shard #1 that is owned by this user but the project is not exported to shard #2.
- Then with that configuration, if you go to the user, click the Share button, and refresh the sharing to shard #2, then this sets up an infinite loop of continual sharing of the user from #1 to #2, with requests coming every second or so.
- Issue: 3775

1.14 11.5.13 November 8, 2023

Bug Fixes

BUGFIX: MetaProperties:user.projects not understand at design time by ForEach
- If you create a workflow with a user event and a ForEach action that is given MetaProperties.user.projects as the list to iterate over, then child actions do not know that the ForEach is providing a Project biskit.
- This means that child actions cannot directly access any of the standard project properties on the biskit because it doesn’t know it’s a project.
- Issue: 3776
BUGFIX: New Password dialogue auto submits when clicking on New Password field a second time
- Clicking with a mouse between the text fields in the change-password popup and be treated as though the ‘Apply’ button has been pressed.
- This is now changed so that you can only apply the password change either by:
  - Clicking the Apply button
  - Pressing the Enter key while the second password field has the focus
  - Pressing enter or spacebar while the Apply key has focus (using the tab key to get the focus there).
- Issue: 3780
BUGFIX: New password dialog does not give focus to the text boxes when it first appears
- When the “change password” dialog appears (either by you clicking “Change password” or by being forced to on login), the text boxes in the dialog are not given input focus.
- That means you can’t operate them using the keyboard alone, and you must click the mouse to activate it.
- Also, if the two passwords you enter are not the same as each other, then after the error dialog disappears, you should be left with the focus on something in the “Change password” dialog, but you must again click with the mouse.
- Now:
  - When the pop-up first appears, the old password field has input focus
  - If the two new passwords you enter do not match each other, then after the error popup is displayed, the first new password field has focus.
- Issue: 3784
BUGFIX: Adding an attachment to an already-exported project does not make a usable attachment on importing shards
- On an enterprise system, if you edit a biskit that is already exported, and add an attachment to it, then the importing side is updated, but the attachment does not work.
- This means you get a link for the attachment on the importing side, but clicking it does not download the file.
- Issue: 3785

1.15 11.5.14 November 13, 2023

Changes

Upgrade JsBarcode for client-side barcodes from 3.11.4 to 3.11.6
- JsBarcode is a third party library used for rendering barcodes in the browser.
- This can be done by configuring a string property in the bakery to have a string property type of “Barcode”.
Change order of (+) and (-) buttons in workflow actions
- When creating conditions, there are (+) and (-) buttons, in that order, at the end of each condition to allow you to add a new condition or delete one, respectively.
- In various workflow actions, there is a similar display of having a list of a variable number of items that can be added to and have items removed.
- However, these display the (+) and (-) buttons the other way around.
- This is now changed in workflows so that it increases consistency.
- Issue: 3794

Bug Fixes

BUGFIX: Export of user/project does not send fragments out as it should
- When a user or project is modified, a copy is sent to all shards that have imported it.
- There is normally a cloned copy sent to each so that they don’t interfere with each other, as we handle the fragments for each shard specially.
- However, the process of making that cloned copy had stopped working after changes to the way we handle auto-exporting biskits that were already exported and were then modified in 11.5.13.
- This meant that the export would not include all the fragments going to all shards, so that some shards would be missing fragments for some shards.
- As a consequence, the import would fail.
- Note that the fix means exports will no longer be wrong. It does not mean those exports can be imported.
- Issue: 3793

1.16 11.5.15 November 21, 2023

Bug Fixes

BUGFIX: Enterprise system would not boot if user nobody from another shard is imported
- Sometimes, a special user nobody could be exported.
- When this happens, the system would not boot - as it complained about there being too many ‘nobody’ users.
- It now distinguishes between those that are local and imported to avoid this problem.

1.17 11.5.16 November 22, 2023

Bug Fixes

BUGFIX: Joining new shard to federation sometimes fails
- The circumstances under which this happens are not known.
- But there are reports of triggering a bug with a ClassCastException showing in the logs, even though we can’t see how the circumstances of the bug arise.
- However, the bug is easily fixed.

1.18 11.5.17 November 23, 2023

Bug Fixes

BUGFIX: Joining new shard to federation sometimes fails
- This removes debug code accidentally left in in version 11.5.16 that meant the problem was not fixed in that version.

1.19 11.5.18 December 14, 2023

Bug Fixes

BUGFIX: Updating the order of imported booking rules fails
- Suppose you export a booking rule to another shard, so that on the importing shard, it has rules from foreign shards.
- Then in the rule editor, if you try to change the order of the rules by drag-and-drop, then it gives an exception.
- Issue: 3826
BUGFIX: Foreign-owned custom properties count towards a starter shard’s limit
- Issue: 3835

1.20 11.5.19 December 14, 2023

Bug Fixes

BUGFIX: Booking Display Flag not working correctly for Ephemeral bookings
- Both Booking.flags and Booking.ephemeral are created on-the-fly, with neither being in the database.
- So it’s a questionable thing to configure the conditions on booking flags to depend on the ephemeral property.
- It wasn’t operating as one might expect because the flags were calculated before expansion of repeats, which means there would be no ephemeral bookings yet.
- This has now changed so that it calculates the booking flags after expansion, so booking flag conditions can now use the ephemeral property in the way one would expect.
- Issue: 3614
BUGFIX: CustomTreePage shallow exception if click on uncached biskit
- For example, suppose you configure a CustomTreePage to show bookings.
- They are never cached, and so when you click on a node in the tree, the booking it is given is shallow (it has a type and id but carries no data).
- There was nothing to deshallow the biskit when you configure it to view a biskit property, so you got a shallow exception.
- Issue: 3634
BUGFIX: Linked Booking not use available child when another child unavailable
- Suppose you configure a linked booking to have two child resources, and that you want a minimum of 1 child linked booking, and a maximum of all (ie 2)
- and then suppose that one of those child bookings cannot be made because there’s a double booking at the same time
- then that should mean you just get the one child booking that can be made.
- However, it would instead complain about the one that could not be made, and you would get no child linked bookings at all.
- Issue: 3646
BUGFIX: Report columns lost when biskit type being searched for is changed
- This allows columns to be retained when changing the type of biskit, when they are consistent with the new BiskitDef.
- This only applies for List and Group reports. Other reports will reset as they used to.
- Issue: 3702
BUGFIX: Linked bookings do not work unless edit/save link
- After restarting Calpendo, all the linked booking links fail to do anything.
- If you create a new one or edit an existing one, then that one link will work properly until Calpendo is next restarted.
- Issue: 3749
BUGFIX: Upgrade from 10.1 to 11.0 fails on resource_usage_outcomes
- There’s sometimes a problem with upgrading from 10.1 to 11.0 where it fails on an update 10.4.0/11/1.
- This relates to the resource_usage_outcomes table, and setting up a new shard column and a unique key based on the shard and name.
- It appears that, depending on the configuration of the database server, this can fail to create the key.
- So we now limit the name column to 180 characters to avoid this problem.
- Issue: 3750
BUGFIX: Cannot attach file more than 5MB even with larger allowed size
- If you set a maximum size for uploaded files to be more than 5MB, then there is still a 5MB limit applied.
- Issue: 3765
BUGFIX: Workflow subroutine calls forget arguments after restart
- After restarting tomcat, any Call Subroutine workflow action will behave as if the arguments passed in were null.
- Editing the workflow and saving it will make it work again until tomcat is next restarted.
- Issue: 3767
BUGFIX: Starter & Lite licence complains about linked bookings but allows them to be created and they function
- Starter and Lite licences should not allow linked bookings to function.
- However, while they do complain when you create or update a link, it allows them to function.
- This has now been changed so that it does not allow them to function with a starter or lite licence.
- Issue: 3786
BUGFIX: User “nobody” can be deleted using checked-deletion
- You’re prevented from deleting the user “nobody”.
- But if you have a list of users, tick nobody and delete from there, then it lets you do it.
- This is a special user that must never be deleted.
- Issue: 3787
BUGFIX: Custom message for expired accounts is ignored
- When somebody tries to log in, but their account has been set to expired, then they are shown a default message.
- However, global preferences allows you to set a message that should be displayed in this situation, but it is ignored.
- Similarly when somebody tries to log in with an account whose status is requested.
- Issue: 3808
BUGFIX: Upgrade from 10.1 to 11.0 fails on MySQL 8.0.35
- Issue: 3832
BUGFIX: Database upgrade for 10.4.9/19/1 gives error upgrading to 11.0
- Issue: 3834
BUGFIX: Booking flags on ephemeral repeats show multiple times
- Suppose you create a booking flag with no conditions, so that it is always displayed.
- Then if you create a daily repeat booking, then in the ephemeral part of the calendar, the bookings show multiple copies of the flag when you are in a week view.
- Issue: 3836
BUGFIX: Remove duplıcates function gives lazy initialization exception with custom user field
- Suppose you have a custom property on a project to store a user, and you have a project there that custom property references somebody that is not the owner or one of the users on the project.
- Then a workflow that builds a list of users, owner and that custom property, followed by a call to the workflow function “removeDuplicates” will generate an error if the workflow is triggered by a database event running in the after-transaction database update phase.
- Issue: 3837
BUGFIX: Cannot view or edit calendar if booking is missing a required project
- Suppose you configure a resource so that it does not require a project, and then create a booking for it. Then, modify the resource to indicate that it does require a project. This will mean that pre-existing bookings are missing the required project.
- In this condition, the calendar does not behave very well, giving an exception when displaying the booking with missing project.
- This problem affects both week view and month view.
- Issue: 3838

1.21 11.5.20 January 10, 2024

Bug Fixes

BUGFIX: Fragment sub-types have wrong table name when edit their BiskitDef
- If you add any property to one of the subtypes of UserFragment or ProjectFragment in an Enterprise system, then the table name for that fragment will be given a prefix of “shardN_” where N is the shard number.
- This is not how fragment tables are named, and so this causes lots of problems.
BUGFIX: Manual request to update licence from licence server fails
- On the system settings page’s Licence tab, there’s a button that lets you request that the licence be updated by fetching from the licence server right now.
- This always fails on a production server as it does not send the required information in the request to the licence server.
- Issue: 3841

1.22 11.5.21 January 10, 2024

Bug Fixes

BUGFIX: Fix: Enterprise import of project using “nobody” gives error
- When importing a project that had a reference to a previously unimported “nobody” user, then the import failed with a message “No row with the given identifier exists”.
- Issue: 3845

1.23 11.5.22 January 15, 2024

Bug Fixes

BUGFIX: Enterprise tools’ Export Analysis breaks bakery saving of BiskitDef
- Once you run “Analyse Exports” inside Enterprise Tools in an Enterprise system, then you get an exception when you attempt to use the bakery to save the BiskitDef of the type whose exports were analysed.
- The only workaround is to restart Apache Tomcat.
- Issue: 3860

1.24 11.5.23 February 8, 2024

Changes

Simplified Fragment Analysis message when importer missing biskit copy
- You used to see a message like this when a biskit had been exported somewhere, but the importing side did not have a copy of the biskit:
```
Exported to Shard[pk=1 == 1[number=1, url=https://your.calpendo.com/, name=Main], but it does not have a copy of biskit
```
- This has now changed to a friendlier version:
```
Exported to Main (1), but it does not have a copy of biskit
```

Bug Fixes

BUGFIX: Report Manager has extraneous vertical spaces between items
- The Report Manager page shows items on multiple rows when you click on “system reports” or “personal reports”. There is:
  - Description of the search done most recently
  - A Create button
  - A count of how many items have been found
  - A table with the items found
- When these did not take up the whole of the vertical space, they were being displayed with large vertical gaps to make them use all the space.
- Issue: 3869
BUGFIX: Project not exportable in Enterprise when Project.owner marked required
- If you configure Project.owner in the bakery so that it is marked as “required”, then trying to export any project in an Enterprise system fails.
- An error is displayed saying something like “that project is a fully owned child, and so you must export the parent biskit instead”.
- Issue: 3875
BUGFIX: Approving queued import can get stuck for an extremely long time
- Issue: 3876
BUGFIX: Enterprise import of project with attachments fails on the attachments
- This generated the error:
```
Unsaved transient instance when importing an Attachment
```
- Issue: 3877

1.25 11.5.24 February 21, 2024

Bug Fixes

BUGFIX: Enterprise starter includes master-to-fragment props as custom prop
- There are 20 custom properties maximum in a starter system.
- If an Enterprise system includes a starter shard, then that starter shard was including the property added to each of user and project that references the local shard’s user or project fragment as a custom property.
- This is no longer included in the count.
- Issue: 3878
BUGFIX: Look at details of FederationImport in UI gives exception
- Click on a FederationImport row in a list of them, and it gives a shallow exception.
- Issue: 3879
BUGFIX: Unshared and deleted biskit reports false export analysis error
- Suppose you have a biskit that is first shared to another shard, then unshared, and then deleted from the original shard.
- Then performing an Export Analysis on it in the Enterprise Tools indicates an error when there isn’t one.
- Issue: 3880

1.26 11.5.25 March 22, 2024

Changes

Remove restriction that biskits cannot reference a fragment
- This now allows one to add a set of biskits to a user fragment or project fragment.
- Issue: 3907

Optimisations

Optimisation: Speed up sharing of user or project
- When you have many users and projects, then importing a user or project takes a lot longer than it should.
- Issue: 3906

Bug Fixes

BUGFIX: Checked-delete of an already-deleted biskit gives an exception
- Suppose you get a list of biskits, and then tick one or more of the check boxes, and delete them.
- Then, leaving them checked, ask to delete them again.
- This time, with the biskits already have been deleted, you get an error message saying “NullPointerException” instead of something more sensible.
- Issue: 3901
BUGFIX: Unsharing a user results in exporter & other importers still seeing unshared fragment
- Suppose you have a user that belongs to shard 1, and the user is shared to shards 2 and 3.
- Then on shards 1, 2 and 3, you would see that the user has a fragment for all three of those shards.
- You can see this by looking at the tabs that are displayed for the user.
- If you then unshare the user from shard 3, then you should see:
  - That the user is no longer present on shard 3
  - That the copy of the user on shards 1 and 2 should have no fragment for shard 3.
- However, while the first of these was working (user deleted on shard 3), the remainder was not. All other shards retained a fragment of the user for shard 3.
- Issue: 3902,3903
BUGFIX: Enterprise import of a biskit with a new one-to-many property fails
- In an Enterprise system, suppose you use the bakery to add a new one-to-many relationship to a biskit.
- Then update the DB schema and reload the DB config, but do not do the same on other shards.
- Then create or edit a biskit of the affected type, and add one or more child (using the new one-to-many property).
- Export that biskit to another shard.
- Then on the importing side, import the bakery change and apply that in the bakery.
- Then, when you approve the import of the biskit that you created or edited, the import fails with an error about the child biskits.
- Issue: 3904

1.27 11.5.26 March 28, 2024

Bug Fixes

BUGFIX: Enterprise import of a workflow fails
- Importing a workflow with biskit create, biskit update or function actions (amongst others) fails with an exception.
- This is a problem that was introduced by the fix to issue 3877 “Import of project with attachments fails on the attachments”.
- Issue: 3914

1.28 11.5.27 April 9, 2024

Bug Fixes

BUGFIX: Enterprise unimport allowed data deletion while still referenced
- When you unshare a biskit, that means it is deleted from the importing side.
- This was allowed to happen even while there were still references to that biskit on the importing side.
- We normally have the database always checking that everything we reference, exists.
- However, Enterprise imports are done with these referential integrity checks turned off to avoid difficulties of importing a tree of objects.
- We have checks before import to make sure nothing will reference anything that does not exist at the end, but this did not apply when deleting things.
- Referential integrity checks are now applied while doing an deleting something for an unimport.
- Issue: 3918
BUGFIX: Browser says server down if imported project has non-imported resource
- In 11.5.26, exporting a project will result in the ProjectResourceSettings always being imported - even if the PRS references a resource that has not been imported.
- This results in the PRS referencing a non-existent resource.
- In this situation, trying to use the importing shard fails after login with a message saying the server is down.
- Only 11.5.26 will allow this situation to be created. In earlier and later versions, the import will ignore any PRS that reference a resources that has not been imported.
- Issue: 3919
BUGFIX: Importing a project with a PRS for non-imported resource still imports the PRS
- In 11.5.26, exporting a project will result in the ProjectResourceSettings always being imported - even if the PRS references a resource that has not been imported.
- This results in the PRS referencing a non-existent resource.
- The import should ignore any PRS that references a resources that has not been imported.
- This fix includes reverting the fixes for issues 3877 and 3914, and fixing them all in a better way.
- Issue: 3920,3877,3914

1.29 11.5.28 April 18, 2024

Bug Fixes

BUGFIX: Enterprise attachments on non-imported biskits cannot be downloaded
- Suppose you add an attachment to a biskit that is not imported (eg a booking), and then run a search on another shard that includes seeing that biskit.
- Then click on the attachment, and it gives you a 404 error.
- Issue: 3937

1.30 11.5.29 April 19, 2024

Bug Fixes

BUGFIX: Click on Define Subroutine action with abstract base type gives error
- Suppose you create a new BiskitDef in the bakery, and mark it as abstract and that it does not share its table with subtypes.
- (One might do this to create a grouping in the bakery, and also to provide a top-level set of properties that might be shared amongst related biskit types).
- Then in the workflow manager, create a Define Subroutine action, and assign an input as a list of biskits of the type just created.
- Then whenever you click on that action, it displays an error that says “X is not mapped” where “X” is the type of the BiskitDef you created.
- Issue: 3942
BUGFIX: Formulaic property referencing property on specific fragment fails
- On an Enterprise system, a booking formula like [project.fragment2.x] should be able to access property x on fragment 2 of the booking’s project.
- However, it got mangled and generated a SQL formula that was quite wrong.
- Issue: 3943
BUGFIX: Resources marked as not using drag-and-drop sometimes do so
- When you move from week to week in the booking calendar, or click the refresh button that’s inside the bookings calendar, then the onscreen widgets used to display bookings are re-used for the new display. This is an optimisation to make it faster that has been in place for a long time.
- However, this re-use of these items means that it mixes up those items for which drag-and-drop is supposed to be enabled, and those for which it is supposed to be disabled.
- One can choose whether drag-and-drop is supported on a per-resource basis.
- Issue: 3944
BUGFIX: Before-transaction Create database workflow event is never triggered
- Suppose you create a database event, and mark it as running when something is created only, and to run in the before-transaction phase.
- Then create a biskit of the same type that the event is targeted at, and the event does not run.
- This bug was introduced in 11.0.4.5 and 11.5.5.
- Issue: 3950
BUGFIX: Memory leak kills server when repeatedly update DB schema and reload DB config
- Issue: 3951

1.31 11.5.30 May 3, 2024

Changes

Show tentative bookings by default when CTMS not loaded
- There was a change a while ago so that tentative bookings would not be displayed by default.
- This was done because CTMS generates a very large number of tentative bookings, which are not generally wanted cluttering up the calendar.
- Now the default will now be to show tentative bookings when CTMS is not loaded, and hide them otherwise.
- Issue: 3916

Bug Fixes

BUGFIX: Workflow search doesn’t fetch sub-type properties on remote requests
- When a search workflow action fetches data from anything other than just the local shard, then it did so with a report that fetched the columns that exist on the type specified.
- This means that if the type you’re searching for is actually a subtype, then the properties that exist on the subtype were not populated.
- Issue: 3952

1.32 11.5.31 May 8, 2024

Changes

Remove lastRepeat from Booking, Template and TotalTimeBookedTimeMask
- The property Booking.lastRepeat and Template.lastRepeat indicated when a booking or template that repeats would have its very last instance.
- Now that repeat bookings and templates are expanded in the database (out to 90 days or so) then it no longer makes sense to have this on every booking.
- It also caused other problems to have it, and could not be kept up to date in the same manner that it was in 10.1 and earlier.
- So this property has now been removed.
- Issue: 3887
Add support for “includes time between” and “does not include time between” condition relations
- When you create a report from the bookings search page, Calpendo generates some conditions for the things you want the report to include.
- These conditions include a part that covers the start and finish date/time that you specify on the report.
- The conditions used for the start/finish times were complicated, with multiple conditions working together, and not at all intuitive.
- These have now been replaced with a single condition that will say something like:
```
Value of dateRange includes time between May 1, 2024 and May 8, 2024
```
- This condition is then converted behind the scenes to something that handles the complexity involved with repeat bookings so that it finds all the things it should.
- This makes conditions on a report much more comprehensible.
- The new “includes time between” relation is also available for users to use directly in their own reports, along with the inverse “does not include time between”.
- Issue: 3892
Change default dateRange conditions to use ‘includes time between’
- When you use the general search page and search for Resource Usage, it now defaults to using the new “Includes time between” relation to provide a default filter.
- It does this over the same period as before, from 14 days ago to 14 days from now, but it now calculates when those dates are and explicitly uses them rather than using “now plus 14 days” which is not (yet) supported by the “Includes time between”.
- When you use the general search page and search for Booking, this does exactly the same thing as for Resource Usage.
- The old default of searching for bookings from 14 days ago to 14 days from now did not correctly find repeat bookings, whereas the new “Includes time between” does.
- Issue: 3900,3925
Add includes-time-between relation to Biskit Query API
- This allows a URL like this to search for bookings between certain dates:
```
 https://mysystem.calpendo.com/api/q/Calpendo.Booking/dateRange/includes_time_between/20250430.105900-20250614.180000/
```
- Note that other API relations for searching for bookings do not take into account repeats and how they work.
- Anybody attempting to obtain bookings or templates within a set period is encouraged to use this new includes-time-between method.
- Note also that the format of the two dates for an includes-time-between in the URL is much stricter than the query API generally supports.
- The syntax is like this:
```
/includes_time_between/yyyymmdd.hhmmss-yyyymmdd.hhmmss/
```
- Each of the date-time values are like this:
```
yyyymmdd.hhmmss
```
- but can alternatively miss out the seconds:
```
yyyymmdd.hhmm
```
- or can simply be the string:
```
now
```
- Issue: 3936

Bug Fixes

BUGFIX: Child linked bookings updated even when they break bookings rules
- Suppose you have a linked booking configured, and you have a parent booking and a child booking (or child bookings), and then you change the time of the parent such that one of the children would clash with a pre-existing booking, thereby contravening a double booking rule.
- Then the user would be shown an error message telling them the child had broken the rule, but all children would still be modified.
- In other words, it would allow the child to break the double booking rule (or in fact any rule).
- Issue: 3706
BUGFIX: Authentication buttons don’t appear in order set by drag & drop
- You can change the order of authentication methods by using drag & drop in the authentication method editor.
- However, the order that you then set is not reflected in the order of the displayed buttons on the login page.
- Issue: 3777
BUGFIX: Reminder Manager does not start
- No reminders are sent in 11.0 and no system events are generated by the Reminder Manager.
- Issue: 3844
BUGFIX: Group report of bookings showing linked parent fails
- If you have a group report of bookings that includes any child of a linked booking, then adding a column to the report to show linkedBookingParent gives an exception.
- Issue: 3851
BUGFIX: Bakery references to BiskitDef gives exception
- Asking for references to any non-abstract BiskitDef in the bakery generates an exception.
- Issue: 3852
BUGFIX: Database dump file not loadable on recent MySQL servers
- If you generate a database dump using Calpendo 11.0.0 to 11.0.4.2, then the result cannot be loaded into MySQL.
- It complains that it cannot assign a value to a generated column.
- Issue: 3889
BUGFIX: Import of external iCal feed fails to import anything
- One can configure a resource in Calpendo to contain bookings that come in from an external system. For example, from a Google Calendar or other system, you can generate a URL that you can give to Calpendo, so Calpendo will create a booking to represent every item found on the Google calendar.
- This worked in 10.1, but in 11.0 it fails to import anything.
- Issue: 3927
BUGFIX: Edit ‘Includes time between’ conditions gives ‘accuracy not set’ error
- If you go to Search>Search and search for Bookings, then you get some default conditions that uses the ‘includes time between’ relation.
- If you run the report as-is, then it works.
- If you click the Conditions button and then click the OK button (without even changing anything), then you get an error telling you that the Date accuracy is not set and it was expected to be.
- Issue: 3929
BUGFIX: Linked bookings min children of “All” does not treat any handle double-booking breakage on child incorrectly
- If you specify that the minimum number of child bookings required for a linked booking is “All”, then whenever a child is refused (eg by a booking rule), then the message you see indicates that it is not considered an error (which is incorrect) and the parent booking is allowed to happen (which is also incorrect).
- Issue: 3945
BUGFIX: Linked booking messages are confusing when a child is refused due to breaking a booking rule
- If a child linked booking is refused, perhaps because it breaks a booking rule, then the error that is displayed is confusing.
- We have now improved the message.
- Issue: 3946
BUGFIX: iCal import generates duplicate bookings and double booking warnings
- If you set up an iCal import, then all the imported bookings should have a unique iCal ID stored on each booking (property name is iCalUid).
- This ID is generated by the remote system that is the source of the iCal feed.
- We store the ID so that when we synchronise with the remote system, we know which of the bookings in our database relates to the items in the feed.
- However, the iCal unique ID was not being written to the database due to the changes that happened between 10.1 and 11.0.
- This meant that the first import would work okay, but the second time it would fail.
- That’s because the incoming bookings could not be matched to any pre-existing bookings, since none of them stored the iCal unique ID.
- But every incoming iCal item was at the same time as the booking created when we first imported the iCal feed, and this would then generate an error as it failed a double booking rule.
- Issue: 3947
BUGFIX: iCal import subjects imported bookings to rules and limits on old bookings Type
- When an iCal import takes place, then the idea is that the bookings in Calpendo should be a reflection of the items that exist in the remote calendar.
- If the remote calendar includes historical items, then that’s what should be created in Calpendo.
- If the remote calendar has items that are at the same time, then that’s what should happen in Calpendo.
- However, all booking rules and limits on historical bookings were being applied to bookings imported via iCal, which doesn’t make sense.
- Issue: 3948
BUGFIX: Error if click on Booking group report with project.type for row where no project
- Suppose you create a group report of bookings, and add a column for project.type.
- Add a condition to show only bookings with no project.
- Then clicking on the row in the group report gives an exception saying
```
"Cannot read properties of null"
```
- Issue: 3949
BUGFIX: Repeats table uses date-time column for date-no-time properties start and finish
- The repeats table now uses the type ‘date’ rather than ‘datetime’ for columns ‘start’ and ‘finish’.
- This matches the bakery properties Repeat.start and Repeat.finish which were (correctly) defined as being of type Date and not Datetime.
- Issue: 3954

1.33 11.5.32 May 21, 2024

Bug Fixes

BUGFIX: Holiday Rule cannot be opened from #search
- If a Holiday rule is created, and at least one holiday date added to it, then if you go to the standard search page, search for a holiday rule and display it, you get an exception.
- Issue: 3962
BUGFIX: User and Project lose links when resharing
- Suppose:
  - a user has already been exported from shard A to shard B
  - and the user belongs to a project on shard A
  - and the project is exported to shard B
- Then if you reshare the user to shard B, the user forgets that it is related to the project on shard B, and the project on shard B forgets that it contains the user.
- This does not affect the exporting side (shard A in this example).
- Issue: 3963
BUGFIX: Before transaction workflow event overwrites old value of a property
- Suppose you set up a workflow so that a database event runs before-transaction when a booking is updated, and it changes the description on the booking.
- Suppose further that there’s another database event, but this one is triggered during-transaction. In this event, set up a templated text to show the old value of the booking start time and the new value.
- Then if you edit a booking and change its start time, the second workflow should see the old and new value of the start time as being different. But instead, it shows them as the same, and equal to the new value.
- Issue: 3964
BUGFIX: Logging in to Enterprise shard with inoperative user gives no message
- Suppose you have a user whose account has been exported to a particular shard, but their user status on that shard is set to “Inoperative”.
- This means the user account was exported without any specific request for the user to have login access.
- Then in this state, if the user tries to log in, they will not be allowed to log in, but they will not be shown any reason why not.
- They just see a red-bordered box with no message inside.
- Issue: 3966
BUGFIX: Workflow search does not filter selected shards by user’s access
- When a workflow is run on behalf of a particular user (eg a user modifies a biskit and it triggers a database event, or a user selects a menu option that runs a user workflow event), then that user’s access should limit what the workflow can do.
- When a search workflow action specifies selected shards to search, rather than “all” or “local”, then the request is sent to all those shards regardless of the user’s access to them.
- Issue: 3967
BUGFIX: After running assertActiveUser, a workflow search fetching from everywhere only fetches from local shard
- The workflow function ‘assertActiveUser’ can be used to indicate who the workflow is working on behalf of whenever there isn’t a specific user.
- For example, a timed event or an anonymous http event have no user that initiated the workflow, whereas if a user updates a biskit and that triggers a database event, then there is a specific user.
- If there is already a specific user and the ‘assertActiveUser’ function is called, then it does nothing at all (effectively ignored).
- Suppose:
  1. A timed event runs (or any event without a specific user) and the workflow function ‘assertActiveUser’ is used to identify the user
  2. The user is specified as a fixed value rather than a variable one
  3. The workflow then runs a search action and specifies that it should fetch data from everywhere
- Then only the local shard will provide results
- Issue: 3968
BUGFIX: Exception when workflow search selects only foreign shard sources
- If you choose that a search workflow action should search from particular shards, and you don’t include the local shard, then the server throws an exception and the search fails.
- Issue: 3969

1.34 11.5.33 June 11, 2024

Bug Fixes

BUGFIX: Unsharing a missing workflow gives an exception
- Suppose you have exported a workflow (or indeed any biskit) to another shard, but somehow that importing shard does not have a copy of the biskit in its database. (Maybe it was deleted separately, or the import request was queued and deleted before it was acted upon).
- Then on the exporting shard, if you try to unshare the biskit, it will fail and display an error.
- Issue: 3989
BUGFIX: An Enterprise project list report projects fails if status property is hidden
- Suppose you have an Enterprise Calpendo and have a permission that allows the action “Export to Federation” for projects when the status is approved.
- Further if you set up a list report of projects, and do not display the status property in the list, then when the report runs, it generates a shallow exception.
- Issue: 3990

1.35 11.5.34 June 18, 2024

Changes

Add verbose-controlled debug logging for downloading attachments
- You can enable and disable additional logging by visiting the #verbose page.
- We now have additional entries in there for:
  - com.springsolutions.exprodo.core.server.AttachmentDownloadHandler
  - com.springsolutions.exprodo.core.server.HttpRequestEnvelope
- There is also now additional logging done for:
  - com.springsolutions.exprodo.core.server.ExprodoSessionDAO
- If you edit the entries for all the above 3 items, and set their verbose setting to “true”, then more information will be sent to the tomcat log file.
- Whenever somebody does anything to contact a Calpendo, HttpRequestEnvelope will show what it thinks is the user’s IP address, and why.
- If you try to download an attachment, then you will see entries from AttachmentDownloadHandler and ExprodoSessionDAO.
- These settings should not be generally on in production, although they can be briefly while investigations are performed.
- Issue: 4016

Security Fixes

SECURITY FIX: Users can duplicate templates - ignoring permissions
- Any user that can see the template calendar can click on a template, and click the “Duplicate Across Resources” option.
- This happens even if permissions say the user cannot create templates.
- This security hole only applies to users with access to the template calendar and only allows an existing template to be duplicated; users cannot choose anything at all about the newly created template apart from the resource it applies to.
- No other changes to data are in any way affected by this - it’s limited to duplicating templates across resources.
- Issue: 3908

Bug Fixes

BUGFIX: High volume of permissions could crash booking tooltip request
- When there is a high quantity of booking property READ permissions and custom booking tooltip content, then the tooltip display can generate an exception in the server.
- Issue: 3807
BUGFIX: hibernate.connection.url set incorrectly in sample-hibernate-mariadb.cfg.xml
- Those who host their own Calpendo will download an archive that includes, amongst other things, a file called sample-hibernate-mariadb.cfg.xml
- This file needs to be edited to match the database environment.
- However, some changes in version 11.0 were not reflected in this file, which was using the wrong protocol for MariaDB databases.
- It should have used “jdbc:mariadb” as the protocol, but was using “jdbc:mysql”.
- Issue: 3972
BUGFIX: Linked booking link child property setting disappears
- If you set a fixed value for a property on the “child properties” tab of a linked booking link, then that value will usually (although not always) be lost by the user interface.
- When you first set up such a property, then it will be saved properly, even if after the save the value is not displayed.
- However, from that point, if you edit the linked booking link again, then the value would be lost.
- Issue: 3976
BUGFIX: Custom search page with filter for date-time property gives exception
- If you set up a custom search page and the filter includes a property that stores a date-time, then the search will generate an exception unless there is no data to match the search filter options selected.
- Issue: 3977
BUGFIX: Remove lastRepeat columns from list reports
- The lastRepeat property has been removed from Booking and Template, with no replacement property. This is a breaking change required by the changes to the way repeats work in 11.0.
- We now have warnings in place if anything references these properties.
- This means that when an upgrade from 10.1 to 11.0 is performed, we may see these warnings.
- In the case of list reports of bookings or templates with columns that reference lastRepeat, the only action is to remove the column.
- Users will probably not even notice the column being removed, and probably won’t have used the column.
- So having a warning about these list report columns is not helpful. That is, we can and should automatically delete the columns which would mean an upgrade from 10.1 to 11.0 would be less likely to generate warnings, which in turn means the process of upgrading many Calpendos from 10.1 to 11.0 becomes easier to manage (since every time there are warnings, they would have to be investigated and handled).
- Issue: 3979
BUGFIX: Error in standard “Exception to email” workflow
- There is a bug in the standard workflow “Exception to email” that exists in any system that was first created in 10.1.x. Anything created in 10.0.x or earlier, and 11.0 or later did not have the problem.
- There is an action to send an email, and one of the properties written into the email is SystemEvent.user.userIdentity, but now that SystemEvent.user is the base User type (since it might be an ExprodoUser or a SystemUser causing an event), there is no SystemEvent.user.userIdentity property.
- Issue: 3980
BUGFIX: Show error when report or permission that references unknown props is displayed
- This is here in particular because version 11.0 has removed properties Booking.lastRepeat and Template.lastRepeat, with no alternative properties to replace them.
- This is a breaking change, and any reports that referenced those properties will no longer work.
- Consequently, when you now try to look at such a report or permission, it will show an error telling you about the properties it does not recognise.
- Issue: 3981
BUGFIX: Bakery allows you to create a new BiskitDef with clashing biskit type
- The biskit type on all BiskitDefs must be unique.
- However, nothing enforced that uniqueness so that you were able to create BiskitDefs with duplicated biskit types.
- In lots of places there are assumptions that the biskit type uniquely identifies a BiskitDef, and so non-uniqueness of the type can cause problems.
- Issue: 3983
BUGFIX: Exception displayed on calendar when project has an associated user that does not exist
- Issue: 4012
BUGFIX: Get nasty error if an unimport request fails due to being referenced
- In an Enterprise system, if you try to unshare a user that has been shared to a shard where it is referenced, then you get an unfriendly error message instead of a good one.
- Issue: 4013
BUGFIX: Enterprise Query API calls ignore any conditions set in the URL
- In an Enterprise system, if you add conditions to a biskit Query API request that you ask to fetch data from all shards (or a selection of shards), then the conditions are ignored and the results reflect what you would get if you had specified no conditions at all.
- Note that you can specify all shards by appending “&shards=all” to the URL.
- Issue: 4014
BUGFIX: Enterprise Query API fails “&shards=all” if not a user on all shards
- You can specify that a query API call should fetch data from all shards by appending “&shards=all” to the URL.
- However, doing so will fail unless you are a user on every shard.
- Issue: 4015

1.36 11.5.35 June 20, 2024

Bug Fixes

BUGFIX: Workflow search action search conditions cannot access earlier context
- If you set up a search action in a workflow, and the search conditions use something output earlier in the workflow, then when the search runs, it will be as if that thing from earlier in the workflow was null.
- Effectively, the whole context of earlier workflow output was not available at runtime to the search conditions.
- This bug was introduced in version 11.5.30
- Issue: 4018
BUGFIX: Workflow search produces biskits referencing shallow biskits
- The problem is that if you search for something (eg bookings with a project), and then list extract the projects, you will find the projects are all shallow.
- If you try to get properties, they will all appear null.
- Issue: 4020

1.37 11.5.36 September 10, 2024

Changes

Add more debug logging to debug attachment downloading in Enterprise
- Issue: 4016
Change Enterprise tools wording when user account exists mismatches
- Issue: 4027
Prevent updates to exported biskits that make them not exportable
- Issue: 4067
Enterprise - Show shard number in permissions & rule pages for imported items
- Issue: 4070
Prevent custom repeat booking/template from being created or updated
- Custom repeat types were introduced to solve a problem while upgrading from 10.1 to 11.0.
- In 10.1, the repeat information on a booking was embedded within the booking, whereas in 11.0, it is now separated out into its own table.
- In 10.1, any set of repeat bookings that have completely finished their repeating sequence so they are all in the past, will have lost the information about what type of repeat it was.
- Whereas in 11.0, repeats in the past retain a reference to their repeat information.
- Those repeats in 10.1 that have finished their repeating sequence could not be represented as a proper repeating sequence because of the information having been lost due to the way repeats were handled in 10.1 and earlier.
- So a “custom repeat type” alongside daily repeats and weekly repeats etc. This allowed historical repeats to be tied together in a repeating sequence.
- The intention was to allow custom repeats to be created so that you can choose ad hoc dates that form part of a repeating sequence. However, this has not yet been done, and custom repeats don’t quite work properly as they are.
- So for now, creating or changing bookings or templates with a custom repeat type is disabled until they can be fully implemented.
- Issue: 4098
Check whether allow Enterprise unimport on receipt of request
- When you ask for something to be unshared from one or more shards, those remote shards check whether the biskit being unshared is referenced or not. If it is referenced, then it does not do the unimport.
- However, the check for whether it is referenced is done only when the unimport is attempted. But if there is something already queued, the the unimport request will also be queued, and so the check for any references will not be done until later, when somebody clears the queue.
- This means the person doing the unshare will think it has gone ahead okay, and can be oblivious to a problem that may exist on the importing side.
- Issue: 4104

Security Fixes

SECURITY FIX: Set Cache-Control no-store header on all HTTP POST responses
- This is part of security improvements so that it becomes harder for anybody to misuse data sent to a Calpendo client by making sure that the browser can’t blindly store and reuse responses from the server.
- Issue: 4049
SECURITY FIX: Mark file upload JSESSIONID cookie as SameSite=strict and HttpOnly
- When you upload a file to Calpendo, then it sets a JSESSIONID cookie.
- Once a cookie is present, then another one is not set for each upload, but the same one reused.
- However, the cookie was not marked as HttpOnly and not marked as SameSite=strict, both of which are recommended.
- Issue: 4050
SECURITY FIX: Remove sessionID from network requests URL when uploading file
- When you upload a file, this involves multiple network requests to servlet.gupId, all of which would include a parameter containing the session ID in the URL.
- This is contrary to best practice because putting a session ID in an HTTP request URL means the session ID would be recorded by server logs and be generally more visible than it should be.
- Issue: 4051
SECURITY FIX: Hide bakery page when not on the menu and user has no write perms
- If the bakery is not on your menu, then you were still able to see the bakery by changing the URL to #bakery.
- If you were not an admin, then this would only serve as a read-only page with no ability to modify anything.
- Even so, it would be better that if the page is not on your menu, and you don’t have permission to modify anything in the page, then you should not be able to view it.
- Note that this should not be hidden from anybody who does have permission to change things in the bakery because the bakery can sometimes be the only way to recover when booting Calpendo runs into a problem due to bad biskit definitions. In this case, it boots into rescue mode when you would be told to use the bakery to fix issues.
- Issue: 4052
SECURITY FIX: Mark the session cookie as SameSite=strict
- The cookie that stores the user’s session ID was not marked with a SameSite directive.
- This has now been changed to “strict” mode, which is one part of protection against cross site request forgery (CSRF/XSRF).
- Issue: 4053

Bug Fixes

BUGFIX: API query fails to find a match when a search condition string value includes a space
- If an API query is submitted to find a biskit that matches a specified string value for one of its properties, then no match is found if the string specified contains a space.
- For example, an API query to search for a bookable Resource whose name contains a space will not find a match even if you get the name right in the condition.
- Issue: 3921
BUGFIX: Before transaction workflow event overwrites old value of a property
- Suppose you set up a workflow so that a database event runs before-transaction when a booking is updated, and it changes the description on the booking.
- Suppose further that there’s another database event, but this one is triggered during-transaction. In this event, set up a templated text to show the old value of the booking start time and the new value.
- Then if you edit a booking and change its start time, the second workflow should see the old and new value of the start time as being different. But instead, it shows them as the same, and equal to the new value.
- Issue: 3964
BUGFIX: Conditions in a URL that take a DateRange value only accept a prefix of ‘R’ but should also accept ‘r’
- The documentation here: https://docs.exprodo.com/railroad/conditions-url-11.0.4.html describes how you can use a link directly to a search page, and put conditions in the URL that will choose what the search will find.
- For example:
```
  https://demo.calpendo.com/#search&searchType=Calpendo.Booking&action=view&condition=dateRange.start/includes_time_between/R20240528.120000-20240528.230000/to-the/hour
```
- This query is perfectly valid, and works. The documentation indicates that when putting a DateRange value in the URL, it must be prefixed with ‘R’ or ‘r’.
- In the above example, it appears as: R20240528.120000-20240528.230000
- However, while ‘r’ should be accepted, it isn’t. Only ‘R’ works. If you use ‘r’, then it causes an exception.
- Issue: 3974
BUGFIX: Annual Repeat Bookings are assigned incorrect dates beyond the second instance
- Suppose you create an annual repeat booking that repeats on July 20 every year.
- If you then run a report to show the instances of that booking for the next 10 years, you would see the first two on July 20, but subsequent years show as being on February 1.
- Issue: 3975
BUGFIX: Search for references to property sometimes gives exception with illegal report
- Suppose:
  - You have some property “x” on a biskit
  - There is a report with a condition that references “x”
  - The table that stores the condition has its owner_id column set to null (which it should never do).
- Then when you click on the property “x” in the bakery and search for references to it, you get an exception.
- Issue: 3984
BUGFIX: Specifying an invalid API resource looks like server down
- If you run an API request and specify a URL whose path indicates something that does not exist, then the result is an exception that makes it look like the server is down, rather than giving a clean 404 error response.
- Issue: 3986
BUGFIX: Errors sent from API give illegal content type
- If the API returns an error, then it does so with an illegal content type of “application/text” instead of “text/plain”.
- “application/text” is not a standard content type, as defined by Iana.
- Issue: 3987
BUGFIX: Using API in browser shows raw HTML instead of interpreting it as HTML
- When you access the API from a web browser, then the result will always be in HTML.
- Using the API from a script, you can specify that you want the response in XML or JSON.
- However, in the browser, the response should be interpreted as HTML, but instead showed the raw HTML code because the response did not indicate that the response contained HTML, so browsers treated it as plain text.
- Issue: 3988
BUGFIX: Downloading Enterprise foreign attachments fails if not already logged in
- Suppose:
  - You view a biskit that belongs to another shard
  - You have not logged in to that other shard
  - The foreign biskit you’re viewing has an attachment property
  - You click on the attachment
- Then the download fails and returns an error.
- Or more precisely, it sometimes fails since there are some circumstances in which it works.
- Issue: 4011
BUGFIX: Cancelling last non-ephemeral repeat instance (‘This Item’) cancels all subsequent instances as well
- When Calpendo stores a repeat booking, it will expand the repeating sequence up to 90 days (by default) and store those in the database.
- The last of those that are stored in the database also serves as a template for future repeats, and so can be thought of as a “promise to repeat”.
- When you cancel just one one instance of the repeats which is the last booking that was expanded in the database, then what should happen is that the next repeating instance should be stored in the database, and it would serve as the new template for future bookings, or the “promise to expand”.
- However, that newly added instance was incorrectly marked as cancelled, and so the whole repeating sequence after that point was displayed with a status of cancelled.
- Issue: 4029
BUGFIX: No warning popup when booking inside a warning template
- When a template is configured to give a warning when a booking is made at the same times as the template, the warning is not displayed to the user.
- Issue: 4030
BUGFIX: Setting booking rule to “suggest retry as tentative/requested” doesn’t result in expected suggestion popup
- When a booking rule triggers, it will normally generate an error.
- However, whoever writes the box can tick options to have Calpendo offer the user the option to retry the booking as a requested or tentative booking.
- If such a rule is triggered, then Calpendo was not showing the user the option of retrying as it should.
- Issue: 4033
BUGFIX: Bookings rejected by a workflow rule did not generate exception
- Issue: 4042
BUGFIX: Repeat expansion rejected by a booking rule prevented any expansion
- Bookings that repeat have a certain number of booking instances expanded and stored in the database. This is set to 90 days by default.
- Suppose a booking rule prevents a booking being created on some day in the future.
- This might be a holiday rule or anything else that rejects a future booking.
- Then when you create a booking, if the day which would be rejected by the rule is WITHIN the 90 day period, the booking would be outright rejected as breaking the rule.
- This is not ideal, but is how the system has always behaved, and we are accepting this for now.
- Suppose then that the day which would be rejected by the rule is OUTSIDE the 90 day period.
- Then it’s the job of the “Repeatable Handler” to check every day to see if there are repeat bookings that need to have another day’s booking expanded and stored in the database.
- If that happened, and the booking it tried to create was rejected by a rule, then this would generate an exception and no changes would be written out.
- This isn’t right because this booking would never be able to exist beyond this one day that the rule disallows.
- The behaviour now is that on the day in question, the booking will be created, but it will have a status of DENIED.
- A further issue with this behaviour exists on upgrading from 10.1 to 11.0. In this case, the upgrade procedure which runs at boot time does not expand the repeat instances. Instead, this expansion happens after the Calpendo boot has completed. However, any booking for which any of its repeat instances (within the 90 day period) are rejected by a rule will result in that booking not being expanded at all - not even before the day that is rejected.
- The expected behaviour here is that those bookings that are rejected are assigned a status of DENIED, and all others would be expanded as normal.
- Issue: 4043
BUGFIX: Repeat expansion could set a whole sequence to denied when it should not
- When you have a repeat booking, the last booking stored in the database when expanding the repeats for the booking is used as a “template” for future expansions.
- So suppose there is a repeat expansion done and there’s a rule that prevents a booking from being made.
- So that booking will now be assigned a status of DENIED.
- However, if the last instance of a repeat booking stored in the database is DENIED, then that means it would be the one used as a template for future repeats, and so the whole sequence of ephemeral bookings would be DENIED, and so every time the booking is expanded another day in the future, it would also be DENIED (since it copies the template booking).
- So the behaviour now has changed. When the last instance of an expansion is denied, then Calpendo will now expand another day to see if the next booking will be accepted.
- If that is also denied, then Calpendo will continue on for a maximum of 20 further repeat instances to see if any of those will work.
- As soon as one is not denied, it will stop. If all are denied, then all 20 are stored with a status of DENIED, and it’s left like that.
- Issue: 4044
BUGFIX: Errors sent from API set the HTTP return status code to 200, which suggests no error
- If you make a query to the API to search for biskits of a type that does not exist, then you did get back an error message, but the return code was 200, which means all was well. This now returns 404, to indicate the item was not found.
- Similarly, if you make a query API request with conditions in the URL that reference properties that don’t exist, then you now get a 400 (bad request) response, where it used to be 200 (OK).
- Also, if you make a query API request and ask for the result to include properties that do not exist, then you now get a 400 (bad request) response, where it used to be 200 (OK).
- Finally, if you use the Biskit API to ask for a biskit of a specific type or specific ID where either the type is not known or the ID is for a biskit that does not exist, then you now get a 404 (Not found) return code where you used to get 200 (OK).
- Examples of the URLs that are affected are:
  - /api/q/Calpendo.Resource/name/EQ/blah?paths=fakePropertyName
  - /api/q/Calpendo.Resource/fakePropertyName/EQ/blah?paths=name
  - /api/q/fakeTypeName/name/EQ/blah?paths=id
  - /api/b/Calpendo.Resource/12345/ (where no resource with ID 12345 exists)
  - /api/b/fakeTypeName/
- Issue: 4046
BUGFIX: RepeatableHandler “update” system event is badly formatted, confusing and misleading
- When RepeatableHandler kicks in (once per day), it looks to see if there are any repeating bookings or templates that should be expanded in the database.
- When it does this, it generates a system event with the category set to “Update” to say what it did.
- There were 4 separate problems with the information in the “Update” system event it creates:
  1. If it finds any repeatables that have a start and finish date surrounding the period where it is wanting to expand bookings, but there no instances due to fall within that period, then the HTML table it generates is broken so that a table that should have 6 columns, and indeed has 6 columns in the header row, ends up with 10 columns. The extra 4 columns have no header row, and the thing is not readable.
  2. Any booking or template IDs shown in the message are displayed in their unformatted numerical form, rather than formatted in the way that is done everywhere else in the UI.
  3. When something fails to expand, such as because a booking breaks a rule, then the system event detail suggests the new instance of the booking was saved without any additional information. Nothing in the system event indicates that there was a problem.
  4. Without the resource names being shown, it makes it a little harder to understand the information displayed.
- Issue: 4054
BUGFIX: Permission editor gives false-positive errors about unknown properties
- Issue number 3981 and change number 591 in 11.0.5 added support for showing an error in a report or permission when a non-existant property is referenced.
- For reports, this works okay. However, when a permission references a property in a condition, it would usually show an error when it should not.
- Suppose a permission applied to Booking, and it had a condition that referenced the booking’s status property.
- Then the UI should have verified that Booking.status existed, and show an error if there is no Booking.status.
- Whereas it actually checked whether Permission.status existed instead. So it produced a lot of false-positive errors.
- Issue: 4055
BUGFIX: Database stored functions ‘formatpk’ and ‘parsepk’ get timezone wrong
- Sometimes, it is useful to work directly in a database command line.
- This typically happens when investigating some issues.
- Since the UI exclusively displays ID numbers as a formatted string, then it is convenient to have stored functions in the database that format an ID number as a string (“formatpk”) and parse a formatted ID number into an ID (“parsepk”).
- These stored functions are not needed for Calpendo to operate, but help provide support.
- We have had these functions for a long time now. But some systems have incorrect versions of these stored functions. A part of the ID number encodes the date and time when it was created in UTC. When this is formatted or parsed, then the stored functions should also use UTC.
- However, some databases have older versions of these stored functions that do not correctly include timezone calculations.
- In particular, new databases recently created have been using the older version of these functions.
- Issue: 4056
BUGFIX: Change finish time on last instance of a repeat gives exception
- Suppose you create a repeat booking and give it a finish date, so that it does not repeat forever.
- Then if you edit the last instance of the repeat and change the finish time, then you get an exception that says:
```
"IndexOutOfBoundsException: Index -1 out of bounds for length 0"
```
- Issue: 4060
BUGFIX: Edit ephemeral afternoon daily repeat booking this-item and non-ephemeral booking not created next day
- If you create a daily repeating booking that starts after noon, and then edit the description of any one of the repeat instances after the period of expansion in the database (90 days from today by default), then it does not store a new instance of the repeating booking a day later, which it should.
- Issue: 4061
BUGFIX: Ephemeral bookings sometimes do not display in the calendar
- Repeat bookings are expanded in the database up to a particular point, and thereafter any further repeating instances are generated on-the-fly and displayed in the calendar despite no being stored in the database.
- However, under some circumstances, the one-the-fly expansion can miss out some instances that then don’t appear on the calendar.
- Issue: 4062
BUGFIX: Existence of before-transaction db event causes aborted cancellation to be persisted
- When there is a database event in the workflow manager, and the database event is configured to run before-transaction, then any attempt to modify a booking (eg cancel it) will be succeed, even if a booking rule prevents it.
- In this case, changes to the booking will be saved, but an exception is also raised and this will return an error to the user for the rule failure.
- Issue: 4063
BUGFIX: Location applicability is ignored on rules
- In an Enterprise Calpendo, Booking rules were always functioning, when enabled, regardless of how its Location Applicability was set.
- This is something that should control whether it operates remotely (when imported) or locally (on the shard that owns the rule) or both.
- Issue: 4064
BUGFIX: Edit description of last ephemeral THIS-ITEM and previous ephemeral is not created
- Suppose:
  - You have a daily repeat booking with a finish date set
  - You edit the last repeating instance, for example to change its description
  - You select THIS-ITEM when asked which repeating instances should be affected by the change
- Then it will correctly store a booking in the database to represent this instance.
- However, it should also create bookings in the database for all previous ephemeral bookings, and it did not do this.
- Issue: 4066
BUGFIX: Exception on change repeat so previously cancelled bookings now needed
- Suppose you have a repeat booking, and you then modify the repeat in such a way that some repeat instances are no longer needed, and so are cancelled.
- Then modify the repeat again so that some or all of those cancelled instances are required again. That is, they must be “uncancelled”.
- This situation was not handled correctly, and it tried to save the uncancelled bookings with a null status, which is not allowed.
- Issue: 4071
BUGFIX: Enterprise cannot unshare a project
- Issue: 4074
BUGFIX: Approve repeat booking also approves cancelled and denied instances
- Suppose you:
  - Create a daily repeat booking, repeating every day, such that its status is requested everywhere
  - Change it to repeating every 2 days
  - This means every other booking will have its status changed to cancelled
  - Approve one of the requested bookings
- Then all the repeat instances are approved.
- This means that the instances that are not wanted (because it’s repeating every 2 days) are also approved, and so they look like that are wanted, even though the repeat still says every 2 days.
- Issue: 4075
BUGFIX: You can approve a repeat booking instance that is cancelled because the repeat says it should not exist
- Suppose you:
  - Create a daily repeat booking, repeating every day
  - Change the booking to repeat every 2 days
  - Every other booking now has its status changed to cancelled
  - Edit one of the cancelled bookings and change its status to approved
- Then this allows you to mark the cancelled booking as not cancelled, so that you are allowed to approve a booking that the repeat says should not exist.
- If the repeat says there should be no booking on a particular day, then you should not be able to uncancel that repeat instance.
- Issue: 4076
BUGFIX: Uncancelling repeat booking ALL ITEMS only uncancels one instance
- Issue: 4077
BUGFIX: Creating a new booking allowed you to select “custom” repeat type
- Custom repeat types are partially implemented. This is a type where you have multiple bookings that are considered part of the same repeat sequence, but without a defined pattern to the dates that the repeats occur on.
- During an upgrade from 10.1 to 11.0, any repeat bookings where the whole sequence is in the past will have lost the information about what sort of repeat it was.
- Consequently, during the upgrade they are converted to a repeating sequence with “Custom” repeat type.
- This is currently the only way to create such repeats as they are not fully implemented.
- So when creating a new booking or template, the repeat types drop-down lists “Custom”, but it is greyed out and cannot be selected.
- Issue: 4078
BUGFIX: Custom repeat type is selectable when editing existing booking
- A custom repeat type should ONLY be selectable when:
  1. The booking already exists in the database (not a new one being created)
  2. The booking is already repeating with type Custom
- However, pre-existing bookings which were either not repeating, or were repeating with a type that was not custom could be edited to make them custom repeats. This is not supported.
- Issue: 4080
BUGFIX: Choose reason for cancellation and it did not notice (if on subtab)
- When a resource indicates its bookings need a reason when they are cancelled, and you edit a booking and select a reason, then the yellow warning saying you need to supply a reason is still visible if you put the status property onto a subtab in the booking layout.
- Issue: 4082
BUGFIX: Change repeat booking description ALL ITEMS gives shallow exception with status on subtab
- Issue: 4083
BUGFIX: Change repeat booking description ALL ITEMS gives shallow exception with formulaic property
- Issue: 4084
BUGFIX: Edit a repeat booking instance and “Cancelled” does not appear in the status drop-down
- In version 10.1, there was only ever one non-ephemeral instance of a repeat booking. This meant that cancelling that booking wasn’t a sensible thing to do. You could delete the whole thing, and that’s all.
- As a part of this, the drop-down that lets you choose the new status when editing a booking did not include “Cancelled” when the booking was a repeat.
- While that was sensible in 10.1, it isn’t in 11.0 as cancelling a single instance of a repeating sequence is now supported.
- However, while the “Cancel Booking” button works, you could not do the same thing by selecting “Cancelled” from the status drop-down.
- “Cancelled” now appears in the status drop down for repeat bookings, as well as non-repeat bookings.
- Issue: 4085
BUGFIX: User can change the resource of any booking from a repeat sequence
- A repeat sequence should all be for the same resource.
- It doesn’t make sense to allow them to be across different resources.
- This restriction is now enforced.
- Issue: 4086
BUGFIX: Error displayed after editing a non-ephemeral booking in the future and select ‘This and Later’ option
- Issue: 4087
BUGFIX: Created booking appears to be ephemeral via ‘Copy to Clipboard’
- Copy and paste a non-repeat booking in the calendar, and it appears to be an ephemeral booking, until you refresh the calendar contents.
- Issue: 4088
BUGFIX: Cut/paste some workflow actions gives EntityNotFoundException on save
- If you have a workflow that contains a CreateVariables action, and you cut/paste that action to a different place in the workflow, then saving the workflow fails with an exception.
- Issue: 4090
BUGFIX: Cannot save User BiskitDef with property that references a User
- Issue: 4093
BUGFIX: Enterprise user session loaned to other shard not marked as borrowed
- In an Enterprise system, a user only need log in to one Calpendo shard.
- Then, if they access another shard, the session for the previous shard can be used so they don’t need to log in again.
- A part of the way this works is that the database tracks which sessions have been “borrowed” in this way by other shards.
- Suppose:
  1. You have a shard A with a project that has been shared to shard B
  2. The project has a file attachment
  3. A user is logged in to shard B, but not shard A
- Attachments are never shared. So this attachment belongs to shard A and will only ever be stored in shard A’s database.
- Then the user is on shard B, and clicks on the attachment, their session on B will be loaned to shard A. The session on shard B should record that it has been borrowed, but it does not do so.
- Issue: 4095
BUGFIX: Unsharing Enterprise project with referenced fragment gives bad error
- If you have a biskit that references a fragment of an imported biskit, and then try to unshare that biskit, the result is a horrible error message.
- This commit checks for references to the fragments so that we can provide a better message. Previously we only check for references to the main biskit.
- Issue: 4096
BUGFIX: Data loss if edit a biskit referencing a non-enumerable biskit value
- Suppose you have a biskit (“parent”) which stores a property that holds another biskit (“child”), where the child is a non-enumerable biskit.
- It can be almost any non-enumerable biskit, although NOT a Booking since it is always rendered specially.
- Then when you edit the parent biskit, the editor loses the value for the child so that when you save it, the parent’s reference to the child is null.
- Issue: 4097
BUGFIX: Allow Zombie Enterprise imports to be denied
- When an import fails for some reason, its status is changed from QUEUED to ZOMBIE.
- The ZOMBIE then prevents things on the import queue from being imported.
- It was not possible to ignore a ZOMBIE if you want to, and the only option was to delete it, which meant losing information.
- So we now allow the status of ZOMBIE imports to have their status changed to DENIED so that they will then be ignored.
- Issue: 4100
BUGFIX: Allow user to log in if menu references non-existent user workflow event
- It should not be possible to get into a state whereby a menu references a workflow event that does not exist, however this is possible using an Enterprise system.
- If you get into such a state, and your menu has such a bad reference, then you were not able to log in.
- Issue: 4101

1.38 11.5.37 September 24, 2024

Changes

Display Enterprise warning if edit a foreign Biskit in the bakery
- With suitable permissions in an Enterprise system, you can edit a BiskitDef and other items in the bakery (MappedInt, MappedString etc) when that BiskitDef (or other type) belongs to another shard.
- However, the changes won’t be visible in this shard until the home shard for the BiskitDef publishes those changes.
- This can be confusing, and so there’s now a warning to that effect when you start editing.
- Issue: 4106
Show references in Enterprise to biskits that are in other shards
- When showing references to a biskit, it did only shows things in the current shard.
- It now shows references that exist in other shards as well.
- Issue: 4112
Prevent Enterprise updates to a workflow that remove stuff if you don’t have an account on all importing shards
- Suppose:
  - you edit a workflow that has been exported to at least one other shard to which you have no login rights
  - your change to the workflow involves removing a user workflow event, or a DefineConstants, DefineInterface or DefineSubroutine action
- then since you can’t log in to all the shards to which the workflow has been exported, you cannot check whether the workflow is referenced on those shards.
- Consequently, you will now be refused the ability to update a workflow in such a way that removes any of the above events/actions, or that deletes a workflow if you cannot log in to any shard to which the workflow has been shared.
- Issue: 4114

Bug Fixes

BUGFIX: Allow user to log in if menu references non-existent user workflow event
- It should not be possible to get into a state whereby a menu references a workflow event that does not exist, however this is possible using an Enterprise system.
- If you get into such a state, and your menu has such a bad reference, then you were not able to log in.
- Issue: 4101
BUGFIX: Reports with holes in the list of columns cannot be run and break show-references
- A report’s columns are stored as a list. That means each column stores a reference to its report, and also an integer index that is its position within the list of all columns on that report.
- Indexes should start at zero, and increase by 1 each time, leaving no gaps.
- If the indexes miss out any numbers, then that ends up being represented by a null value in the list of columns.
- Some parts of Calpendo are able to cope with this.
- However, there are three occasions when these erroneous columns cause issues:
  1. Go to Search->Search and load a bad report
  2. Go to the reports manager, click a bad report, and then click on “Open Report” or “Run Report”
  3. In the bakery, if you ask it to show references to a property, then it can also look for references from reports which can generate the same error.
- These are now handled properly.
- Issue: 4105
BUGFIX: Non-Enterprise search workflow action upgraded from 11.0 gives exception
- Issue: 4107
BUGFIX: Account status page sometimes shows a message with missing spaces
- When there’s a problem with an account being active on different shards from what another shard thinks, then you can see an error message like this:
  
  Account is active on more shards than shard 34 thinks. Active on shards 1, 331 and 409 while shard 34 thinks the account is active onshard 1
- The problem is the “onshard” at the end, which should say “on shard”.
- Issue: 4108
BUGFIX: BiskitDef does not have versioning set up
- Some BiskitDefs are configured to specify a property that stores a version number.
- The BiskitDef for BiskitDef itself does have an integer property for this purpose, called “version”.
- However, it was not set up as the property to store the version number for a BiskitDef.
- This means that there was no protection against somebody editing an out-of-date BiskitDef.
- Issue: 4109
BUGFIX: References to a Workflow do not show menus and other workflows
- When you look for references to a workflow, there are two classes of reference that were never found:
  1. When you have a menu that references a UserWorkflowEvent defined by the workflow, nothing looks for references to that event, so the menu is not found.
  2. A workflow is referenced by every event and action within it. To avoid noise, references from workflows to a workflow were ignored. But this did not take into account when an action has a reference to something in another workflow. For example:
    - where a CallSubroutine action calls a subroutine defined in another workflow
    - where a CallSubroutine action calls a subroutine whose interface is defined in another workflow
    - where a DefineSubroutine action declares that it implements an interface defined in another workflow
    - where a GetConstants action fetches constants defined in another workflow
- Issue: 4111
BUGFIX: Updating a workflow to remove parts of it that are referenced is not handled well
- There has always been a check to make sure you can’t delete a workflow while something references it directly.
- However, there can be references directly to some of the events or actions within a workflow, and we never did check for those references.
- This means that when you delete a workflow that has references to the things within the workflow, but not directly to the workflow, then you would get a nasty error message. That error came from the database which could see that you were deleting something that is referenced.
- This error is now detected and handled gracefully with a good error message.
- In an Enterprise system, this is really important. That’s because it’s possible to update a workflow that has been shared to another shard, and in so doing remove events or actions inside it that are referenced on a shard that imports the workflow. That would introduce problems if the importer has a referential problem while the exporting shard does not.
- Issue: 4113

1.39 11.5.38 October 17, 2024

Changes

Provide message on login if using Enterprise and there is an import queue needing attention
- If you are using an Enterprise system, and there is at least one item on the import queue, and you are a user who has permission to import things, then on login you now see a message telling you there are items on the import queue.
- Also, when there are bakery things on the import queue, it tells you so.
- Issue: 4131
Allow support for linked bookings to be added to Calpendo starter licences
- Calpendo Starter does not support linked bookings.
- However, we now have the ability to add support to Calpendo Starter for this by a licence change.
- Issue: 4136
Add extra verbose logging to show incoming server requests
- When there’s a storm of messages going between shards in an apparent infinite loop, it can be difficult in production to determine what those messages are and so diagnose the problem.
- If you enable verbose mode for APIExecutor, it will now write additional information to the tomcat log file to indicate what messages it is receiving.
- Issue: 4149
Include audit log comment in reason in import request we send out
- When an exported biskit is modified, then we tell importers about the change.
- The import request we send them includes a space for us to tell them the reason why we’re asking for them to do the import.
- This reason now includes the comment that was stored on the audit log entry for the original save of the exported biskit.
- Also, when we receive a new fragment from a shard that imports a biskit, then we now store a suitable comment in the audit log to say why we’re saving it, and this then appears on any import requests that sends out to other shards.
- Issue: 4150
Add number of top-level imports to each FederationImportBatch
- Every time there is an export from one shard to another, the importing side records a FederationImportBatch. This is what the federation import queue page looks for.
- Each batch contains one or more top-level biskits that it wants to import. Each of those can include other biskits, so there may be more than just the top-level biskits being imported.
- We now want a property on the batch to say how many top-level biskits are being imported.
- This is helpful when looking at a large import queue to give a better understanding of what is there.
- This has been done by adding an integer property FederationImportBatch.numberOfRootImports
- Issue: 4153
Add property to FederationImportBatch to say whether it’s an import or unimport
- Every time there is an export from one shard to another, the importing side records a FederationImportBatch. This is what the federation import queue page looks for.
- Each batch contains one or more child items for the import or unimport of a biskit.
- Each of those children specify whether they are an import or an unimport.
- However, we do not allow a single batch to mix imports and unimports.
- So we now have a property “importAction” on the batch items to indicate whether it contains imports or unimports.
- Issue: 4154

Optimisations

Optimisation: Many Enterprise user imports can result in many permission cache rebuilds
- When there is an import of a user, then just like any change to a user, it triggers a change to rebuild the permission cache.
- But when there are many users being imported, then this could result in a very large number of permission cache rebuilds.
- This has now been simplified to reduce the system load.
- Issue: 4152

Bug Fixes

BUGFIX: 11.0 upgrade does not warn about conditions that reference lastRepeat
- The lastRepeat property has been removed from Booking and Template in 11.0.
- Some conditions are automatically modified when the reference the lastRepeat property, but not all.
- There was already an upgrade script to make sure there was a warning generated during the upgrade for any remaining condition that referenced lastRepeat, but it never ran because it was misconfigured.
- Issue: 4120
BUGFIX: Report with lastRepeat columns fails after upgrade from 11.0
- In 10.1, there are properties Booking.lastRepeat and Template.lastRepeat that do not exist in 11.0.
- If you have a report which has a column referencing one of those properties, and it is not the last column in the report, then upgrading from 10.1 to 11.0 produces a report that gives errors when you open it.
- Specifically, locate the report in the report manager page, and then click on either “Open Report” or “Run Report”, and it gives an exception.
- Issue: 4121
BUGFIX: Enterprise scheduled report is blank if getting data from multiple shards (even if all the data is held on the home shard)
- Issue: 4122
BUGFIX: Cannot initialise system identity when upgrading an already-expired licence system from 10.1 to 11.0
- When a Calpendo’s licence has expired, and gone beyond its grace period, trying to use it will instead display a “Licence Reset” page.
- When a Calpendo has just been upgraded from version 10.1 to 11.0, then the “Licence Reset” page will show as well. This is because it will need to be assigned a “system identity”. This is used with the new licence server so that each system can have their licences automatically updated each year, rather than requiring a manual change to input the new licence.
- However, if an already-expired system is upgraded, then you could not use the licence reset page to assign a system identity. Without a licence and without a system identity, recovery from this would be messy.
- So now, the system reset page will allow you to set the system identity when the licence has expired. This allows for upgrades from 10.1 (which have no system identity) to work properly.
- Issue: 4124,4125
BUGFIX: CustomTreePage error when multiple items start with the same string
- Suppose:
  1. a CustomTreePage shows biskits, and groups them by some string property.
  2. Some biskits have a value for that property that starts with a value that matches exactly the full value for another item. Eg some biskits have “HELLO” as the string to group by, while others have “HELL”.
- Then when you click on any of the biskits below the longer name, you get a message pop-up for a few seconds in blue that says:
```
"Could not parse requested node identity (ignored)"
```
- Issue: 4127
BUGFIX: Click on any biskit and the “Delete” button is always greyed out
- This was a problem with the changes to the way references to biskits were calculated, which left all biskits as being considered undeletable even when they were unreferenced and deletable.
- Issue: 4128
BUGFIX: Linked booking sometimes fails when one child breaks rules, others ok
- Suppose you have linked bookings set up so that the creation of a booking for a parent resource will create a booking for exactly one child booking, but from a selection of more than one resource.
- Then if you make a parent booking and the first child it tries to create fails because it breaks a rule, it means that it doesn’t even try to make a booking for another child, so the parent gets refused.
- Issue: 4129
BUGFIX: Enterprise service orders should live only in the shard that owns the service
- Service orders should only ever exist on the shard that owns the service.
- This is exactly like the way bookings only exist in the shard that owns the resource.
- Issue: 4130
BUGFIX: Searching for references ignored anything referenced in conditions
- If a permission has a condition that references a particular ResourceGroup, such as:
  
  self member of fixed MyResourceGroup
- Then when you go to the MyResourceGroup and look for references to it, it would not show the permission as referencing it.
- This was true of all flavours of conditions.
- Issue: 4132
BUGFIX: Boolean properties don’t work when displayed as a check box
- If you configure a layout to display a boolean property with a checkbox (rather than radio buttons or a list box), then it does not display the correct value and does not let you change the value.
- Issue: 4133
BUGFIX: Login page fails to display with msg “Could not initialize proxy - no Session”
- With the right permissions in place, wait long enough and the Calpendo login page will fail to display and instead show an error message.
- Issue: 4134
BUGFIX: Edit the schedule for a report and the start time-of-day is ignored
- Create or edit a report in the report manager, and the time-of-day on the schedule’s “When” tab always reverts to midnight, regardless of what time you choose.
- Issue: 4138
BUGFIX: Enterprise import can fail when two users imported with same project
- Suppose two users are imported at the same time, when both users are a member of the same project, and that project has not yet been imported.
- Then in this case, the import would fail with an error like this:
  
  FetchNotFoundException during FederationImportApprovalRequest: Entity Calpendo.Project with identifier value 633366068069377 does not exist
- Issue: 4139
BUGFIX: Record a reason why each Enterprise import batch was created
- Each federation import request stored in the database already had a field to store a comment.
- This was usually empty, although did contain something in some circumstances.
- This should now always be populated with a reason for why the import was done.
- Issue: 4140
BUGFIX: Enterprise exceptions from foreign shards don’t log foreign details
- If a request is sent from shard A to shard B, and it generates an exception, then shard A will log a system event.
- However, the stack trace generated on shard B does not get saved in the system event, which means it is harder to debug what actually went wrong.
- Also, the Tomcat log file generated would log the stack trace from shard A but not include details from shard B.
- Issue: 4141
BUGFIX: Persistence exception on import does not update import status
- When there’s a failure to perform an import, this would most normally generate a HibernateException. If there was one, then we would mark the batch as having a status of ZOMBIE.
- However, there are some things that can go wrong that are thrown as a PersistenceException, which we did not catch.
- This meant that these errors would not result in the import status being changed to ZOMBIE as it should.
- Issue: 4142
BUGFIX: Guaranteed delivery of messages between Enterprise shards was not working
- Some messages between shards must be delivered, and failing to deliver them would generate problems.
- Any messages that require guaranteed delivery will be saved to the database if they fail, so that they can be resent later.
- However, this process was not working correctly.
- Issue: 4143
BUGFIX: Infinite loop if Enterprise requests implies communications failure
- Suppose a particular request is consistently handled badly, such that it results in what appears to be a communications failure to another shard, while other messages are able to get through to the shard without a problem.
- Then in this case, our general practice of resending failed messages would result in an infinite loop.
- This behaviour is now modified such that if we see a particular request failing many times, and other messages are able to get through to the shard over the same time period, then we will assume the request is somehow bad, and should be dropped.
- This means the notion of “guaranteed delivery” is weakened for those cases where it appears impossible to deliver a particular request.
- Issue: 4144
BUGFIX: Federation Import Queue page cannot handle large number of queued items
- If a problem results in a repeated export from one shard to another, and those items are all queued, then the federation import queue can be large.
- We’ve seen a queue with 100,000 items in production.
- When this happens, the federation import queue page would not be able to display as it doesn’t handle a large number of items well.
- Consequently, it’s now been changed to show a group report by default instead of a list report.
- At the same time, the report now shows the shard number so that when you configure the page to get queued items from multiple shards, you can see which shard has what items queued.
- Issue: 4145
BUGFIX: Two “booted” messages were sent to other shards on each boot
- When a shard boots, it sends a message to all other shards to let them know that it has booted.
- However, it was doing this twice where it only needed to be once.
- Issue: 4146
BUGFIX: Import requests sent to ourselves on reconnecting to a shard
- When we reconnect to a shard after some kind of disconnect, we capture a list of the outstanding import requests we had to send to that shard, and then we send that to ourselves instead of the the foreign shard.
- Issue: 4147
BUGFIX: Importing a biskit that might be a child generates duplicate requests
- When a biskit is imported, and that biskit is the parent of some others via either a one-to-many or a to-many relationship, then we do not necessarily force the children to be imported along with the parent.
- Consequently, when we later import a biskit that might be the child of a one-to-many or a to-many relationship, then we need to check whether it actually is in such a relationship.
- This means sending a request to exporting shards to ask whether our view of the relationships is complete. If not, the exporting shards will resend a copy of the parent biskits so that we can ensure the relationships are kept up-to-date.
- However, when this happened, we would send a separate request for to-many relationships and one-to-many relationships. This was a duplication of effort, and there should have been a single request that encompassed all the data within the two.
- This is only a problem when a biskit can be the child of both a to-many and a one-to-many relationship, and such a biskit is newly imported.
- Projects fall into this category because User.projectsOwned is a one-to-many property of projects and rules contain multiple properties that contain a to-many set of projects.
- Issue: 4148
BUGFIX: Users & Projects changed by export written to database twice
- Suppose you have a user or project that has been exported, and then somebody makes a change to it.
- Then Calpendo will see that it has changed, and that it should be re-exported to all previous importers. So it sends an import request to all the importers.
- The importers send a reply that includes a copy of the fragments so that we can update our copy if their fragments have changed.
- The exporter checks the response to see whether the fragment has changed, and if so, then it writes the new value of the fragmented biskit to the database.
- However, the write to the database happened twice rather than just once.
- Issue: 4151
BUGFIX: Example services not compatible with Enterprise
- There are modules containing example services that can be enabled as desired.
- However, they are not compatible with Enterprise in the form they exist.
- They create BiskitDefs with a type that does not start like “ShardN.” where N is the local shard number, as is a requirement in Enterprise.
- They have been disabled rather than fixed because they’re not enormously useful in production anyway.
- Issue: 4155
BUGFIX: Cannot tell which shard an Enterprise service is for in “Available services” page
- The name of the shard is now shown on the Available Services page entries when running in Enterprise.
- Issue: 4156

1.40 11.5.39 October 18, 2024

Bug Fixes

BUGFIX: Re-import of user can auto-update user status (possible part of infinite loop)
- We can configure the system so that users that are approved anywhere will be approved here, and users that are requested are automatically approved.
- Whenever a user is re-exported, and a shard re-imports the user, this triggers the resetting of a user status, depending on the the above-mentioned settings.
- In particular, if a user is imported and:
  - if a user status is REQUESTED, and auto approval is enabled, then the user status will be set to APPROVED
  - if a user status is INOPERATIVE, and we auto approve shared users that are approved anyway, then the user would be set to APPROVED
- This happened both on import and re-rimport. But it doesn’t feel like the right thing to do to change a user status on a re-import, and so is now only done on a first time import.
- Issue: 4158
BUGFIX: Save an exported biskit without making any changes causes it to be re-exported (possible infinite loop)
- If an exported biskit is saved without making any changes, it is currently re-exported.
- This generates noise, and potentially contributes to an infinite loop of exports.
- Issue: 4159
BUGFIX: Infinite import loop when consecutive import batches are approved together and have different user status
- Suppose:
  - You have two import batches, A and B.
  - They both import the same user
  - But they have a different user status for one of the importing shards
  - Somebody approves the import of both of these batches at the same time.
- Then this leads to an infinite loop of the imports being done, sent out to previous importers of the user who send a message back to the exporter, which will re-send an export message.
- The infinite loop will flip-flop between the user status specified in each of the batches A and B.
- Issue: 4160

1.41 11.5.40 November 1, 2024

Changes

Templates in Enterprise did not let you specify local project type
- When using Enterprise, Templates let you specify which local user type a template applies to, but it did not offer an ability to specify which local project type it applies to.
- This is a missing feature that ought to exist so that local project types can work properly if and when they are used.
- Issue: 4165

Bug Fixes

BUGFIX: Change of Repeat.start from date to datetime causes workflow warnings
- Issue 4138 “Edit the schedule for a report and the start time-of-day is ignored” was fixed in 11.0.7.
- However, the fix for it was bogus. It involved changing Repeat.start so that it is a date-time property instead of just date.
- However, workflows that use Repeat.start would rely on its type being a date without time, and changing this caused warnings from such workflows when you view or edit them, and quite possibly errors at runtime too.
- This has been fixed in 11.0.8 by reverting the fix for 4138. This means issue 4138 exists again and will be fixed in a future version.
- Issue: 4161,4138
BUGFIX: Search for Calpendo Licence gives usedLinkedBookingLinks error
- Search for “Calpendo Licence”, and either show a list report or a group report which includes the new property “usedLinkedBookingLinks”, and you get an error:
  
  IllegalArgumentException during GroupSearchRequest: org.hibernate.QueryException: could not resolve property: usedLinkedBookingLinks of: Calpendo.CalpendoLicence
- This was a bug introduced in 11.0.7 due to a change to allow linked bookings to be added to a Calpendo Starter licence.
- This change had an error in it that meant that Calpendo Licence was not properly defined, and any attempt to access the new usedLinkedBookingLinks property would fail.
- Issue: 4162
BUGFIX: New user and project fragments were not assigned any default values
- If you modify the BiskitDef for a user fragment or project fragment, and set a default value on a custom property, then when you create a user or project, the default value is not set.
- Issue: 4164
BUGFIX: New user exported in Enterprise did not send fragments everywhere
- The changes in 11.5.39 to avoid fragments being sent everywhere repeatedly in an infinite loop were a little too strong.
- When a user is first exported to another shard for the first time, then the importing shard’s new fragment is not sent to other shards.
- It should go to the exporting shard, and also to any other shards that import it.
- Issue: 4166
BUGFIX: ConcurrentModificationException sometimes seen while importing biskits
- Issue: 4167

1.42 11.5.41 November 5, 2024

Bug Fixes

BUGFIX: Edit/save imported user that owns a non-exported project gives error
- If you edit and save an imported user, where that users owns a project that has not been exported to the user’s home shard, then saving the user would generate an error.
- Issue: 4168
BUGFIX: Errors in bookings calendar if there are old templates present
- Suppose you have templates in an 11.5.39 or earlier system, and upgrade to 11.5.40.
- If you then look at the bookings calendar and it includes resources that have any of those templates, an error is displayed saying “Failed to load bookings…”
- Issue: 4169
BUGFIX: “Delete” button enabled at wrong times for imported Enterprise biskits
- Suppose a biskit is shared from one shard to another.
- Then on the importing side, when you view the biskit, the “Delete” button would be greyed out or enabled according to erroneous logic, so that it might be disabled when it should be enabled.
- Issue: 4170
BUGFIX: Enterprise biskit references hides multi-shard references
- When you look at a biskit, and click the references button, then it will show you which shard has a reference from which type of biskit, and via which property.
- However, when multiple shards have references from the same type of biskit and same property name, only the information from one shard would be shown.
- Issue: 4172

1.43 11.5.42 December 6, 2024

Bug Fixes

BUGFIX: Upgrade to 11.5.41 gave boot error on non-Calpendo system
- The database upgrade for issue 4169 should have checked that it was running on a Calpendo system, since the change was only relevant to Calpendo.
- However, it did not do this, and so upgrades would complain as it tried to look for content inside a Calpendo-only table.
- Issue: 4178
BUGFIX: Calendar error if upgrade to 11.5.40/41 with pre-existing templates
- If you have templates and then upgrade to 11.5.40 or 11.5.41, then you get this error in the calendar:
  
  Null value was assigned to a property of primitive type setter of com.springsolutions.calpendo.domain.template.TemplateTAM.equalsLocalProjectType
- Issue: 4192

1.44 11.5.43 December 13, 2024

Bug Fixes

BUGFIX: Exporting project can fail with message “UserIdentity is not mapped [select count(*) from UserIdentity where id = 0]”
- Issue: 4198

1.45 11.5.44 February 7, 2025

Changes

Prevent linked bookings using linkedBookingParent as link to child
- The property Booking.linkedBookingParent exists so that a child linked booking knows who its parent booking is.
- You may also provide a property that allows a parent booking to reference the child.
- This ought to be a custom property that you add for the purpose, as we do not provide a property for it since it necessarily implies that the parent has only a single child, which may not be true.
- However, the UI allowed the property linkedBookingParent to be used for the link from parent to child as well as the link from child to parent.
- This is confusing and so is now prevented.
- Issue: 3645,3847
Sort list reports using the sort order defined in the bakery
- Issue: 3779
Display 3 letters for the month in the navigator above the calendar instead of full month name
- As you clicked the arrows to move forwards or backwards a week or month, then changing from one month to another would mean the buttons would change their location because of the variable month name length.
- Changing this to a constant three letters beings better stability to button locations.
- Issue: 3864
Add support for a number of templates and rules in the licence to override standard starter licence limits
- Currently the starter licence limits the number of templates to four and the number of rules to four, while a premium licence allows an unlimited number.
- We can now alter a licence so that additional templates and rules can be added to a starter licence.
- Issue: 3958
Append trailing slash to system settings Email Base URL if one not provided when configure new system
- The Emailed Base URL system setting can be used by workflows to generate a URL that, when accessed, will result in a call back to Calpendo.
- However, if this doesn’t have a trailing slash, and workflows don’t check for and append a slash, then URLs generated by a workflow will not work.
- When you configure the initial screen for a Calpendo, it asks you for the base URL, and this now has a slash appended automatically if there isn’t already one there.
- Issue: 4059
Add id to buttons and text boxes in login and new user request pages
- This is needed to help automated testing using Selenium, so that it can pick out the various items on the page and target them in a sensible way.
- Issue: 4171
Make the error message from linked bookings more user friendly
- When a linked booking parent cannot be created or updated because an insufficient number of child linked bookings could be created, then the error message presented to the user was a bit confusing.
- This language has now been made clearer.
- Issue: 4175
Add licence type (full/lite/starter etc) to licence server requests
- This means each request for a licence sent to the licence server would additionally specify the current licence type.
- Issue: 4200
Add scripts for exporting attachments to the INSTALL directory
- The Calpendo release now includes a new directory in the archive in INSTALL/export_exprodo_events for exporting attachments programmatically from a script.
- Issue: 4208
Make all biskit type columns use ascii char set and related collation
- Some tables store a column that references a biskit type. There can be one of two reasons for this:
  1. There’s a string-valued property that stores a the type of a biskit
  2. There’s a column used as a discriminator on a table that stores biskits of multiple types, with the discriminator telling us what type of biskit is stored in that row.
- In all cases, we have always enforced the requirement that the text used for a biskit type matches a simple expression that means it consists solely of upper and lower case letters, digits and the underscore.
- In particular, it cannot have accented characters or any exotic non-ASCII characters.
- Each string-valued column stored in the database has associated with it a character set used by that column, and also a collation that specifies how to order and compare values.
- The data stored within these columns is always compatible with the database character set known as ‘ascii’, which reflects the ASCII characters.
- However, the actual character set defined was left to be the default for the database. Since MySQL has changed the default in recent versions, it means that you can have a different character set being used for some of these columns than others.
- The 11.0 upgrade introduces changes to the way repeats are handled.
- In particular, it creates a new “repeats” table which stores a column for a biskit type, and as a part of the upgrade, values stored in this column are compared to the ‘cls’ column in the bookings and templates column.
- However, since the repeats table is new, it was being assigned the new default character set, and the bookings and templates tables being old meant they could use the old default character set. This caused a failure during the upgrade when run on a MySQL database.
- So now we modify all columns that store a biskit type so that they are explicitly declared with the ‘ascii’ character set, along with the default collation for that character set, which is ‘ascii_general_ci’.
- Issue: 4209

Security Fixes

SECURITY FIX: New user registration sends user info to the browser
- On every system, clicking the “Register New User” button results in a list of all registered users (their numerical id number, login name and real name) being sent to the browser.
- On all Calpendo systems, it also sends the id number, project code and name of all projects.
- This user and project information is not usually required, and should not be available before a user has logged in. This represents a data breach since it is possible to enumerate all users and projects on an enterprise system, and all projects on any Calpendo.
- If users reference any other biskits, then all instances of whatever type is referenced is also sent to the browser. This is here so that a user that self-registers can select their user type or department etc.
- However, if there were any sets of biskits attached to a user, for example their training records, then training record id numbers would also be sent, plus any name if they had one.
- Clicking the “Register New User” button results in the browser being sent some information about all users in the system.
- This includes their numerical ID number (which encodes the date/time the user was created), their login name and their real name.
- The ID number, project code and name of all projects was also sent to the browser.
- An attacker could use this to see the names of all users on Calpendo and the date on which they became a user.
- When a user self-registers, there can be drop-downs, like the one that allows them to select their own user type. For this to work, the name and ID number for every user type must be sent to the browser.
- This was looking for any type of biskit referenced by a user, and sending the name and ID number of every biskit of that type.
- The fix specifically prevents user and project information from being included.
- Further, we exclude any biskit type for which the user “nobody” does not have EXISTS permission on every instance of that biskit type. For example, if a user were given a property that referenced a resource, then the name and ID of all resources would be sent to the browser. But if just one resource has a permission that prevents user “nobody” from being able to know it exists, then no resources would be sent to the server.
- Issue: 4294

Bug Fixes

BUGFIX: Template prevents bookings 45 minutes before template start
- Create a template rejecting everyone. Set it to start at 9:00.
- On the calendar, if you click on any quarter-hour from 08:15, the templat rejects you outright whereas one might expect it would allow you to make a booking 08:15-09:00.
- Issue: 3710
BUGFIX: Booking fields that are filtered don’t filter on first click after browser refresh
- Issue: 3761
BUGFIX: Booking references from other biskits do not display name format specified in bakery
- If you have a biskit with a booking field on it (ie that links to a booking and also has the little calendar icon next to it to take you straight to the calendar) then the text used for the link is:
  
  Booking ID/start date/start time/finish time
- This should be whatever is specified in the bakery as the name property or the format definition for the biskit.
- Issue: 3781
BUGFIX: %dateRange% format always repeats the date even for bookings that start and end on the same day
- The dateRange property on a booking is correctly displayed as:
  
  [dateRange.start.date] [dateRange.start.time]-[dateRange.finish.time]
- Except when the booking stretches over more than one day, in which case it is correctly displayed as:
  
  [dateRange.start.date] [dateRange.start.time]- [dateRange.finish.date] [dateRange.finish.time]
- However if you use %dateRange% in the format or when specifying what to show in bookings in the Calendar view, it always uses the version that repeats the date, even for bookings that start and end on the same day.
- Issue: 3782
BUGFIX: Columns displayed in a list report reset to defaults after item in list is edited
- Issue: 3783
BUGFIX: Workflow Search Action using a ‘Not All’ condition returns incorrect results
- When a Workflow Search Action includes a ‘Not All’ condition on the search, then the results it finds are incorrect.
- Issue: 3823
BUGFIX: Display is blank when viewing linked booking null parent-to-child prop
- A linked booking link can define an optional property on the booking that will be used to reference the child booking from the parent.
- If there is no such property configured (which is the most common configuration), and you view a linked booking link in read-only mode, then it would just show blanks for the name of the property, which is not ideal.
- It now says “Parent does not reference child” instead.
- Issue: 3857
BUGFIX: Reports with null conditions cause multiple failures
- Reports can have no conditions, but what that should mean is that the report has conditions that say that are empty rather than the conditions being null.
- No report should ever have null for its conditions, although it has been observed.
- When this happens, it resulted in an error running the report.
- Issue: 3858
BUGFIX: Searching for Calpendo Config generates an IllegalArgumentException
- If you try to search for Calpendo Config, then you get an error:
  
  Failed to fetch data: could not extract ResultSet
- Issue: 3909
BUGFIX: Holiday dates import not accessible to calculateWorkingHours workflow function
- If you use the CSV file import utility to import holiday dates, then the workflow function calculateWorkingHours ignores the imported holiday dates.
- Issue: 3923
BUGFIX: Custom Tree Page with grouping by null-valued biskit gives exception
- When using a resource biskit for dynamic sub nodes on a custom tree page, if one of the resources has no location and location is used as a property to group biskits the page can’t load through menu with an error.
- Issue: 3932
BUGFIX: Resource sort order ignored in Calendar-by-location
- When viewing a calendar page using a calendar-by-location menu item, it shows all the resources in alphabetical order, ignoring any sort order that had been specified in the bakery.
- Issue: 3985
BUGFIX: Workflow sort action fails if the list of biskits contains a null value
- When sorting a list of biskits in a workflow, then if one of the list is null, the sort action fails.
- Issue: 4019
BUGFIX: When multiple template messages should be displayed, some may not be
- If you have a message on a template group, and also have a message on the template directly in the template calendar, then at times when both messages should show, only one does show.
- Issue: 4031
BUGFIX: Default time when creating booking is weird when using predefined time slots
- Issue: 4032
BUGFIX: Breaking booking rule on linked booking of one instance of a repeat prevents further expansion of the repeat
- Issue: 4048
BUGFIX: View history of a linked booking and click on one of past versions gives an exception
- Issue: 4057
BUGFIX: Click on biskit can show error saying possible permissions problem
- Some permissions could result in an error being displayed incorrectly when you click on a biskit.
- Issue: 4099
BUGFIX: Reports with missing columns or bad conditions generate exceptions when run
- Issue: 4105,4121
BUGFIX: Information Pages module does not set up pages in a hierarchy
- Calpendo has a module called “Information Pages” which when loaded allows you to display pages about your facility.
- This allows you to specify that a page has a parent and children, so that the pages display in a hierarchy using a tree structure.
- However, it would always display as a flag list instead of in a tree.
- Issue: 4118
BUGFIX: Cannot disable rule when over limit by more than 1 in Calpendo Starter
- A starter licence allows only a limited number of bookings rules to be used.
- If you are over the limit (perhaps because your licence changed from a premium system to a starter), and try to edit a rule to make it disabled, then you are not able to.
- It gives a message “Failed to save Interval Rule” without any more information.
- Issue: 4137
BUGFIX: Edit the schedule for a report and the start time-of-day is ignored
- Issue: 4138
BUGFIX: Booking repeat displays badly if the booking layout assigns full detail tab to it
- Issue: 4157
BUGFIX: Booking history fails when EXISTS permission depends on type
- Issue: 4173
BUGFIX: Cannot delete bookmarks (error message says it doesn’t exist)
- If you try to delete any bookmark that should be deletable, then it fails with a message to say the bookmark doesn’t exist.
- Issue: 4190
BUGFIX: Workflow action displays in red box on history page
- When a workflow modifies some data, the history page shows which workflow action made the change.
- This is displayed on the history page in a red box, which is normally used to indicate an error.
- The red box no longer displays in this context.
- Issue: 4193
BUGFIX: Click on group report row shows nothing if time condition to-the-hour, minute or second
- Suppose you create a group report of bookings, and add a condition of the form “dateRange.start equals DATE-TIME to the HOUR”.
- Then, if the report finds any bookings, click on any of the rows displayed in the group report and it doesn’t find the bookings in that group, and so does not display them.
- The same happens if you use a condition that is to-the-minute or to-the-second.
- Issue: 4194
BUGFIX: Upgrade directly from 9.0.67 to 11.0 fails
- Issue: 4197
BUGFIX: Tooltip on LinkedBookingLink.cancellationReason does not say when reason will be used
- The tooltip on the cancellation reason on a Linked Booking Link did not make it clear when exactly the provided reason would be used, and it wasn’t otherwise obvious.
- The tooltip has now been clarified.
- Issue: 4201
BUGFIX: Validation errors in linked booking links are not displayed
- If a linked booking link is configured to reference a property that has been deleted, then this gives an error.
- However, the UI does not tell you what the error really is.
- Issue: 4202
BUGFIX: Read-only calendar does not handle non-Latin characters properly
- A read-only calendar displays a non-interactive view of bookings.
- If any of the resource names or bookings contain accented characters, then the calendar does not display properly.
- Issue: 4205
BUGFIX: Read-only calendar in systems created in 10.1 cannot cope with formatted resource IDs
- Any Calpendo that was first created in 10.0 or later has a default workflow that can display an anonymously-accessed read-only non-interactive calendar of bookings. This is disabled by default.
- The workflow will parse arguments in a URL so that you can, amongst other things, define the resources whose bookings should be displayed.
- If you specify the resource IDs using a formatted ID (as is displayed in the Calpendo user interface) then the calendar did not display.
- Issue: 4206
BUGFIX: Read-only calendar sometimes fails when specify large numeric value for resource ID
- The read-only bookings calendar does not display when one of the resources being displayed has an ID greater than 2,147,483,647 and the user that is the source of displayed styles has no user setting for the resource.
- Issue: 4207
BUGFIX: JSON error reported when viewing history of booking modified in 11.0.7
- Whenever a booking that was edited in 11.0.7 then has its history examined in 11.0.8, a JSON error is reported.
- Repeat.status was changed from a date property to date-time in 11.0.7, and then back to a date property in 11.0.8. So if you look at the history of such a booking in 11.0.8, it can’t parse the contents of the historical booking and gives an exception.
- Issue: 4210
BUGFIX: LazyInitializationException updating booking after having modified workflow with BookingRuleWorkflowEvent
- If you modify a workflow that contains a BookingRuleWorkflowEvent, then any time you create or update a booking thereafter you get an exception and are prevented from making the change.
- The only work-around is to restart Tomcat after updating any workflow with a BookingRuleWorkflowEvent.
- Issue: 4257
BUGFIX: “could not initialize proxy” error when adding a note to a project
- One can configure projects, or indeed any biskit type, to have attached text notes.
- Notes can be easily created from the project view, and show who created it and when.
- In 11.0, creating such a note gives an exception.
- Issue: 4274
BUGFIX: Configure notes in layout and then view layout shows misconfigured
- After configuring a layout so that a biskit will have a means of attaching text notes, then after refreshing the browser, the display will indicate there is a configuration error with the layout when there is nothing wrong with it.
- Issue: 4276
BUGFIX: Booking reminders partially broken - wrong content and tries to send emails to email address “null”
- The reminder system is not working properly in 11.0. There’s a base Exprodo reminder system, and a Calpendo reminder system built on top of it. The Calpendo reminder system was not booted, so we were only left with the default reminders instead.
- This meant:
  - The subject on reminder emails for bookings was “Reminder for Booking” rather than “Calpendo booking reminder for [resourceName]”
  - Reminders went to everybody who had ever edited a booking rather than to the people requested on the booking (eg remind booker, owner, project owner or project users)
  - The content of the reminder was more basic than content designed specifically for Calpendo.
  - Instances of repeat bookings are generated by user “nobody”. So “nobody” would also receive a reminder. But “nobody” has no email address, and so there would be errors reported saying that an email could not be delivered to “null”.
- Issue: 4277
BUGFIX: SQL Export of reports & timed workflow events broke start & finish
- If you have a report or timed workflow event that is set to repeat, and you export the report/workflow to SQL and use that to import into another database, then the imported report/workflow would be broken.
- The repeat’s start and finish date were not loaded.
- This would mean the repeat would be seen to repeat forever, even if the original was set to finish on a set date.
- Also, having no repeat start breaks it completely and prevents the things from working at all in 11.0.8
- Issue: 4278
BUGFIX: TimedEvents don’t work if the start date/time is null and users don’t see the start date/time
- Issue 4278 means that when you export a workflow to SQL and then import it, and the workflow contains a timed event that repeats, then the imported timed event has null for the repeat start.
- The user is shown a date/time for a timed event, but it’s actually a separate property from the repeat start, since the event has a time even if it does not repeat.
- In other words, a timed event that repeats has two properties that contain a date/time and that should have the same value.
- Issue 4278 means one of those properties can be set to null, and it’s the one that’s never shown to the user, so you have no way of knowing that there’s anything wrong with the timed event.
- This has been changed so that there is only one date/time in a timed event.
- It’s the time when the event happens, and for a timed event that repeats, it’s also the repeat start.
- Issue: 4279
BUGFIX: Permissions for repeat templates & bookings are overly restrictive
- The change to the way repeats work in 11.0 completely changed the way bookings and templates handle repeats. One of the consequences of this is that a repeat is now a separate biskit that can be queried and modified where before it could be.
- That’s because repeats used to exist only as an integral part of the booking or template that owned it, and was stored in the same database table row as the booking or template.
- This meant that there was only ever one row for a repeat booking, and so all instances in a sequence had to be identical.
- This is now different, and it means the repeat information now lives in a table of its own.
- When you edit a repeat booking in such a way that it required a change to the repeat as well as the booking, then it was checking that you had permission to change the repeat as well as that you had permission to change the booking.
- However, this doesn’t and can’t work because the repeat does not have enough context to evaluate whether you should be allowed to modify it.
- For example, there is no permission one could express directly for the repeat to indicate that the resource’s manager user group should be permitted to modify the repeat because the repeat does not store a reference to the booking.
- So now when you modify a repeat booking, it will only check permissions for changing the booking. If you want to limit what can be done to repeats, then create a permission on the booking or template to do so.
- Issue: 4280
BUGFIX: User names with a period in them are rejected
- Issue: 4291
BUGFIX: Boot fails every 10,000 boots with complaint about ApproxateDate.year not being saved by its DTO
- At boot time, we run automated tests to make sure that any classes that use a data transfer object (DTO) to transport their data over the network are well defined.
- Occasionally, when there’s a check on the biskit ApproximateDate’s year, this will fail complaining that it put in zero and got out null with this error message:
  
  Property ApproximateDate.year appears not to be saved by its DTO (put in ‘0’, and got out ‘null’)
- This error happens on average once every 10,000 boot cycles as it depends on a random number from 0 to 9,999 coming out as zero.
- Issue: 4298

1.46 11.5.45 February 8, 2025

Changes

Prevent linked bookings using linkedBookingParent as link to child
- The property Booking.linkedBookingParent exists so that a child linked booking knows who its parent booking is.
- You may also provide a property that allows a parent booking to reference the child.
- This ought to be a custom property that you add for the purpose, as we do not provide a property for it since it necessarily implies that the parent has only a single child, which may not be true.
- However, the UI allowed the property linkedBookingParent to be used for the link from parent to child as well as the link from child to parent.
- This is confusing and so is now prevented.
- Issue: 3645,3847
Sort list reports using the sort order defined in the bakery
- Issue: 3779
Display 3 letters for the month in the navigator above the calendar instead of full month name
- As you clicked the arrows to move forwards or backwards a week or month, then changing from one month to another would mean the buttons would change their location because of the variable month name length.
- Changing this to a constant three letters beings better stability to button locations.
- Issue: 3864
Add support for a number of templates and rules in the licence to override standard starter licence limits
- Currently the starter licence limits the number of templates to four and the number of rules to four, while a premium licence allows an unlimited number.
- We can now alter a licence so that additional templates and rules can be added to a starter licence.
- Issue: 3958
Append trailing slash to system settings Email Base URL if one not provided when configure new system
- The Emailed Base URL system setting can be used by workflows to generate a URL that, when accessed, will result in a call back to Calpendo.
- However, if this doesn’t have a trailing slash, and workflows don’t check for and append a slash, then URLs generated by a workflow will not work.
- When you configure the initial screen for a Calpendo, it asks you for the base URL, and this now has a slash appended automatically if there isn’t already one there.
- Issue: 4059
Add id to buttons and text boxes in login and new user request pages
- This is needed to help automated testing using Selenium, so that it can pick out the various items on the page and target them in a sensible way.
- Issue: 4171
Make the error message from linked bookings more user friendly
- When a linked booking parent cannot be created or updated because an insufficient number of child linked bookings could be created, then the error message presented to the user was a bit confusing.
- This language has now been made clearer.
- Issue: 4175
Add licence type (full/lite/starter etc) to licence server requests
- This means each request for a licence sent to the licence server would additionally specify the current licence type.
- Issue: 4200
Add scripts for exporting attachments to the INSTALL directory
- The Calpendo release now includes a new directory in the archive in INSTALL/export_exprodo_events for exporting attachments programmatically from a script.
- Issue: 4208
Make all biskit type columns use ascii char set and related collation
- Some tables store a column that references a biskit type. There can be one of two reasons for this:
  1. There’s a string-valued property that stores a the type of a biskit
  2. There’s a column used as a discriminator on a table that stores biskits of multiple types, with the discriminator telling us what type of biskit is stored in that row.
- In all cases, we have always enforced the requirement that the text used for a biskit type matches a simple expression that means it consists solely of upper and lower case letters, digits and the underscore.
- In particular, it cannot have accented characters or any exotic non-ASCII characters.
- Each string-valued column stored in the database has associated with it a character set used by that column, and also a collation that specifies how to order and compare values.
- The data stored within these columns is always compatible with the database character set known as ‘ascii’, which reflects the ASCII characters.
- However, the actual character set defined was left to be the default for the database. Since MySQL has changed the default in recent versions, it means that you can have a different character set being used for some of these columns than others.
- The 11.0 upgrade introduces changes to the way repeats are handled.
- In particular, it creates a new “repeats” table which stores a column for a biskit type, and as a part of the upgrade, values stored in this column are compared to the ‘cls’ column in the bookings and templates column.
- However, since the repeats table is new, it was being assigned the new default character set, and the bookings and templates tables being old meant they could use the old default character set. This caused a failure during the upgrade when run on a MySQL database.
- So now we modify all columns that store a biskit type so that they are explicitly declared with the ‘ascii’ character set, along with the default collation for that character set, which is ‘ascii_general_ci’.
- Issue: 4209

Security Fixes

SECURITY FIX: New user registration sends user info to the browser
- On every system, clicking the “Register New User” button results in a list of all registered users (their numerical id number, login name and real name) being sent to the browser.
- On all Calpendo systems, it also sends the id number, project code and name of all projects.
- This user and project information is not usually required, and should not be available before a user has logged in. This represents a data breach since it is possible to enumerate all users and projects on an enterprise system, and all projects on any Calpendo.
- If users reference any other biskits, then all instances of whatever type is referenced is also sent to the browser. This is here so that a user that self-registers can select their user type or department etc.
- However, if there were any sets of biskits attached to a user, for example their training records, then training record id numbers would also be sent, plus any name if they had one.
- Clicking the “Register New User” button results in the browser being sent some information about all users in the system.
- This includes their numerical ID number (which encodes the date/time the user was created), their login name and their real name.
- The ID number, project code and name of all projects was also sent to the browser.
- An attacker could use this to see the names of all users on Calpendo and the date on which they became a user.
- When a user self-registers, there can be drop-downs, like the one that allows them to select their own user type. For this to work, the name and ID number for every user type must be sent to the browser.
- This was looking for any type of biskit referenced by a user, and sending the name and ID number of every biskit of that type.
- The fix specifically prevents user and project information from being included.
- Further, we exclude any biskit type for which the user “nobody” does not have EXISTS permission on every instance of that biskit type. For example, if a user were given a property that referenced a resource, then the name and ID of all resources would be sent to the browser. But if just one resource has a permission that prevents user “nobody” from being able to know it exists, then no resources would be sent to the server.
- Issue: 4294

Bug Fixes

BUGFIX: Template prevents bookings 45 minutes before template start
- Create a template rejecting everyone. Set it to start at 9:00.
- On the calendar, if you click on any quarter-hour from 08:15, the templat rejects you outright whereas one might expect it would allow you to make a booking 08:15-09:00.
- Issue: 3710
BUGFIX: Booking fields that are filtered don’t filter on first click after browser refresh
- Issue: 3761
BUGFIX: Booking references from other biskits do not display name format specified in bakery
- If you have a biskit with a booking field on it (ie that links to a booking and also has the little calendar icon next to it to take you straight to the calendar) then the text used for the link is:
  
  Booking ID/start date/start time/finish time
- This should be whatever is specified in the bakery as the name property or the format definition for the biskit.
- Issue: 3781
BUGFIX: %dateRange% format always repeats the date even for bookings that start and end on the same day
- The dateRange property on a booking is correctly displayed as:
  
  [dateRange.start.date] [dateRange.start.time]-[dateRange.finish.time]
- Except when the booking stretches over more than one day, in which case it is correctly displayed as:
  
  [dateRange.start.date] [dateRange.start.time]- [dateRange.finish.date] [dateRange.finish.time]
- However if you use %dateRange% in the format or when specifying what to show in bookings in the Calendar view, it always uses the version that repeats the date, even for bookings that start and end on the same day.
- Issue: 3782
BUGFIX: Columns displayed in a list report reset to defaults after item in list is edited
- Issue: 3783
BUGFIX: Workflow Search Action using a ‘Not All’ condition returns incorrect results
- When a Workflow Search Action includes a ‘Not All’ condition on the search, then the results it finds are incorrect.
- Issue: 3823
BUGFIX: Display is blank when viewing linked booking null parent-to-child prop
- A linked booking link can define an optional property on the booking that will be used to reference the child booking from the parent.
- If there is no such property configured (which is the most common configuration), and you view a linked booking link in read-only mode, then it would just show blanks for the name of the property, which is not ideal.
- It now says “Parent does not reference child” instead.
- Issue: 3857
BUGFIX: Reports with null conditions cause multiple failures
- Reports can have no conditions, but what that should mean is that the report has conditions that say that are empty rather than the conditions being null.
- No report should ever have null for its conditions, although it has been observed.
- When this happens, it resulted in an error running the report.
- Issue: 3858
BUGFIX: Searching for Calpendo Config generates an IllegalArgumentException
- If you try to search for Calpendo Config, then you get an error:
  
  Failed to fetch data: could not extract ResultSet
- Issue: 3909
BUGFIX: Holiday dates import not accessible to calculateWorkingHours workflow function
- If you use the CSV file import utility to import holiday dates, then the workflow function calculateWorkingHours ignores the imported holiday dates.
- Issue: 3923
BUGFIX: Custom Tree Page with grouping by null-valued biskit gives exception
- When using a resource biskit for dynamic sub nodes on a custom tree page, if one of the resources has no location and location is used as a property to group biskits the page can’t load through menu with an error.
- Issue: 3932
BUGFIX: Resource sort order ignored in Calendar-by-location
- When viewing a calendar page using a calendar-by-location menu item, it shows all the resources in alphabetical order, ignoring any sort order that had been specified in the bakery.
- Issue: 3985
BUGFIX: Workflow sort action fails if the list of biskits contains a null value
- When sorting a list of biskits in a workflow, then if one of the list is null, the sort action fails.
- Issue: 4019
BUGFIX: When multiple template messages should be displayed, some may not be
- If you have a message on a template group, and also have a message on the template directly in the template calendar, then at times when both messages should show, only one does show.
- Issue: 4031
BUGFIX: Default time when creating booking is weird when using predefined time slots
- Issue: 4032
BUGFIX: Breaking booking rule on linked booking of one instance of a repeat prevents further expansion of the repeat
- Issue: 4048
BUGFIX: View history of a linked booking and click on one of past versions gives an exception
- Issue: 4057
BUGFIX: Click on biskit can show error saying possible permissions problem
- Some permissions could result in an error being displayed incorrectly when you click on a biskit.
- Issue: 4099
BUGFIX: Reports with missing columns or bad conditions generate exceptions when run
- Issue: 4105,4121
BUGFIX: Information Pages module does not set up pages in a hierarchy
- Calpendo has a module called “Information Pages” which when loaded allows you to display pages about your facility.
- This allows you to specify that a page has a parent and children, so that the pages display in a hierarchy using a tree structure.
- However, it would always display as a flag list instead of in a tree.
- Issue: 4118
BUGFIX: Cannot disable rule when over limit by more than 1 in Calpendo Starter
- A starter licence allows only a limited number of bookings rules to be used.
- If you are over the limit (perhaps because your licence changed from a premium system to a starter), and try to edit a rule to make it disabled, then you are not able to.
- It gives a message “Failed to save Interval Rule” without any more information.
- Issue: 4137
BUGFIX: Edit the schedule for a report and the start time-of-day is ignored
- Issue: 4138
BUGFIX: Booking repeat displays badly if the booking layout assigns full detail tab to it
- Issue: 4157
BUGFIX: Booking history fails when EXISTS permission depends on type
- Issue: 4173
BUGFIX: Cannot delete bookmarks (error message says it doesn’t exist)
- If you try to delete any bookmark that should be deletable, then it fails with a message to say the bookmark doesn’t exist.
- Issue: 4190
BUGFIX: Workflow action displays in red box on history page
- When a workflow modifies some data, the history page shows which workflow action made the change.
- This is displayed on the history page in a red box, which is normally used to indicate an error.
- The red box no longer displays in this context.
- Issue: 4193
BUGFIX: Click on group report row shows nothing if time condition to-the-hour, minute or second
- Suppose you create a group report of bookings, and add a condition of the form “dateRange.start equals DATE-TIME to the HOUR”.
- Then, if the report finds any bookings, click on any of the rows displayed in the group report and it doesn’t find the bookings in that group, and so does not display them.
- The same happens if you use a condition that is to-the-minute or to-the-second.
- Issue: 4194
BUGFIX: Upgrade directly from 9.0.67 to 11.0 fails
- Issue: 4197
BUGFIX: Tooltip on LinkedBookingLink.cancellationReason does not say when reason will be used
- The tooltip on the cancellation reason on a Linked Booking Link did not make it clear when exactly the provided reason would be used, and it wasn’t otherwise obvious.
- The tooltip has now been clarified.
- Issue: 4201
BUGFIX: Validation errors in linked booking links are not displayed
- If a linked booking link is configured to reference a property that has been deleted, then this gives an error.
- However, the UI does not tell you what the error really is.
- Issue: 4202
BUGFIX: Read-only calendar does not handle non-Latin characters properly
- A read-only calendar displays a non-interactive view of bookings.
- If any of the resource names or bookings contain accented characters, then the calendar does not display properly.
- Issue: 4205
BUGFIX: Read-only calendar in systems created in 10.1 cannot cope with formatted resource IDs
- Any Calpendo that was first created in 10.0 or later has a default workflow that can display an anonymously-accessed read-only non-interactive calendar of bookings. This is disabled by default.
- The workflow will parse arguments in a URL so that you can, amongst other things, define the resources whose bookings should be displayed.
- If you specify the resource IDs using a formatted ID (as is displayed in the Calpendo user interface) then the calendar did not display.
- Issue: 4206
BUGFIX: Read-only calendar sometimes fails when specify large numeric value for resource ID
- The read-only bookings calendar does not display when one of the resources being displayed has an ID greater than 2,147,483,647 and the user that is the source of displayed styles has no user setting for the resource.
- Issue: 4207
BUGFIX: JSON error reported when viewing history of booking modified in 11.0.7
- Whenever a booking that was edited in 11.0.7 then has its history examined in 11.0.8, a JSON error is reported.
- Repeat.status was changed from a date property to date-time in 11.0.7, and then back to a date property in 11.0.8. So if you look at the history of such a booking in 11.0.8, it can’t parse the contents of the historical booking and gives an exception.
- Issue: 4210
BUGFIX: LazyInitializationException updating booking after having modified workflow with BookingRuleWorkflowEvent
- If you modify a workflow that contains a BookingRuleWorkflowEvent, then any time you create or update a booking thereafter you get an exception and are prevented from making the change.
- The only work-around is to restart Tomcat after updating any workflow with a BookingRuleWorkflowEvent.
- Issue: 4257
BUGFIX: “could not initialize proxy” error when adding a note to a project
- One can configure projects, or indeed any biskit type, to have attached text notes.
- Notes can be easily created from the project view, and show who created it and when.
- In 11.0, creating such a note gives an exception.
- Issue: 4274
BUGFIX: Configure notes in layout and then view layout shows misconfigured
- After configuring a layout so that a biskit will have a means of attaching text notes, then after refreshing the browser, the display will indicate there is a configuration error with the layout when there is nothing wrong with it.
- Issue: 4276
BUGFIX: Booking reminders partially broken - wrong content and tries to send emails to email address “null”
- The reminder system is not working properly in 11.0. There’s a base Exprodo reminder system, and a Calpendo reminder system built on top of it. The Calpendo reminder system was not booted, so we were only left with the default reminders instead.
- This meant:
  - The subject on reminder emails for bookings was “Reminder for Booking” rather than “Calpendo booking reminder for [resourceName]”
  - Reminders went to everybody who had ever edited a booking rather than to the people requested on the booking (eg remind booker, owner, project owner or project users)
  - The content of the reminder was more basic than content designed specifically for Calpendo.
  - Instances of repeat bookings are generated by user “nobody”. So “nobody” would also receive a reminder. But “nobody” has no email address, and so there would be errors reported saying that an email could not be delivered to “null”.
- Issue: 4277
BUGFIX: SQL Export of reports & timed workflow events broke start & finish
- If you have a report or timed workflow event that is set to repeat, and you export the report/workflow to SQL and use that to import into another database, then the imported report/workflow would be broken.
- The repeat’s start and finish date were not loaded.
- This would mean the repeat would be seen to repeat forever, even if the original was set to finish on a set date.
- Also, having no repeat start breaks it completely and prevents the things from working at all in 11.0.8
- Issue: 4278
BUGFIX: TimedEvents don’t work if the start date/time is null and users don’t see the start date/time
- Issue 4278 means that when you export a workflow to SQL and then import it, and the workflow contains a timed event that repeats, then the imported timed event has null for the repeat start.
- The user is shown a date/time for a timed event, but it’s actually a separate property from the repeat start, since the event has a time even if it does not repeat.
- In other words, a timed event that repeats has two properties that contain a date/time and that should have the same value.
- Issue 4278 means one of those properties can be set to null, and it’s the one that’s never shown to the user, so you have no way of knowing that there’s anything wrong with the timed event.
- This has been changed so that there is only one date/time in a timed event.
- It’s the time when the event happens, and for a timed event that repeats, it’s also the repeat start.
- Issue: 4279
BUGFIX: Permissions for repeat templates & bookings are overly restrictive
- The change to the way repeats work in 11.0 completely changed the way bookings and templates handle repeats. One of the consequences of this is that a repeat is now a separate biskit that can be queried and modified where before it could be.
- That’s because repeats used to exist only as an integral part of the booking or template that owned it, and was stored in the same database table row as the booking or template.
- This meant that there was only ever one row for a repeat booking, and so all instances in a sequence had to be identical.
- This is now different, and it means the repeat information now lives in a table of its own.
- When you edit a repeat booking in such a way that it required a change to the repeat as well as the booking, then it was checking that you had permission to change the repeat as well as that you had permission to change the booking.
- However, this doesn’t and can’t work because the repeat does not have enough context to evaluate whether you should be allowed to modify it.
- For example, there is no permission one could express directly for the repeat to indicate that the resource’s manager user group should be permitted to modify the repeat because the repeat does not store a reference to the booking.
- So now when you modify a repeat booking, it will only check permissions for changing the booking. If you want to limit what can be done to repeats, then create a permission on the booking or template to do so.
- Issue: 4280
BUGFIX: User names with a period in them are rejected
- Issue: 4291
BUGFIX: Boot fails every 10,000 boots with complaint about ApproxateDate.year not being saved by its DTO
- At boot time, we run automated tests to make sure that any classes that use a data transfer object (DTO) to transport their data over the network are well defined.
- Occasionally, when there’s a check on the biskit ApproximateDate’s year, this will fail complaining that it put in zero and got out null with this error message:
  
  Property ApproximateDate.year appears not to be saved by its DTO (put in ‘0’, and got out ‘null’)
- This error happens on average once every 10,000 boot cycles as it depends on a random number from 0 to 9,999 coming out as zero.
- Issue: 4298
BUGFIX: New user registration fails in an Enterprise system
- When you try to register, it appears to work except that an error flashes up briefly after you enter your details and click the register button.
- The message says something like:
  
  Could not create fragment 956 for a child of ExprodoUser - that is probably not fragmented. We calculated the fragment type as ExprodoUserFragment956
- This bug was introduced in 11.5.40 as part of the fix for issue 4164.
- Issue: 4314
BUGFIX: Cannot log in if login name contains the @ symbol
- 11.0.9 (and so also 11.5.44) introduced a limit to the characters that can be used in a login name.
- However, there are pre-existing users that break the rule, and so can’t log in. Also, they don’t necessarily get a choice of login name when using a single-sign-on system.
- In particular, the @ symbol being prohibited is a problem if login names look like email addresses.
- This was the set of characters not allowed:
```
  TAB
  SPACE
  !"£$%^&*()=+{}[]~#'@;:/?<>,|\
  
```
- This has been changed to be more liberal in 11.0.10 so that the illegal characters are:
```
  TAB
  SPACE
  !"&*(){}[]';?<>
  
```
- Issue: 4322

1.47 11.5.46 February 10, 2025

Bug Fixes

BUGFIX: Database upgrade error in non-Calpendo apps in scripts for 11.0.7
- The two database upgrade scripts in 11.0.7/3 are only meant for Calpendo, but neither script specified that it was Calpendo-only and so they ran in other Exprodo apps too.
- This meant that upgrading non-Calpendo apps would result in a database upgrade error, albeit a benign one that needed no remediation.
- Issue: 4324

1.48 11.5.47 February 13, 2025

Bug Fixes

BUGFIX: Edit a child linked booking and you get a shallow exception
- Issue: 4334
BUGFIX: Error messages containing HTML “br” tags in linked booking error popup
- Suppose you have a linked booking and you drag the parent to a time where the child booking would clash with another booking so that it triggers a double booking rule.
- Then the error message that is shown contains “
  ” as visible text.
- This happens because of a security change for issue 4212 that prevented user-provided html from appearing in error pop-ups as it was a potential source of an attack.
- So any text in a pop-up is now treated as plain text rather than parsed as html.
- However, linked booking messages use “
  ” as a way to generate a new line in error message, so this is now treated specially.
- Issue: 4335

1.49 11.5.48 March 19, 2025

Bug Fixes

BUGFIX: Calendar by location not filtering resources
- You can add menu item called “Calendar by location”.
- This adds an item to the menu that expands out to provide an entry for every location that contains at least one resource. Click on the location, and it takes you to a calendar for all the resources in that location.
- However, this had stopped working so that it was instead showing all resources.
- This bug was introduced in 11.0.9.3, 11.5.44 and 12.0.4 as a result of the fix for issue 3985.
- Issue: 4325

1.50 11.5.49 March 24, 2025

Bug Fixes

BUGFIX: New user registration fails in an Enterprise system
- Regardless of what type of authentication method you use, at the point where you’ve filled in your name and email address, and then click the Register button, the display would switch to the login page with no additional information displayed, and your details would not be recorded.
- This is a follow-on from issue 4164 which fixed another aspect of new user registration failing.
- Issue: 4314

1.51 11.5.50 April 2, 2025

Changes

Add verbose logging to track file uploads
- When uploading a file and storing it in the database, there is now a variety of logging done to help track down what’s happening if things go wrong.
- This is enabled by going to #verboseSearch and turning on the verbose setting for AttachmentDAO, TemporaryFileManager and ExprodoUploadServlet.
- Issue: 4367
Add support for a downloadable browser log
- Sometimes it is necessary for a customer to do something that generates log output in the browser itself.
- We now have added support for this, and will instruct customers individually if and when this is required.
- Issue: 4374
Add version number to “Boot” system events to make it easier to see
- Every time the system boots, there are messages with a category of “Boot” that say the system is booting, and then that it is booted.
- These now have the version number appended to the message so that it’s easier to see which version was booted and when by looking at the system events.
- Previously, one had to open each boot message individually to see the version that was booted.
- Instead, now you can just ask for the “message” column to be displayed, and then you can easily see which version was booted by showing system events in the “Boot” category.
- Issue: 4376

Security Fixes

SECURITY FIX: File upload and download put session ID into URL
- When you have an attachment on a biskit, and view the biskit in a read-only context, then the link to show the attachment has a URL that includes putting your session ID into the URL.
- This is bad for security because it means the session ID is visible to anybody looking at server logs, which is not ideal.
- When you upload a file, that can send multiple network messages to the server, some of which also include putting your session ID in the URL. This happens more if the file you are uploading is large, or if your network connection is slow (so that the browser asks for status updates while the file is uploading).
- The session ID has now been removed from these things.
- Issue: 4379
SECURITY FIX: Temporary files can be downloaded without being logged in
- Temporary files are generated in several circumstances. For example:
  - when somebody runs a report and asks for it to be exported, it is first generated and written to a file before the user downloads it
  - when the database dump facility is used, the dump is first written to a temporary file before being downloaded
  - when uploading a new attachment, the file is first written to a temporary file, until the biskit the uploaded file is attached to is saved, at which point the attachment is written into the datbase
- Downloading those files would then require a key that had generated for it.
- However, the download itself did not require that the user be logged in.
- This would mean there’s a time window when a temporary file could be downloaded by somebody else. This would require that an attacker get a copy of the file’s key (which is very hard to guess as it contains a 16 character random text string), and they use it between the temporary file being created and deleted.
- Temporary files are normally deleted either when the user that generated them logged out, or periodically Calpendo would look for temporary files older than one hour and delete them. This used to happen every 24 hours but now happens every 4 hours.
- So the opportunity to exploit the weakness would be very limited.
- We now require that the user is logged in, so they must have a cookie containing a valid session ID, and the temporary file must have been created for the user logged in when the download occurs.
- Issue: 4380
SECURITY FIX: Limit users to downloading temporary files they generated
- Whenever a temporary file is generated, it is because of the action of some user. That user is recorded against the temporary file so we know who caused it to be created.
- When downloading a temporary file, we not limit the download to the same user that created it. Temporary files are generated as part of a wider action by the user, and there’s no need for anybody to download a temporary file generated by somebody else.
- The security benefit from this is probably quite limited because it would be quite difficult for an attacker to download a temporary file generated by somebody else.
- Issue: 4382

Bug Fixes

BUGFIX: Parent linked booking allowed to change to time when child is refused
- Suppose you have resources “parent” and “child”, and set up a linked booking link so that booking for parent creates a booking for child at the same time.
- Then create a booking for parent, so that it creates a child booking.
- Then change the time for the parent booking so that the child booking would clash with the time of a pre-existing child booking, and the user would see an error saying the child could not be updated, but the parent would still be allowed to change.
- This is now changed so that the parent will not be allowed to change if any change to a child linked booking is not allowed.
- Issue: 4199
BUGFIX: Calendar by location not filtering resources
- You can add menu item called “Calendar by location”.
- This adds an item to the menu that expands out to provide an entry for every location that contains at least one resource. Click on the location, and it takes you to a calendar for all the resources in that location.
- However, this had stopped working so that it was instead showing all resources.
- This bug was introduced in 11.0.9.3, 11.5.44 and 12.0.4 as a result of the fix for issue 3985.
- Issue: 4325
BUGFIX: Cannot save a workflow function with MappedString argument
- If you try add a custom workflow function that has a Mapped String as an argument, then it gives an exception when you save it.
- Issue: 4350
BUGFIX: Cannot boot when custom function has mapped int arg with no mapped int
- If you have a custom function in a workflow, which has an argument taking a MappedInt, but that does not specify which Mapped Int it should be, then the system will not boot.
- Note that it’s not easy to generate this situation because the UI will force you to choose a Mapped Int.
- However, if you use the SQL export facility, and then import that SQL to another system, it is quite possible to have no MappedInt set on a custom function argument thereby generating this error.
- Issue: 4351
BUGFIX: Cannot boot when a function action references unknown biskit type
- If a custom function in a workflow specifies an argument that takes a biskit, but it does not specify which type of biskit it is, then the system cannot boot.
- Note that it’s not easy to generate this situation because the UI will force you to choose a BiskitDef.
- However, if you use the SQL export facility, and then import that SQL to another system, it is quite possible to have no BiskitDef set on a custom function argument thereby generating this error.
- Issue: 4353
BUGFIX: Validating workflows does not show errors like unknown BiskitDef
- If a workflow function references a BiskitDef that does not exist, then clicking “Validate Workflows” did not show the correct error message for it. (But then, it wouldn’t boot before now either).
- Also, clicking on a workflow that included such an error would show an exception pop-up instead of the normal validation error pop-up.
- Issue: 4354
BUGFIX: DB schema update fails with message “wrong column type column [start] in table [report_schedules]”
- Issue: 4366
BUGFIX: Uploading files logs errors for things that are not errors
- When you upload a file, there are some logged errors that include the text “UPLOAD-SERVLET” in the message, none of which are actually errors.
- These should be logged as DEBUG instead of ERROR.
- Issue: 4368
BUGFIX: Update project to assign new user as owner gives ClassCastException
- This only happened in limited circumstances, when some debug options were enabled and you edit a project and change the owner to some user not currently associated with the project (and not yourself).
- Issue: 4369
BUGFIX: Copy biskits with attachments and new attachment says it has size zero
- For example, add an attachment to a booking. Copy the booking on the calendar, and create a new booking. The attachment will be copied to the new booking, which will work.
- However, when you look at what the attachment thinks its size is, it says zero.
- You can see this in the UI by searching for bookings in the Bookings->Search page, run a group report, and show the attachment.size property.
- However, the attachment does have a real size, and downloads properly, so it is lying about being zero length.
- Issue: 4370
BUGFIX: Uploaded files from anonymous user if login name contains @
- If a login name contains the @ symbol, files uploaded by them would end up not being associated with that user, but as though uploaded anonymously.
- Such anonymous uploads used to be accepted, but no longer are.
- Issue: 4371
BUGFIX: Updating DB schema complains about workflows.finish column type
- Issue: 4372
BUGFIX: File uploads sometimes end up with zero length files
- When a file is uploaded as an attachment to something, then it was sometimes ending up as a zero length attachment.
- Issue: 4375
BUGFIX: Repeat.ownerId shows value in reports not formatted as a primary key
- Reports showing a value of Repeat.ownerId would show a plain (and large) number instead of formatting it like ID numbers are formatted elsewhere in Calpendo.
- Issue: 4377
BUGFIX: History on a Holiday Date Rule gives a ClassCastException
- If you have a Holiday Date Rule that contains dates, and try to view the history of changes to the rule, then clicking on any of the versions where it had some holiday dates would given an exception.
- Issue: 4378
BUGFIX: When child linked booking change denied, user sees same message twice
- Suppose you have a linked booking configured, and you have a parent and child booking.
- They move the parent to a time whereby the child would clash with another booking on the child’s resource.
- Then the pop-up the user sees has the same message twice.
- Issue: 4383
BUGFIX: Bad msg format if booking update gives multiple linked booking errors
- Suppose you have a linked booking configured, and you have a parent and child booking.
- They move the parent to a time whereby the child would clash with another booking on the child’s resource.
- Then the pop-up the user sees has a message containing the HTML tag “br” displayed as text.
- Issue: 4384
BUGFIX: Enterprise cannot boot when running on MySQL rather than MariaDB
- Issue: 4387

1.52 11.5.51 May 9, 2025

Changes

Add support for system setting to allow file upload before user is registered
- When a new user registers themselves to request an account, they are offered a form including most of the properties on a user.
- If there is a property that stores a file attachment, then this will let them upload a file.
- By default, we now prevent file uploads before a user has logged in. This is what we refer to as an anonymous file upload because at the time the user is registering themselves as a user, we don’t know who they are.
- You may or may not require that users be able to upload a file at the time they register themselves as a user, and there is now a system setting to allow the choice to be made.
- This is on the “Security” tab, and is referred to as allowing anonymous file uploads.
- This is disabled by default so that users registering themselves are not allowed to upload a file.
- Issue: 4406
Provide indication of why session cookies do not work when they are broken
- With a server misconfiguration, it is possible that the JSESSIONID cookie is not visible to the browser. This cookie is used when files are uploaded from the browser. If there is a problem with the cookie, then some things don’t work as well. For example, if you try to upload a file that is larger than the maximum allowed size, then the user may not be told because it is possible the browser cannot work out that this is the problem.
- The principle reason for this going wrong is that the server has a context path at which the application is found, and this path is stored on the returned cookie header. If that path does not match the path used by the browser, then the cookie will be hidden from the application by the browser.
- These paths can mismatch when there is a reverse proxy (such as Apache HTTP server) that rewrites the paths. In this case, it would be necessary to rewrite the cookie paths as well, using a ProxyPassReverseCookiePath directive in Apache. Without it, the change of paths causes the cookie to be hidden.
- When a file upload is performed for the first time in a browser session, this problem is detected. The browser now logs a message to indicate the server and client context path along with a suggestion for a server configuration change that might fix the problem.
- Issue: 4414

Bug Fixes

BUGFIX: Enterprise export of project with a populated one-to-many property fails
- Issue: 4203
BUGFIX: Default database workflow events on new system do not have an update phase set on database events
- When a new virgin database is created, it comes with some default workflows that send emails when a user registers and other things relating to the user lifecycle.
- None of the DatabaseWorkflowEvents created have a “Database Update Phase” set on them, and this is a required part of dtabase events.
- This means they don’t run at all.
- New systems created from now on will have this set correctly, and any pre-existing systems which have a DatabaseWorkflowEvents without a “Database Update Phase” set on them will automatically have it set to “After transaction”.
- Issue: 4373
BUGFIX: Report columns “lastRepeat.start” and “lastRepeat.finish” are not deleted in upgrading to 11.0 and so give errors
- The lastRepeat property was removed in 11.0 from Booking and Template, and there was a database upgrade in 11.0.5 to remove columns in reports that referenced lastRepeat.
- However, it was written in such a way that it missed any column lastRepeat.foo for some pseudo-property of lastRepeat.
- For example, a report that references lastRepeat.start or lastRepeat.finish or lastRepeat.start.year etc would not be deleted.
- This means that after upgrade, it would still have a column referencing lastRepeat, and cause an error when such a report was run.
- These columns are now automatically removed.
- Issue: 4401
BUGFIX: User registration page doesn’t load if there is an attachment property
- If there is an attachment property added to the definition of a user, then whenever anybody tries to register themselves as a new user, the user registration page fails to open, instead it gets immediately redirected to the login page.
- Issue: 4405
BUGFIX: Project Biskit subtypes are not applied when creating new biskits in v11
- If you define subtypes of project, then whenever you create a new project, you are asked which type of projject it should be.
- However, the project that is displayed and saved is always the top-level type of project.
- This means, for example, that any custom properties added to the subtype of project the user selected would not be displayed or saved.
- Issue: 4407
BUGFIX: Uploading a file that is larger than the max file upload size results in browser appearing to hang
- If you upload a file that is larger than the maximum size of file that is allowed (according to system settings), then the UI appears to just hang.
- The file upload fails immediately, but you just don’t get an error telling you this, and the UI doesn’t clean up by removing the in-progress file from the display.
- Issue: 4410
BUGFIX: Total time booked rule gives exception when limits are applied across all time and time masks are in use
- Suppose you create a total time booked rule such that:
  - On the “Rule” Tab, you set “Applies” to be “In Total”
  - You tick “Show advanced settings”
  - On the “Booking time to include” tab, you tick “Specify times to include in count”
  - You create at least one item on the calendar on the “Booking time to include” tab
- Then when you make a booking that the rule would apply to, it fails and generates an exception.
- Issue: 4411
BUGFIX: Total Time Booked Rule shows bogus error message when acceptable booking time used
- When you create a total time booked rule, you can set a custom message.
- It comes with placeholders that will be replaced with the total number of hours and minutes that were actually used, so you can have a message read something like:
  
  “You used 5 hours and 30 minutes for this project, but there is a limit of 4 hours”
- When the total time booked rule finds zero time is used, then the error message for the rule would be displayed. But where there are placeholders for the amount of time used, they are NOT replaced by the actual time used (zero), but left as placeholders.
- This makes for a weird message displayed to the user, which is displayed as a disappearing blue info box in the bottom right corner.
- The same is true when it finds there is some time used, but within the acceptable use. This is different code, but with the same problem.
- In both cases, the rule should and does accept the booking, but still generates an error message, and one which is not formatted correctly.
- It no longer shows an error message in these circumstances.
- Issue: 4412

1.53 11.5.52 June 13, 2025

Changes

Add support for system setting to allow file upload before user is registered
- When a new user registers themselves to request an account, they are offered a form including most of the properties on a user.
- If there is a property that stores a file attachment, then this will let them upload a file.
- By default, we now prevent file uploads before a user has logged in. This is what we refer to as an anonymous file upload because at the time the user is registering themselves as a user, we don’t know who they are.
- You may or may not require that users be able to upload a file at the time they register themselves as a user, and there is now a system setting to allow the choice to be made.
- This is on the “Security” tab, and is referred to as allowing anonymous file uploads.
- This is disabled by default so that users registering themselves are not allowed to upload a file.
- Issue: 4406
Provide indication of why session cookies do not work when they are broken
- With a server misconfiguration, it is possible that the JSESSIONID cookie is not visible to the browser. This cookie is used when files are uploaded from the browser. If there is a problem with the cookie, then some things don’t work as well. For example, if you try to upload a file that is larger than the maximum allowed size, then the user may not be told because it is possible the browser cannot work out that this is the problem.
- The principle reason for this going wrong is that the server has a context path at which the application is found, and this path is stored on the returned cookie header. If that path does not match the path used by the browser, then the cookie will be hidden from the application by the browser.
- These paths can mismatch when there is a reverse proxy (such as Apache HTTP server) that rewrites the paths. In this case, it would be necessary to rewrite the cookie paths as well, using a ProxyPassReverseCookiePath directive in Apache. Without it, the change of paths causes the cookie to be hidden.
- When a file upload is performed for the first time in a browser session, this problem is detected. The browser now logs a message to indicate the server and client context path along with a suggestion for a server configuration change that might fix the problem.
- Issue: 4414

Bug Fixes

BUGFIX: Default database workflow events on new system do not have an update phase set on database events
- When a new virgin database is created, it comes with some default workflows that send emails when a user registers and other things relating to the user lifecycle.
- None of the DatabaseWorkflowEvents created have a “Database Update Phase” set on them, and this is a required part of dtabase events.
- This means they don’t run at all.
- New systems created from now on will have this set correctly, and any pre-existing systems which have a DatabaseWorkflowEvents without a “Database Update Phase” set on them will automatically have it set to “After transaction”.
- Issue: 4373
BUGFIX: Report columns “lastRepeat.start” and “lastRepeat.finish” are not deleted in upgrading to 11.0 and so give errors
- The lastRepeat property was removed in 11.0 from Booking and Template, and there was a database upgrade in 11.0.5 to remove columns in reports that referenced lastRepeat.
- However, it was written in such a way that it missed any column lastRepeat.foo for some pseudo-property of lastRepeat.
- For example, a report that references lastRepeat.start or lastRepeat.finish or lastRepeat.start.year etc would not be deleted.
- This means that after upgrade, it would still have a column referencing lastRepeat, and cause an error when such a report was run.
- These columns are now automatically removed.
- Issue: 4401
BUGFIX: User registration page doesn’t load if there is an attachment property
- If there is an attachment property added to the definition of a user, then whenever anybody tries to register themselves as a new user, the user registration page fails to open, instead it gets immediately redirected to the login page.
- Issue: 4405
BUGFIX: Project Biskit subtypes are not applied when creating new biskits in v11
- If you define subtypes of project, then whenever you create a new project, you are asked which type of projject it should be.
- However, the project that is displayed and saved is always the top-level type of project.
- This means, for example, that any custom properties added to the subtype of project the user selected would not be displayed or saved.
- Issue: 4407
BUGFIX: Uploading a file that is larger than the max file upload size results in browser appearing to hang
- If you upload a file that is larger than the maximum size of file that is allowed (according to system settings), then the UI appears to just hang.
- The file upload fails immediately, but you just don’t get an error telling you this, and the UI doesn’t clean up by removing the in-progress file from the display.
- Issue: 4410
BUGFIX: Total time booked rule gives exception when limits are applied across all time and time masks are in use
- Suppose you create a total time booked rule such that:
  - On the “Rule” Tab, you set “Applies” to be “In Total”
  - You tick “Show advanced settings”
  - On the “Booking time to include” tab, you tick “Specify times to include in count”
  - You create at least one item on the calendar on the “Booking time to include” tab
- Then when you make a booking that the rule would apply to, it fails and generates an exception.
- Issue: 4411
BUGFIX: Total Time Booked Rule shows bogus error message when acceptable booking time used
- When you create a total time booked rule, you can set a custom message.
- It comes with placeholders that will be replaced with the total number of hours and minutes that were actually used, so you can have a message read something like:
  
  “You used 5 hours and 30 minutes for this project, but there is a limit of 4 hours”
- When the total time booked rule finds zero time is used, then the error message for the rule would be displayed. But where there are placeholders for the amount of time used, they are NOT replaced by the actual time used (zero), but left as placeholders.
- This makes for a weird message displayed to the user, which is displayed as a disappearing blue info box in the bottom right corner.
- The same is true when it finds there is some time used, but within the acceptable use. This is different code, but with the same problem.
- In both cases, the rule should and does accept the booking, but still generates an error message, and one which is not formatted correctly.
- It no longer shows an error message in these circumstances.
- Issue: 4412
BUGFIX: Enterprise imports fail if some referenced provided biskits not directly exported
- Some imports from one Enterprise shard to another fail when a biskit that is required is present nested within the data received, but not listed as a top-level biskit that should be created by the import.
- This has been observed for attachments within an attachment set.
- These are now automatically managed to avoid the problem.
- Issue: 4438

1.54 11.5.53 August 7, 2025

Bug Fixes

BUGFIX: Enterprise import of workflow can fail
- This is a bug introduced in 11.5.52 as a part of the fix to issue 4438 “Enterprise imports fail if some referenced provided biskits not directly exported”
- When exporting a workflow to another shard, you could receive an error telling you there was an error like this:
```
A different object with the same identifier value was already associated with the session : [BiskitCreateOrUpdateWorkflowActionItem#872880787175425]
```
- This was a problem with trying to do a double import of the workflow by mistake.
- Issue: 4492
BUGFIX: CSV Importing to update “Base Project” can give shallow exception
- If you do a CSV import to update a project, but you specify that it’s a “Base Project” that you want to update instead, then you end up getting a ShallowException.
- Issue: 4494

1.55 11.5.54 September 18, 2025

Changes

Warn user when search for bookings on general search page will not handle repeats properly
- There are some circumstances where the general search page, found on the menu as Search->Search and then selecting Bookings, could produce incorrect results without the user being aware.
- If you use a include-times-between condition, which will be provided by default, then it will work.
- But if you remove that, then it won’t find all repeat instances.
- If the conditions you add do not provide a fixed range of dates that the returned bookings must be within, then it will now warn you, and suggest that you use the booking search page instead of the general search page, or to add a condition on the booking’s dateRange property with an includes-time-between relation.
- Issue: 3910
Add min and max DB connections to system event for source “ExprodoServiceImpl” and category “Boot”
- Issue: 4443
Record the number of DB connections in use in system status
- The number of database connections is now recorded in the SystemStatus biskit.
- One of these is recorded every 15 minutes to capture information like the amount of memory in use, and now the number of database connections in use.
- Issue: 4444
Make error messages clearer when making booking for bad project
- The error message “You can only choose one of your own projects” sometimes happens when a booking is made for a project that is not related to the user trying to make the booking.
- The regular user interface should prevent such a thing.
- However, a workflow may create an erroneously configured booking that can lead to this message.
- When this happens, it can be confusing what’s happening.
- In particular, there are two errors that can be conflated. “You can only choose one of your own projects”
- and “You must choose a project configured to use [ResourceName]”
- To help make clear what the problem is, and to make the above two harder to conflate, they now contain more information about the problem.
- Issue: 4448
Allow rule editor to display if user has permission to READ rule
- The rule editor did not allow itself to display if the user did not have permission to create or update rules.
- This is now extended so that the rule editor is also accessible if the user has permission to read rules.
- Issue: 4477
Make all biskit_defs and property_defs columns use ascii char set and related collation where appropriate
- This is an addendum to a change made in 11.0.9 where many columns had their character set converted to ASCII and related collation. This was for columns that stored a biskit type.
- However, this did not include the tables biskit_defs and property_defs that each have multiple columns that should receive the same treatment.
- Nobody should notice the change, but it’s an added protection to ensure the affected columns cannot contain accented characters where none should exist.
- Issue: 4490
Add “System Status” node to bakery tools
- There’s a problem seen sometimes in 11.0 whereby updating the DB schema or reloading DB config in the bakery does not work.
- This was addressed, to some extent, in issue 4442: “System locks up if try to update DB schema with insufficient DB conns”
- The solution was to prevent the lock up by showing an error message when there were insufficient free database connections to use.
- While this was better, it did not address the underlying problem of running out.
- While we could increase the number of connections, it would be preferable to identify why and when we use too many.
- So this change adds a tool in the bakery to tell you how many connections are in use, as well as the maximum number of connections and the amount of memory in use by the server. This should help identify the underlying problem.
- Issue: 4508

Bug Fixes

BUGFIX: Unable to define subroutine using an interface
- If you create a workflow, add a “Define Interface” action with at least one input or output, and then add a “Define Subroutine” configured to use the previously created interface, then you cannot save the workflow.
- This gives an error: “Multiple representations of the same entity…are being merged”
- Issue: 3759
BUGFIX: Edit repeat bookings all-items or this-and-later ignores bookings in the past
- Only bookings that are in the future would be affected.
- We now allow changes to historical bookings, so long as the resource indicates historical changes are allowed.
- Issue: 3884
BUGFIX: Exception when update properties on repeat bookings other than dates all-items or this-and-later
- The exception only happens depending on how permissions are configured
- Issue: 3885
BUGFIX: Edit description of single instance of repeat booking in a list updates all repeat instances
- From any search page where you have a list of bookings, use checked-editing to edit the description of one of a repeating sequence, and all instances are changed without you being asked whether you’d like the change to apply this-item, this-and-later or all-items.
- Issue: 3912
BUGFIX: Deleting repeat bookings can break repeats
- Generally, bookings should not be deleted, but should be cancelled instead if they are not wanted.
- The bookings calendar does not provide a mechanism to delete, only to cancel.
- But if you go to a search page to search for bookings, then it does allow you to delete bookings.
- If you delete an instance of a repeat booking from a search page, then this can cause problems. It would not ask you, like the bookings calendar does, whether you want to apply the change all-items, this-and-later or this-item.
- To explain why it is a problem, there are three cases to consider:
  - The instance you clicked on is the last of the repeating sequence that has been expanded in the database. This is known as the last of the “non-ephemeral” bookings. In this case, a simple delete breaks the repeat because the repeat holds a reference to the ID number of the last non-ephemeral, and it is used as a template for future expansion. If it is deleted, then the future expansion cannot function properly.
  - The instance you clicked on was an ephemeral booking. Then the concept of deleting it is spurious because it does not exist in the database, and the last non-ephemeral would have been used to generate the ephemeral on-the-fly. So the system sees the ephemeral booking as having the same ID number as the last non-ephemeral booking, and so it’s the last non-ephemeral that gets deleted, and the repeat is broken as described above.
  - The instance you clicked is not ephemeral, and it’s not the last non-ephemeral. In this case, deleting it would cause no problems.
- We now do ask which repeat instances it should be applied to, and we handle it as a cancellation and not a delete.
- Issue: 3922
BUGFIX: Reports looking for ephemeral bookings always return nothing
- Repeat bookings may repeat forever, and therefore have an infinite number of repeating instances.
- We expand the repeats only so far into the future (90 days by default), and thereafter anything shown on the calendar is generated on-the-fly from the last of the repeating instances that have been expanded in the database.
- These generated instances that aren’t stored in the database are known as ephemeral.
- There is an “ephemeral” property on Booking so that you can see which ones are stored in the database and which ones are generated.
- If you create a report and choose conditions to show only ephemeral bookings, then the report would always return nothing.
- This is because the database only contains non-ephemeral bookings (by definition) and we were applying all the conditions to the database search, and only then expanding repeats.
- This is now handled better so that if you search for ephemeral bookings, it will find any that it should.
- Issue: 3993
BUGFIX: Convert annually repeating booking to monthly repeating mishandles cancellation reasons
- Suppose you create an annually repeating booking that repeats forever on a resource that requires cancellation reasons to be provided.
- Then you edit the booking, and change it to repeating monthly by day and save it.
- Then the save fails with an error message that says you must provide a cancellation reason - even though you were never given the opportunity to provide one.
- The mechanism that detects whether we should ask for a cancellation reason did not always correctly identify when a repeating instance would need to be cancelled. In the case of changing from annually repeating to monthly repeating, the instance that needs cancelling might be a long way into the future, and that wasn’t spotted.
- Issue: 4103
BUGFIX: Property “Project.visits” is reserved for CTMS but not prohibited outside CTMS
- Calpendo includes an optional module called CTMS. This provides support for clinical trials, where it can track all the visits a subject has, and the tasks that must be performed on those visits, as well as all things that need to be booked for those visits and tasks.
- When the CTMS module is loaded, it creates a property called “visits” on Project.
- This means Project.visits is a special property that is reserved for CTMS.
- If you try to add a property called “visits” to Project on a Calpendo without the CTMS module loaded, then it would silently allow you to do it, but it then would not work properly because of its special nature.
- There is now an error generated if you add such a property that prevents you from adding the Project.visits property.
- Issue: 4204
BUGFIX: Attachment broken when copy to clipboard between booking definitions
- Suppose you have two BiskitDefs that represent subtypes of Booking, and they both have their own attachment property that happens to have the same name.
- Then when you copy a booking from one, and paste it to a resource that uses the other booking BiskitDef, the new booking appears to have been created properly.
- However, the attachment on the new booking cannot be downloaded. You get a permission denied error, and a system event is created with the message:
```
Permission denied trying to download attachment [PK], name
'[FILENAME]' due to referee type being inconsistent with the
PropertyDef's owning BiskitDef
```
- Issue: 4434
BUGFIX: The return value is not being set correctly by the ’if()" builtin workflow function
- The return value from the “if” workflow function would be on a property that had the name “value1” or “value2”, whereas it should have the name “value”.
- This meant the result was not where it should be, and other actions might not be able to locate the result.
- Issue: 4437
BUGFIX: Upgrading from 10.1.x to 11.0 fails without database_upgrades table
- If you take a dump of the database and exclude the database_upgrades table, and then you try to upgrade from 10.1.x to 11.0, it cannot cope with the missing table, and the upgrade fails.
- Issue: 4439
BUGFIX: Licence exception if it’s missing an expected property
- If there is a property defined for the licence biskit, but there is no such property in the source code for the biskit itself, then when populating the licence from the licence key, we get an exception on boot.
- This was observed as a result of issue 4439 “Upgrading from 10.1.x to 11.0 fails without database_upgrades table”.
- Issue: 4440
BUGFIX: RepeatableHandler can’t expand old bookings if changing old prohibited
- When upgrading to 11.0, the upgrade can leave some repeat bookings that are entirely in the past.
- After Calpendo boots, it would then be expected to convert expand those historical repeats to enumerate the repeat instances up to 90 days from now.
- However, if the resource is configured to prevent changes to old bookings, then that means the expansion is prevented from happening, and you see lots of errors in the log and system events as a result.
- Issue: 4441
BUGFIX: System locks up if try to update DB schema with insufficient DB conns
- The file hibernate.cfg.xml in the Calpendo distribution lets you specify (amongst other things) the minimum and maximum number of database connections.
- This is in properties:
  - hibernate.c3p0.min_size
  - hibernate.c3p0.max_size
- The default for these is 5 and 20 respectively.
- When the server is busy with users making requests, the number of connections will go up, and will be limited by whatever the maximum is.
- For a busy server, 20 connections may not be enough and you may run out.
- When somebody updates the DB schema, it creates a whole new set of database connections. That means you get the minimum (5) connections added to the existing connections.
- After the schema update script has been generated, those extra connections (5) are discarded.
- When somebody reloads the DB config, it creates a whole new set of database connections (another 5). After the reload is complete, the new connections are retained, and the older connections are closed.
- In both cases, it means that if there happen to be 16 or more connections in use at the time of trying to either update the db schema or reload the db config, then it will fail because it won’t be able to get the full set of 5 connections required.
- We now check for the current number of database connections, and the number required, and avoid updating the database schema or reload the database configuration if there will not be enough, and tell the user what the problem is.
- Issue: 4442
BUGFIX: System events show format in tab called “Event Border”
- Some systems display a tab called “Event Border” in every system event on the system events page.
- This was an error introduced in the upgrade from 9.0 to 10.0.
- There should be no such tab, and its contents should be in the main table of properties.
- Issue: 4445
BUGFIX: Trigger column in history showed wide even when nothing in there
- The history page and history info from any biskit would show a table with a column for the workflow trigger which caused the change.
- Even if there were no workflow triggers that ever modified the biskit, so the column was always empty, then it would show with a width of 400 pixels.
- This is much more than required for the title and the default content which is to show “Nothing selected”.
- This has now been reduced to 100 pixels.
- Issue: 4446
BUGFIX: Attachment download hyperlinks show URL with unformatted ID
- When you click on a property that is a hyperlink to a file attachment, then the URL it uses includes the ID number of the attachment.
- This was used unformatted, whereas we now try to format all ID numbers to make them more human readable.
- Attachments could always be displayed, but now the URL is slightly friendlier.
- Issue: 4447
BUGFIX: CAR/pGina workflows cannot create ResourceUsage with project
- When using CAR or pGina to send actual usage information to Calpendo, things are handled slightly differently in 11.0.
- It means that an internal system user runs any workflow that turns the low level actual usage information into ResourceUsage instances.
- This was causing a problem whereby it would think the user was creating a record for a project they were not related to.
- Issue: 4449
BUGFIX: Can’t find references to a MappedInt/MappedString stored in some workflow actions
- Suppose you create a workflow with a CustomFunction that takes an argument that is a MappedInt or a MappedString.
- Or suppose you create a workflow with a CreateVariables that has a variable that stores an instance of a particular MappedInt or MappedString.
- Then when you go to the bakery and select the MappedInt or MappedString referenced by the workflow, and click the References button, it will not find the reference in the workflow.
- The same can happen from workflow actions CreateBiskitDef, DefineConstants and DefineInterface.
- Issue: 4450
BUGFIX: Summary report sorts pseudo date columns badly when row present
- Suppose you have a summary report where you add a pseudo date property to the column (for example, weekOfYear), and you add something else (anything) for the row.
- Then the columns are sorted by string ordering rather than numerical ordering. This means “10” comes before “9”, for example.
- Issue: 4452
BUGFIX: Virgin Calpendo database is built with conditions tables having null owner_id
- There are many tables in the database that store conditions.
- Each of these tables has a column called owner_id that stores a reference back to the biskit that the condition belongs to.
- Every row in these conditions tables should have a non-null value in the owner_id column.
- However, when you create a new Calpendo database, there are two rules created by default, and their conditions have a null value in the owner_id column.
- The rules are “Double Bookings” and “Predefined slots must be adhered to”.
- The tables rule_conditions, rule_ignore_conditions, rule_not_apply_conditions and rule_tally_conditions all have rows with a null owner_id are affected by this.
- Issue: 4455
BUGFIX: Bakery’s “find references” ignores properties in Resource tooltip
- When your mouse pointer hovers over a booking in the calendar, it will show a “tooltip” with some details about the booking. This can be customised, with each resource specifying what the tooltip should contain for its bookings.
- A booking resource’s tooltip can reference the value of any property on the booking, but when you search for references to the property from the bakery, it does not find anything that referenced it from a resource’s booking tooltip definition.
- Issue: 4456
BUGFIX: Cancellation reason popup text nonsensical when not asking for cancel
- When you cancel a booking for a resource that requires cancellation reasons, then you get shown a pop-up that lets you specify the reason.
- The text used on that popup for the title, the message in the popup and the button labels all make sense.
- However, sometimes, you might modify a booking in such a way that it requires something to be cancelled even though you didn’t directly ask for a cancellation.
- For example, if you have a daily repeating booking and convert it to something that repeats every Monday, then the bookings that are not on Mondays will need to be cancelled.
- From the user’s perspective, when the popup asking for a cancellation reason appears, it doesn’t really make sense to have a popup with a title of “Cancelling Booking”, and buttons “Cancel booking” and “Do not cancel booking” when they changes the type of repeat from daily to weekly.
- So the pop-up asking for a cancellation reason now contains different text when the user did not directly ask for a cancellation, and the buttons contain different text as well.
- Issue: 4457
BUGFIX: New user self-registering does not receive email notification
- When a user registers themselves as a new user, then there is usually a workflow that should send them an email to let them know we have received their request.
- However, that email would not be sent.
- Also, there would also be an entry in the audit log to indicate that the user was created. The audit log entry should say that the user created their own user, but it would instead say that it was created by the system user.
- They should now receive the email, and the audit log says they created the user themselves.
- Issue: 4458
BUGFIX: Save/cancel buttons made inaccessible when pasting nodes in Menu Editor
- When you copy and then paste menu items into a menu using the menu editor, then this can cause the page to scroll in such a way that the buttons at the top of the page become inaccessible.
- Issue: 4459
BUGFIX: Export button on Workflow manager page sometimes disappears
- Following a log out and log in, the “Export” button on a workflow does not display, with a browser refresh being needed to bring it back.
- Issue: 4460
BUGFIX: Menu editor shows odd scrollbar sizing when switching from read to edit mode
- When you edit a menu in the menu editor, then sometimes the scrollbar shown in the pane that lists all the menu items is completely the wrong height for the content that is there. It looks like the system thinks there’s much more content there than there is.
- Issue: 4464
BUGFIX: Workflow Export fails if the workflow includes a Sort Action
- If a workflow contains a Sort action, then an attempt to export the workflow to SQL (to facilitate copying to another system) generates an exception.
- Issue: 4466
BUGFIX: Changing project default name to empty string fails
- There’s a “Default Project Name” you can set in System Settings. This is used as the default name when you create a new project.
- If you edit system settings and set the project’s default name to the empty string and save it, then the UI appears to have done so. However, refresh the page and you see it is set to the default value of “Enter project name”.
- This now works properly.
- If you also set a placeholder for the name property of a project in the bakery, then when you create a new project, the placeholder text will be shown while the project name is empty, and disappear as soon as you start typing.
- Issue: 4467
BUGFIX: Cancel repeat booking this-and-later required permission to update the repeat
- If you cancel a repeat booking this-and-later, then this would require a change to the repeat biskit itself because the repeat stores the date when the repeating stops, and not the booking.
- This requires a permission to edit the repeat itself, and we don’t generally have such permissions since nobody should change repeat biskits directly.
- So now it checks the change to the booking is good, but when cancelling like this, it does not check permission to modify the repeat.
- Issue: 4475
BUGFIX: Error message “cannot change the date of booking that repeats” is misleading
- When you try to change the date of a booking that repeats weekly, you would get a message that said: “You cannot change the date of a booking that repeats weekly”
- But this implies that you can change the date of a booking that repeats a different way, which is untrue.
- So the message now reads “You cannot change the date of a booking that repeats” without specifying the type of repeat.
- Issue: 4476
BUGFIX: Inverse property setting can be lost when editing something else in the bakery
- Suppose you edit the definition of Calpendo.Project in the bakery, and select the “owner” property. Then you should see that the inverse property name is “projectsOwned”.
- If you then click on the “status” property, and then back to the “owner” property, you then see that the inverse property name is now unset.
- If you were to save it, then the inverse property name would be removed.
- Issue: 4478
BUGFIX: Calendar drag selection would include unintended time slots
- When time slots are configured on the calendar, dragging your mouse from start to finish time could yield a booking of the wrong time range when the start or finish exactly matches the boundary of a time slot that should be excluded.
- Issue: 4479
BUGFIX: Workflow “Create Copy” fails to save if the workflow includes Constants
- If a Workflow includes both a Define Constants Action and a Get Constants Action then it is not possible to perform a “Create Copy” and a “Save” of that Workflow because an error.
- The error message is something like: Shallow property: DefineConstantsWorkflowAction#20250702.130213.13.1.children
- Issue: 4480
BUGFIX: Provide better error message when using old format of updateProperties request
- If an old client sends a request to version 11.0.17.1 or 11.0.17.2, then it would receive an exception with an unhelpful message.
- It now provides a better message.
- Issue: 4483
BUGFIX: UI displays error when change linked booking child start/finish
- If you click on a booking that is a child of a linked booking parent in the calendar and edit the times, and it’s a link configured to not allow children to change their times, then you get an error saying there’s a Shallow Exception.
- Issue: 4484
BUGFIX: Go to resource editor without resource selected sends redundant request to server
- When you change page to the Resource Editor, it can sometimes send a request to the server asking it for details of a biskit with type null and id zero.
- This doesn’t cause any harm, but it should not have made the request.
- Issue: 4486
BUGFIX: Deleting a repeat booking THIS-ITEM fails if don’t require reason
- When a resource is configured to not require cancellation reasons, and you cancel a repeat instance from a list of bookings, then you get an exception.
- Issue: 4487
BUGFIX: Error accessing Requirements in Menu Editor
- Attempting to view the menu items under Help > Requirements in the menu editor gives an exception.
- Issue: 4499
BUGFIX: Editing description of a repeat booking instance updates the entire repeat booking sequence
- This relates to issue 3912, fixed in v11.0.17, but that issue applies specifically to using checked-editing of bookings.
- This issue is about what happens when you use the booking search page to locate an instance of a repeat booking, click on the booking to show a booking pop-up, and then edit it.
- It would not ask you whether you wanted the change to apply this-item, this-and-later or all-items, and instead would assume all-items.
- It will now ask which of the repeating instances should be affected.
- Issue: 4503
BUGFIX: Projects without projectCode ignored when checking licence limits
- A Calpendo licence can limit the number of projects.
- However, when creating or updating a project, it would only check if the number of projects had gone too high if the project that has just been created or updated had a projectCode set on it.
- Issue: 4505
BUGFIX: Switching between report menu items does not update displayed report
- When you have multiple menu items that run predefined reports, it is sometimes the case that clicking on one of those menu items shows a report correctly, but then clicking on the other one does not update the displayed report.
- Issue: 4507
BUGFIX: Updating booking can result in a JSON error with too many nested levels of data
- When data structures are especially complex, then updating bookings could fail due to limits employed to the depth of nesting data within JSON.
- Issue: 4509
BUGFIX: Bakery database analysis tool to delete unwanted or bad foreign key constraints does not work
- The bakery has a tool built in that allows for unwanted or incorrectly defined foreign key constraints to be removed.
- This is only available for root users.
- However, using it to delete a foreign key constraint was returning an error instead of working properly.
- Issue: 4510
BUGFIX: Error shown when deleting a booking for a resource that does not require cancellation reasons
- If you go to a booking search, and tick the check box next to any repeat booking and click the “Delete” button, then this would generate an erro:
  
  Cannot read properties of null (reading ‘a’) is prompted
- Issue: 4511
BUGFIX: Menu item to run predefined report doesn’t allow search bar hiding and doesn’t remain on selected token
- In the menu editor, you can add a custom page that will run a predefined report.
- There’s an option in there to hide the report page’s search bar.
- This will hide the File button, the Search for drop-down, the report type drop down, the conditions button etc.
- This works perfectly for any report created from the Search->Search page, but it doesn’t work for any report created from any other search page.
- So if you create a report from the Booking Search page, and then create a menu item that shows that report and asks to hide the search bar, it does not work. The search bar will not hide.
- This same issue has another symptom. In the menu editor, you assign a “token” for the menu item for all menu items of type “custom page”.
- This is what appears after the “#” in the address bar when you select that menu item.
- When you run a menu item that runs a predefined report for a Search->Search report, then the address bar shows the token you selected after the “#”.
- However, for a report created from another page (such as the booking search page), the URL initially shows the token you entered, and then immediately changes to the URL for the report. Eg it might show something like “#bookingSearch&id=20250821.154255.0.1&autorun=true”
- Issue: 4512
BUGFIX: Updating DB schema sometimes fails randomly with multiple updates
- After making changes in the bakery, one must click the “Update DB Schema” button to general the SQL required to modify the database to account for the changes.
- You then click the Apply button to have that SQL executed.
- When the server then executes that SQL, it will first regenerate the SQL and compare the SQL to what it found the first time. If it has changed, then it won’t run it.
- It’s a a fairly straight-forward test to make sure nothing important has changed since the SQL was shown to the user.
- There’s a fundamental assumption made here, which is that the SQL that is generated will always be identical when nothing has changed.
- However, this assumption is faulty. When you make multiple changes, then the SQL contains multiple lines of code, and it is possible that the server will generate those lines in a different order each time.
- This means it would sometimes think the SQL has changed, when it hasn’t really, it’s just generated them in a different order.
- The test for whether the SQL has changed now checks that the same lines exist without a requirement that they be in the same order.
- Issue: 4519
BUGFIX: Booking reports find nothing with custom date conditions that limit the result to ephemeral instances
- When you search for bookings, then by default we generate conditions including something that says “dateRange includes time between A and B” where A and B are dates that you would select.
- If you don’t use an includes-time-between relation, then it’s actually quite difficult to get the conditions right so that they tell you about all repeat instances because the actual conditions required are complex. For more complex than one would generally think.
- An example of this would be if you search for bookings with conditions that look like this, where A and B are dates:
  
  dateRange.start no earlier than A dateRange.start no later than B
- This looks like it should return bookings between A and B, and it will do that to some extent. But it won’t always return all the repeat bookings you would expect.
- In some cases, if A and B are far enough into the future (more than about 90 days by default), then the report would find no repeat bookings at all, even when there are some that it looks like it should find.
- Calpendo will now do a better job of identifying this situation and returning instances of repeats between those dates.
- However, it’s always recommended to avoid this by using an includes-time-between relation because it is designed to cover all the edge cases with how repeats and multi-day bookings work.
- Issue: 4521
BUGFIX: Updating a repeat booking via workflow action affects all repeat items
- When a workflow modifies a repeat booking, then the changes were applied to every instance of the booking in the repeat sequence.
- It now applies only to the particular instance being modified, which is equivalent to choosing “This Item” in the user interface when you edit a repeat booking.
- Issue: 4524
BUGFIX: Error shown when exporting a workflow to SQL that contains a custom function defined with inputs or outputs
- If you have a workflow which a CustomFunctionAction, and click the Export button to generate a SQL file with the contents of the workflow, then you get an error.
- Issue: 4527
BUGFIX: Errors in workflow manager when custom function has mapped int arg with no mapped int
- If you have a custom function in a workflow, which has an argument taking a MappedInt, but that does not specify which Mapped Int it should be, then workflow manager will show an error relating to the custom function at various times.
- This is similar to issue 4351, fixed in 11.0.13, which was the same scenario but more severe consequences. We now handle the situation gracefully.
- Issue: 4528
BUGFIX: Cancel booking when no reason is required and reason is set to -1
- When a booking is cancelled, Calpendo can ask why it was cancelled.
- This happens depending on whether the resource indicates that it requires reasons for cancellation to be captured.
- This involves two items: some text explanation, together with a value selected from a drop-down.
- The drop-down causes an integer to be stored in the database, and this is from the “Cancellation Reason” MappedInteger in the bakery.
- If a resource does not require cancellation reasons, then the pop-up asking for a reason does not appear, and the reason number is set to -1.
- This can be confusing if somebody has configured a text string to be associated with the number -1.
- So we now store a null value for the reason when a booking is cancelled for a resource that does not require cancellation reasons.
- Issue: 4531
BUGFIX: Booking pop-up can show “null” in some names in the owner drop-down
- Sometimes, depending on configuration, it is possible that when you click in the bookings calendar to create a booking, some of the user names shown in the owner drop-down start with “null” where there should be the user’s login name.
- Issue: 4532
BUGFIX: Cannot update DB schema or reload DB config if not enough database connections are available
- This is an extension of a fix in 11.0.16 for what happens when you try to update the database schema or reload the database configuration in the bakery, and there aren’t enough database connections free to use.
- Before 11.0.16, this would result in locking up the system so it couldn’t be used.
- In 11.0.16, we would detect the problem and refuse to try and update the DB schema or reload the DB config to protect against the problem.
- But now, we release any database connections that are not actively being used when there are not enough free connections. Only after doing that and still finding there are not enough free connections would we then refuse to do the update DB schema or reload the DB config.
- Further, we have now reduced the minimum number of database connections that are created when opening a connection to the database from 5 to 2 to make it less likely there will be insufficient connections free.
- For those hosting their own Calpendo, we now recommend modifying your hibernate.cfg.xml file inline with this change. That means changing the value for hibernate.c3p0.min_size from 5 to 2.
- Issue: 4533