Title: Release Notes For Version 10.1.43

0.1 Table Of Contents

• Releases
  • 10.1.25 June 23, 2022
  • 10.1.26 June 24, 2022
  • 10.1.27 July 8, 2022
  • 10.1.28 July 27, 2022
  • 10.1.29 (no date)
  • 10.1.30 September 8, 2022
  • 10.1.31 September 14, 2022
  • 10.1.32 October 20, 2022
  • 10.1.33 January 4, 2023
  • 10.1.34 January 19, 2023
  • 10.1.35 February 20, 2023
  • 10.1.36 March 7, 2023
  • 10.1.37 March 22, 2023
  • 10.1.38 June 19, 2023
  • 10.1.39 August 29, 2023
  • 10.1.40 September 14, 2023
  • 10.1.41 December 20, 2023
  • 10.1.42 March 26, 2024
  • 10.1.43 February 10, 2025

1 Releases

1.1 10.1.25 June 23, 2022

Changes

• Automatically notice and fix problems with server cache

  • There have been some issues lately where a server cache that holds frequently accessed data, has been poisoned.

  • This happens when something that is correct at the time it was created is added to the cache, but later becomes inaccessible thereby making the cache broken.

  • While we have fixed errors that cause this problem, we now have a self-healing process in place that notices this situation, and causes the cache to be rebuilt.

  • The behaviour of the self-healing process can be modified using two flags.

  • In both cases, you would need to search for instances of Verbose (either in the general Search->Search page, or in the special

  • To allow problems found to be fixed, find and enable the Verbose instance with the name:

    com.springsolutions.exprodo.core.server.persistence.LiveCacheHealth:autoFix

  • This is enabled by default.

  • Normally, the server cache is checked every 30 minutes and, if there’s a problem, it will then fix it. Alternatively, you can modify the the period of the check to every minute by enabling the Verbose instance with the name:

    com.springsolutions.exprodo.core.server.persistence.LiveCacheHealth:highFrequencyChecks

  • Issue: 3414

Bug Fixes

• BUGFIX: CustomTreePage miscounts items when using multiple nesting levels

  • If you add a menu item to show a custom tree page, and you configure it to show dynamic nodes using two or more property paths to group biskits by, then the count displayed of the number of items would be wrong.

  • Issue: 2980

• BUGFIX: Select bookings calendar bookmark from menu shows exception

  • If you have a menu item that shows calendars by location, and from the template page, you select one of those calendars from the menu, then it takes you to the right page, but also showed an error in the corner of the screen briefly to say something went wrong on the server.

  • Issue: 3355

• BUGFIX: Create copy of biskit with one-to-many properties can give exception

  • Issue: 3368

• BUGFIX: Error if view old repeat booking where old changes not allowed

  • If you have a booking that is in the past, and which has repeat information set on it, and editing old bookings is disallowed, then viewing this booking in the search page pauses for some time and then gives an exception like “Maximum call stack size exceeded”.

  • Issue: 3371

• BUGFIX: Generate calendar invitation from workflow produces no invitation

  • If you use the workflow function createCalendarInvite to generate an iCal file, and add it into an email, then the email contains a message like:

    "Could not load data: Uploaded file cannot be found: JhGuja_RbdAfg-9v-444879784121345"

    instead of the appropriate content.

  • Issue: 3372

• BUGFIX: View user after creating bookings can give error

  • It was found when a user created a booking that also caused a linked booking to be created, and then if you go to a list of users and look at any user, it would give an error.

  • But this depended on the user performing these actions having limited permissions.

  • This bug is a consequence of a fix to an earlier bug (issue 3306) in 10.1.21.

  • Issue: 3398

• BUGFIX: Exceptions follow after workflow generated linked bookings

  • This bug would not affect most customers. It would be most likely to occur when there are many custom biskit types that have been created that reference users or projects or resources, or groups thereof, and when there are workflows that update anything referencing any of the above.

  • When the problem occurs, the actions it takes work without problem, but it “poisons” a cache held on the server so that it will generate errors at some later time when the poisoned part is used.

  • The poisoning happens through a deep data traversal and modification process of historical origin whose original purpose no longer exists.

  • Consequently, it has now been removed.

  • Issue: 3398,3412

• BUGFIX: Timed events creating biskit with auto-creator fail on update

  • Suppose:

    • you have a workflow that creates a biskit
    • that biskit has an automated property to record who created it
    • you have a workflow run by a timed event that creates such a biskit
    • after creating the biskit, the workflow assigns it as a value on another biskit

  • Then the update fails with an exception.

  • This was caused by an earlier optimisation in 10.1.21 (issue 3259) that made loading a user’s projects happen lazily.

  • Issue: 3400

• BUGFIX: Sort biskits by a string value and you can’t save default weight

  • If you create a Sort Workflow Action, and select a randomisation type of “Sorted”, and then choose a weight path that leads to a string property, then you should be able to set a default weight that is used whenever the weight found at the given path is null.

  • However, for string-valued properties, when you save the action, the default weight always defaults back to null.

  • Issue: 3401

• BUGFIX: Sort biskits by a string value that’s sometimes null gives exception

  • If you set up a workflow and have it sort a list of biskits, where the sorting is by a string valued property that is null for at least one of the biskits, then the action fails with an exception.

  • Issue: 3402

• BUGFIX: Iterate over double-map with FreeMarker gives an exception

  • If you have a workflow that includes a Map action, and it includes at least two keys, and then you feed that into a Templated Text action that uses FreeMarker to iterate over the the entries in the resulting map, then you get an exception.

  • Issue: 3403

• BUGFIX: Repeat bookings that slip into the past not being handled

  • Whenever a repeat booking’s time goes into the past, then something should come along (by default every hour) and create a non-repeat instance to represent what happened, and then modify the repeating instance to reset its start time to the next repeating instance.

  • This had stopped working, generating an exception with the message:

      "illegally attempted to associate a proxy with two open Sessions"

  • Issue: 3406,3359

• BUGFIX: Confirming booking when no changes are required gives exception

  • If you confirm a booking, and then (perhaps in another tab where you already had the booking displayed) you ask to confirm it again, then you get an exception the second time.

  • Issue: 3409

• BUGFIX: Exception when hover over booking in calendar to show tooltip

  • Displaying tooltip by hovering over booking in calendar can cause server data to get corrupted, resulting in exceptions.

  • As a bonus, fixing this has been done in such a way that makes it run much faster.

  • Depending on configuration, it could take a few seconds for the server to generate tooltip. Now it takes a fraction of a second in the cases tested.

  • Issue: 3412

1.2 10.1.26 June 24, 2022

Bug Fixes

• BUGFIX: Bookmark resource type filter shows wrongly formatted names

  • On the bookings calendar, if you click “Bookmarks” and then “Edit resources to display”, then it shows a pop-up where you can choose which resources should be displayed on the calendar.

  • To help filter what’s here, you can choose some resource types.

  • However, the names of the resource types were formatted incorrectly.

  • In a default configuration, you would not notice.

  • But if you changed the BiskitDef for Resource (not Resource Type) and made it use a name property other than “name”, or set a format that used name plus something else, then the resource type filter would try to display the names of the resource types using the Resource format.

  • Issue: 3407

1.3 10.1.27 July 8, 2022

Bug Fixes

• BUGFIX: Exception when workflow updates biskit with “updator” property set
  • When a workflow updates a biskit, it sometimes fails.
  • This happens when:
    • the biskit is configured in the bakery to automatically record who updated it last
    • the workflow is triggered by a user action
    • the user making the change does not have permission to make the change
    • the workflow is allowed (because it’s configured with strong enough roles to do so)
  • Issue: 3472

1.4 10.1.28 July 27, 2022

Security Fixes

• SECURITY FIX: Replace log4j 1.2.17 with real4j 1.2.22
  • There are some security issues with log4j 1.x.
  • These are not related to the log4shell problems with log4j 2.x, but log4j 1.x has its own issues.
  • Log4j 1.x will not be fixed. However, real4j is a project that forks log4j 1.2.17 and has fixed the issues.
  • So we now switch from log4j to real4j.
  • Issue: 3479

Bug Fixes

• BUGFIX: When one resource has bad URL for ical feed, none of them work

  • You can put a URL onto a resource so that it will import its bookings from that URL in ical format.

  • If you put in a malformed URL for one resource, then any resources with an iCal URL that happen to be processed later, would not have their bookings imported.

  • Issue: 3410

• BUGFIX: Repeat booking starts on wrong day if schedule today after now

  • If a daily repeat booking is created to start yesterday (at a time that is later than the current time of day today), then today’s booking is created as a non-repeat booking, where it should be the first of the sequence of repeats.

  • Issue: 3418

• BUGFIX: Day/week bookings calendar “colour by project” miscolours titles If you configure global preferences so that bookings display a title bar whose colour is indicated by the project, rather than the resource, then the colour displayed can change on refreshing the calendar so that the colours don’t always reflect the project colour.
  • Issue: 3458
• BUGFIX: FreeMarker templated text fails on map action entry keys

  • If you run a Map Workflow Action, and then use a FreeMarker-enabled Templates Text Workflow Action that expands the keys, then the result generates an exception.

  • Issue: 3461

• BUGFIX: A user event configured with a pop-up response ignores given title

  • When a workflow runs a User Workflow Event, it can configure a response that should be shown in a popup by:

    • Updating the event’s response to set the message and message type
    • Updating the event’s response’s popup to set the title and other attributes

  • However, whatever you specify for the title, it always shows as “Message”.

  • Issue: 3462

• BUGFIX: Property references do not include booking display flag conditions
  • Suppose you create a Booking Display Flag and add a condition that mentions some properyu ‘X’ on Booking
  • Then if you go to the bakery and search for references to that property ‘X’, it will not find the reference to it from the Booking Display Flag conditions
  • Issue: 3478

1.5 10.1.29 (no date)

Changes

• Add ‘echoArguments’ workflow function (for use in testing)

  • This is a workflow function that takes an argument of every PropertyType, and returns them all unchanged.

  • The function does nothing with them but return them.

  • This is intended for testing purposes only and is probably not of any other practical use.

  • This is here to help test the export of function action arguments of various types.

  • Issue: 3485,3486

Optimisations

• Optimisation: Clicking on project to display it is sometimes slow

  • When displaying a project, one of the things that happens is that each of the biskits it references must have a name calculated so that it can be displayed easily in the browser.

  • When you have a property that holds a file attachment, then Calpendo was loading the whole of the data contained in the attachment, even though it irrelevant to the name, which is stored as a separate property.

  • This optimisation improves things by loading only the necessary data when calculating the name of anything.

  • Issue: 3481

Bug Fixes

• BUGFIX: Re-saving custom search page report makes it load as general search

  • If you create a report from a custom search page (such as the booking search page) and add some conditions, and save it, then editing the report in the report manager generates this message:

      You have changed the conditions beyond the point where they will
      be recognised by the page that originally created them. This
      report will now be loaded by the general search page.

  • Loading the report no longer loads it into the custom search page it was created from, but the general search page, and the conditions show as much more complicated than the originals.

  • Issue: 3334

• BUGFIX: Repeat widget description doesn’t initially reflect correct date

  • Suppose you create a new booking from the calendar so that you’re on the booking form.

  • Then add a repeat. It can be of any type except ‘Daily’ for this bug. Suppose you choose “Monthly by Date”

  • Then repeat description will read “Repeat on the 1st of every month” regardless of the date of the booking.

  • For example if you created your booking on the 15th it should read: “Repeat on the 15th of every month”.

  • The other repeat types also have a similar effect not reflecting the initial date of the booking.

  • You can work around this by changing the start date or time of the booking date range and the repeat description will update itself to display the correct date.

  • Note that this bug is visual only. It does not affect the data that’s actually saved.

  • Issue: 3484

• BUGFIX: Workflow with function actions taking fixed values not exportable

  • Workflows can be exported to a SQL file so that they can be copied from one Calpendo to another.

  • A fix to issue 3461 in version 10.1.28 meant that some workflows could no longer be exported.

  • This affected any workflows containing a function action where at least one of the arguments to the function was specified as a “Fixed” value rather than “Variable” or “Null”.

  • Issue: 3485,3461

• BUGFIX: Repeat widget shows description for a different type of repeat

  • If you change the type of a repeat (eg from “Monthly by Day” to “Monthly by Date”) then the description sometimes shows the wrong content (describing a previous repeat type).

  • Note: this bug is visual only. It does not affect the data saved, only the way the repeat description is displayed while editing a booking.

  • Issue: 3488

• BUGFIX: Repeat widget sometimes shows description with end date when there is no end date

  • The description of a repeat booking can indicate the repeat has an end date when it does not.

  • To replicate this, create a booking, make it repeat and give the repeat an end date.

  • Then if you remove the end date, the repeat description still shows the old end date.

  • Note: this bug is visual only. It does not affect the data saved, only the way the repeat description is displayed while editing a booking.

  • Issue: 3489

• BUGFIX: You can’t change repeat start date back to it’s original date after changing it

  • If you create a booking and make it repeat “Monthly by Date”, “Monthly by Day” or “Annually”, then every time you change the booking start date, the description is only updated if you don’t choose the original start date.
  • Note: this bug is visual only. It does not affect the data saved, only the way the repeat description is displayed while editing a booking.
  • Issue: 3490

• BUGFIX: Shallow exception editing ServiceOrder with layout without autoNumber

  • If you add a layout for ServiceOrder, then any change to a ServiceOrder gives an exception about a shallow autoNumber.

  • Issue: 3491

• BUGFIX: Create a booking in the calendar and the history shows it was created by the system user

  • Issue: 3492

1.6 10.1.30 September 8, 2022

Bug Fixes

• BUGFIX: Saving large file on process update gives exception

  • Suppose you add an attachment property to a biskit and then create it via a process.

  • On the second stop in the process (so after having created it), add an attachment larger than 320KB in side, and save that step of the process.

  • This gives an exception, saying:

    "object references an unsaved transient instance 
      - save the transient instance before flushing: Attachment"

  • Issue: 3498

1.7 10.1.31 September 14, 2022

Bug Fixes

• BUGFIX: Workflow becomes uneditable if it includes a custom function with a JavaEnum argument
  • Suppose you create a workflow, add a Macro Workflow Event and add a custom function to it.
  • Then, add an input parameter to the function of type JavaEnum.
  • Select any of the types of JavaEnum available and give it a name.
  • Save the workflow.
  • Then whenever you try to view the workflow, or click on the Macro event of custom function, you get an exception complaining about a shallow property.
  • Issue: 3499

1.8 10.1.32 October 20, 2022

Changes

• Sort locations on the menu bar in alphabetically order

  • When you add a “Calendar By Location” page to the menu, then it generates submenu items for each defined resource location, with each menu item showing a calendar for the resources in that location.

  • These menu items were not always sorted by name, as one would expect.

  • Issue: 3514

Optimisations

• Optimisation: FreeMarker slow when dealing with users and projects

  • Suppose you have a workflow that runs a TemplatedText action, and the template accesses some property of a user (but not the projects or projectsOwned properties).

  • Then when the workflow runs, it will prepare the data from the user for consumption by FreeMarker, and this will include projects and projectsOwned - even if they are never accessed.

  • If these things are large, then this can mean a lot of work unnecessarily.

  • Issue: 3513

Security Fixes

• SECURITY FIX: Exceptions from automated requests keep session alive

  • If you view the bookings calendar, and leave your browser like that, then it will automatically refresh every now and then.

  • These automatic refreshes do not cause your session to be extended - that requires manual intervention so that your login session period is extended only when you are actually doing things.

  • However, if one of these automatic refreshes were to generate an exception, then that exception would be registered with the server, and that registration message could extend your session.

  • This has now been changed so that an exception generated from an automated request is itself treated as automated.

  • Issue: 3512

Bug Fixes

• BUGFIX: Exception message triggered switching to ‘no repeat’ type

  • Issue: 3502

• BUGFIX: Login download can include bookings (and so cannot log in if bookings table missing a column)

  • Suppose you set up this situation:

    • There is a biskit type X that has a property storing a Booking
    • Booking has a property storing an instance of X
    • X is marked as enumerable
    • One or more properties are added to Booking without clicking Update DB Schema so that the bookings table is missing at least one column
    • You click Reload DB Config
    • Then if there are any instances of X that reference a booking, you cannot log in

  • This scenario has been seen when setting up invoicing and having a Line Item that references a booking, and allowing a booking to reference a Line Item.

  • Issue: 3503

• BUGFIX: Exception running user workflow without awaiting outcome

  • If you create a user workflow event and configure a workflow button or menu to run it and not to await the result, then a Templated Text action will generate an exception.

  • Issue: 3507

• BUGFIX: First login after un-suspending user can fail

  • A user’s status can be “SUSPENDED”.
  • This means they are not counted towards the licensed number of users, but they can still log in.
  • When they do log in, then it means their status changes to “NORMAL”, and they do count towards your licensed number of users.
  • When a user that is suspended tries to log in, then that first login can fail, forcing them to refresh their browser to continue.
  • Issue: 3511

• BUGFIX: Menu-run workflow events never wait for completion even if told to

  • When you configure a menu item to run a workflow, there’s a setting where you can choose whether the UI will wait for the completion of the workflow.

  • Regardless of what you selected, it would not wait.

  • Issue: 3519

1.9 10.1.33 January 4, 2023

Bug Fixes

• BUGFIX: Select booking owner using mouse sometimes does not work

  • When there are more than 20 users to select from, selecting the user that is the owner of a booking using the mouse will sometimes result in the owner being unset.
  • Issue: 3420,3471

• BUGFIX: Copy/paste a templated text does not renumber freemarker loops

  • If you have a workflow that includes a TemplatedText action, then when you copy and paste something that includes it, then any references within the template to outputs from earlier actions may need renumbering to reference the new values.

  • This was not happening for FreeMarker loops. For example:

    <#list source290.biskits as biskit>
    </#list>

  • In this case, where this TemplatedText is inside an action #290, and that it copied elsewhere so its number changes, then the 290 inside the template should change in a corresponding manner.

  • Issue: 3475

• BUGFIX: Update newly created project fails with custom one-to-many prop

  • If you add a one-to-many property to Project, and then create a project and immediately edit and save that project, then the update fails with an exception.

  • Issue: 3483

• BUGFIX: Cannot set default value for automated property

  • If you mark a property as automated in the bakery, then the editor for the default value displays read-only.
  • If the property is string-valued, then a read-only version of the string means it looks like the editor has disappeared.
  • Issue: 3496

• BUGFIX: Trying to create a new theme gave an exception

  • Issue: 3501,3508

• BUGFIX: Exception on the calendar if the number of vertical pixels set to 1

  • You can choose the resolution of the calendar display, and one does this by setting a number of pixels that should be displayed for each 30 minute block.
  • If you were to set this to one, then it would result in an error complaining about a divide by zero.
  • Issue: 3504

• BUGFIX: ServiceOrder permission broken in recently loaded module

  • Issue: 3509

• BUGFIX: Some default Calpendo permissions are configured incorrectly

  • Issue: 3510

• BUGFIX: Condition on user “self member of” shows list of user not group

  • If you search for users, and add a condition of the form:

    self member of

  • then you should see a drop-down with a list of user groups so that the condition checks whether the user is in the selected user group.

  • However, it was instead showing a drop-down with a list of users, which makes no sense.

  • Issue: 3515

• BUGFIX: Hidden formulaic prop on child of one-to-many causes save exception

  • Suppose:
    • you have a one-to-many property from PARENT to many CHILD
    • CHILD.value is a formulaic property
    • CHILD.value is marked as not visible and not visible in biskit detail in the bakery
  • Then if you try to create an instance of PARENT, and add at least one CHILD to it, then the save yields an error message saying “ClassCastException”.
  • Issue: 3522

• BUGFIX: Exception viewing linked booking link if child resource is subtype

  • Suppose:
    • You create a subtype of resource
    • Create an instance of that resource
    • Add that resource as a child resource of a linked booking link
  • Then on viewing the linked booking link, it gives an exception.
  • Issue: 3530

• BUGFIX: Props on subtabs of Booking Layout not filtered based on resource

  • If you add properties to a booking layout, where those properties include a biskit drop-down whose values offered in the drop-down should be filtered depending on which resource is selected

  • then that filtering does not work when the properties are placed into a nested tab.

  • Issue: 3531

• BUGFIX: Index Out Of Bounds exception when using Multi Column table in booking layout

  • Add a multi-property column table to a booking layout, and displaying a booking would give an Index Out Of Bounds Exception.
  • Issue: 3532

• BUGFIX: Export workflow and some action types don’t export fixed values This affects:

  • BiskitCreateOrUpdateWorkflow
  • CallSubroutineWorkflowAction
  • CreateBiskitDefWorkflowAction
  • CreateVariablesWorkflowAction
  • CustomFunctionWorkflowAction
  • DefineConstantsWorkflowAction
  • DefineInterfaceWorkflowAction
  • ExecuteSystemCommandWorkflowAction

  and also

  • StepUser

  • Issue: 3534

• BUGFIX: Execute System Command actions can provide args in random order

  • An Execute System Command workflow action allows a workflow to make a call to a script or executable on the server.

  • You may pass arguments to that script, and the UI takes care to make sure that those arguments are displayed in a consistent order.

  • However, the order of the arguments is not guaranteed to be the same when it calls the script.

  • This fix ensures that the order shown in the UI is what is presented to the script.

  • Issue: 3535

• BUGFIX: Workflow copy function fails on biskits of a generated BiskitDef

  • Suppose you:
    • Add a Create BiskitDef action to a workflow
    • Create an instance of the biskit represented by that BiskitDef
    • Add an action to call the “copy” function that copies that instance
  • Then this fails with an exception.
  • Issue: 3536

• BUGFIX: Occasional exception when click on “References” button in bakery

  • This problem will show up only if you customise layouts and configure a “one to many import header” on a one-to-many property.

  • Issue: 3537

• BUGFIX: Biskit Create action loses StringEnum values on save

  • If you create a workflow that involves a Biskit Create or Biskit Update action that sets the value of a StringEnum property to a fixed value, then when you save the workflow, the display does not show the value it is being set to.

  • The value is saved to the database, but not displayed.

  • Issue: 3539

• BUGFIX: Exporting a ProcessDef makes their steps forget their editors

  • If you create a ProcessDef, and specify who is allowed to be an editor at one or more steps, then on exporting and importing the ProcessDef, it forgets who those editors are.
  • This applies regardless of whether you defined editors using a fixed or variable value.
  • Issue: 3540

• BUGFIX: Workflow copy function bad error message if try to save biskit of a generated BiskitDef

  • Suppose you:

    • Add a Create BiskitDef action to a workflow
    • Create an instance of the biskit represented by that BiskitDef
    • Add an action to call the “copy” function that copies that instance
    • Use a version of the “copy” function that lets you specify whether to save the biskit
    • Specify you want to save the biskit in the copy

  • Then this shows an error message, and on that looks like a server error.

  • However, it should show a nicer error that points to the copy function action, and tells you that you can’t save a biskit for a temporary BiskitDef.

  • Issue: 3542

• BUGFIX: Export ProcessDef and initial step property is lost on import

  • Suppose you create a ProcessDef, with at least one step, and then assign something as the initial step.
  • Then when you export the ProcessDef to SQL, there’s a bug in the generated SQL such that on loading it, the recreated ProcessDef will not have anything as the initial step.
  • The SQL gets confused between the name of the step and the name of the ProcessDef.
  • You can work around this bug by assigning the initial step the same name as the name of the ProcessDef. That would mean the import would work as expected.
  • Issue: 3544

1.10 10.1.34 January 19, 2023

Changes

• Increased limit controlling nesting depth of actions in a workflow
  • Previously, if you added nested actions in a workflow to a depth of about 50, then the workflow manager would stop being able to display any workflows at that point.
  • We have now doubled the limit to support around 100 nested actions.
  • Issue: 3559

Bug Fixes

• BUGFIX: Emails sometimes fail when initiated from a workflow
  • Suppose a user modifies an email, and there is a database event that is triggered by it, and it triggers an action that sends an email to the booking’s booker.
  • Then if the database event is configured with “vetoable” set to false, so that it runs after the update has been committed to the database, then sometimes the email fails to be sent.
  • Issue: 3563

1.11 10.1.35 February 20, 2023

Bug Fixes

• BUGFIX: Booking pop-up drop downs sometimes empty when they should not be

  • The booking pop-up will filter options available in some drop-downs so that it will only include those values that will be allowed.

  • However, following a change in 10.1.32 to fix a different problem (issue 3503), there are some circumstances in which this auto-filtering is broken which results in there being no values to display in a drop down.

  • See the notes for 10.1.32 to see the circumstances of that issue, as it is the same situation that is broken here.

  • Issue: 3578

• BUGFIX: Parsing a version 9 ID greater than 2,097,151 produces a bad result

  • If a version 9 system is upgraded to version 10, and some of the ID numbers were larger than 2,097,151 then you can’t search for those items by their formatted ID number.

  • That’s because the code that handles parsing the formatted ID numbers generates an internal overflow when given something that had an old value above the 2,097,151 limit.

  • Issue: 3587

1.12 10.1.36 March 7, 2023

Optimisations

• Optimisation: Avoid fetch from database when conditions compare biskits directly like “a == b”

  • Suppose a booking is updated, and it triggers a workflow.

  • Then you run a Search Workflow Action where you search for ProjectResourceSettings with a condition:

    value of project equals DatabaseEvent#1.New.project
    

  • That is, you’re searching for ProjectResourceSettings for the project used by the booking.

  • Then the project does not need to be fully fetched from the database to do this, because it only requires a comparison of primary keys.

  • However, this fetch was being done.

  • This optimisation is being done because it also avoids a bug that was discovered in production.

  • Issue: 3598

Bug Fixes

• BUGFIX: Workflow changes to one-to-many child of project lost by browser

  • Suppose that:

    • you have a one-to-many property on project called x, with it being a biskit of type X.
    • you then have a one-to-many property X.y, with it being a biskit of type Y.
    • you have a workflow triggered by creating a project and the workflow creates an instance of X and Y for the project.

  • Then if the user were to create a project, and immediately edit and save without a refresh of the browser in between, then the X and Y would be deleted.

  • Issue: 3592

• BUGFIX: Lazy Initialization Exception in FreeMarker templated text action post-transaction report

  • Suppose you create a Database Workflow event that is triggered from a change to a project, and mark it as not vetoable (so it runs after the project change has been committed to the database)

  • Add a Templated Text action (with FreeMarker enabled) with this as the template:

    <#if source1.New.users?size != 0>
    There are some users on this project
    <#else>
    There are no users on this project
    
    

  • then if you edit/save a project, the workflow will generate an exception.

  • Note that, since this is not vetoable, and it runs after the transaction has been committed to the database, it means that the user triggering this change will not see any indication of a problem.

  • There will instead be a problem shortly afterwards, which could be seen in the log file or system event.

  • Issue: 3593

• BUGFIX: Shallow exception saving a booking if you put status on subtab
  • Suppose you edit the booking layout to add a subtab, and then move status onto it.
  • Then whenever you save a booking, you get an exception.
  • Issue: 3596
• BUGFIX: Warning logged about ‘RepeatableBiskit’ when edit booking
  • If you enable verbose mode for ‘com.springsolutions.exprodo.core.server.ExprodoInternalServiceImpl:validate’
  • and then modify a booking, then the logs contain this (benign) warning:

    WARNING: Could not find BiskitDef 'RepeatableBiskit'
    

  • The warning is a false positive, and should not have been generated.
  • This message does not make it into the system events - only the log file in the tomcat logs directory.
  • Issue: 3600
• BUGFIX: Adding a biskit to a set property and writing back to source gives error

  • Suppose you create a workflow that defines a variable that is a set of biskits.

  • Suppose further that you use the “add” workflow function to add a biskit to that set, and then use a Biskit Update action to assign the result back to the variable.

  • Then doing that sequence twice will fail with an error saying

    “Cannot convert value of property of type List to type Set”

  • Issue: 3602

1.13 10.1.37 March 22, 2023

Bug Fixes

• BUGFIX: Long-running busy Calpendo breaks workflow manager UI

  • If you have a particularly busy Calpendo, or one that is running for a long time between reboots, then Calpendo can get itself into an error state.

  • While in this state, viewing the workflow manager will display errors for any workflow that contains a Create Variables action or a Function action.

  • The workflows will continue to run perfectly okay, but they can’t be viewed or edited properly.

  • Issue: 3413

• BUGFIX: Trouble if one-to-many children share table with another BiskitDef
  • If you have a one-to-many relationship, and the child biskit is stored in the same database table as another biskit, then viewing the parent can show more children than it ought to.
  • This is caused by confusion between the different types that are stored in the same table.
  • Issue: 3616
• BUGFIX: Infinite loop if biskit update sets non-existent variable to vars

  • Suppose:

    • You create a workflow and add a Create Variables action
    • Do not add any variables to the action
    • Add a Biskit Update action
    • Have the biskit update update the output of the variables
    • Add to the biskit update a request to set one property value

  • Now there are no variables, and so when selecting which property will be modified, there is nothing to choose.

  • In the case, the property drop-down says “There are no selectable properties”.

  • Suppose you now choose that this “unknown” property has its value set to the output of the create variables action, and then save the workflow.

  • If you try to run it, then it gives an infinite loop and an exception.

  • If you arrange for this workflow be triggered by something at boot time, then it will prevent Calpendo from booting properly.

  • Issue: 3617

1.14 10.1.38 June 19, 2023

Bug Fixes

• BUGFIX: System events cannot be deleted (if they have child chunked data)
  • System events sometimes have additional data to record beyond the standard minimal set.
  • When this happens, the additional data (which can potentially be large) is stored in a separate table where it is split into chunks (so each row can have limited size).
  • However, any system event which has this child chunked data cannot be deleted.
  • We now automatically delete the child chunked data whenever its system event is deleted.
  • Issue: 3516
• BUGFIX: Cannot book for some projects if owner defaults to project owner

  • If the owner of a booking defaults to the owner of the selected project (which is the default value), then the set of projects from which you can choose for your booking will exclude any project that is not related to the currently selected booking owner.

  • For example, suppose:

    • a user has two projects, A and B
    • these projects have two different owners, OA and OB
    • OA is not a user of B and OB is not a user of A

  • Then when you select either project, A or B in the booking pop-up, the other project would not be included in the drop-down of selectable projects.

  • Issue: 3653

• BUGFIX: Select “last week of month” for monthly repeats by day fails
  • If you make a booking repeat monthly by day (for example on the third Monday, or the last Tuesday), and you tick the checkbox that chooses the last week of the month, then the booking would appear to not have the last week selected, and would behave like it didn’t.
  • However, the information was stored correctly in the database, but was not being read and handled properly.
  • Issue: 3657
• BUGFIX: Set report schedule start date into future causes it to never send

  • Suppose you have a report that is scheduled to run every month on the 10th of the month and repeat forever.

  • With the report already saved, edit it. Whatever the start date on the repeat, set a different start date that is more than one month in the future, and save it again.

  • Then you should see that the “Next Send” date will show “nothing scheduled”, and if you wait for the report to be sent, it won’t ever be sent again.

  • Issue: 3662

• BUGFIX: Booking Approve button greyed-out when it should be enabled

  • When you edit a booking request, and the booking has a custom property storing a user, then the Approve button is greyed out.

  • This applies even if you have permission to approve the booking.

  • As a work-around, you can view the booking request instead, and from there, the Approve button works properly.

  • Issue: 3664

• BUGFIX: Booking approval button is enabled in some cases where it should not be
  • The booking pop-up has a button labelled “Confirm”, which appears next to the current status.
  • This button will attempt to promote a tentative booking to either requested or approved, and to promote a requested booking to approved.
  • If the booking is neither tentative nor requested, then the button does not show.
  • The confirm button ought to be enabled when the user has permission to change the booking’s status to requested or approved.
  • However, it was being enabled when the user had permission to change the booking’s status to anything.
  • This meant that the button would be enabled for a requested booking if you had the right to cancel the booking, but not to approve it.
  • Issue: 3665
• BUGFIX: If permissions hide menus then new users get no menu
  • Suppose you deny exists permission on the admin menu to non-admins.
  • And that you create a new user and assign them the admin role before they log in for the first time.
  • Then when they do log in, they will have no menu.
  • Issue: 3667
• BUGFIX: If a user’s settings has no menu at all, then the log in fails with an error
  • If for some reason a user’s settings has no menu assigned to it at all, then the user is prevented from logging in by a nasty error message.
  • Issue: 3668

1.15 10.1.39 August 29, 2023

Changes

• 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

Bug Fixes

• 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

1.16 10.1.40 September 14, 2023

Changes

• Prevent the system user from being added to permission ‘Applies To’ tab

  • Issue: 3716

Bug Fixes

• 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

1.17 10.1.41 December 20, 2023

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

1.18 10.1.42 March 26, 2024

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

1.19 10.1.43 February 10, 2025

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 breech 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: Rules using new projectResourceSettings see old value instead of new
  • Suppose you have a booking rule that uses the new value of a property on the booking’s projectResourceSettings for the maximum amount of time the user is allowed to book.
  • Then when you modify a booking that changes the project, the projectResourceSettings would change and reflect the new project, so the rule should see the new value on that project.
  • However, the rule uses the old value from the previous project instead of the new one.
  • Issue: 3745
• 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