Foundry

  • Fix – Resource Folders were not exported when the Foundry project was compiled.  Now creates temp folder location if original folder location is not present or cannot be created due to drive not existing.
  • Fix – Publisher main menu report is now better suited for editing with the Menu Editor when Permissions is enabled due to the new Expression UserProductAccess( productCode ) being added that detects admin access defined at the Datamodel level instead of Site Setup.
  • Add – Table SQL Where Root attribute.
  • Add – Field Data Type support for Float in addition to the existing Decimal.
  • Add – Option Show PDF and Excel download icons on reports
  • Change – Publisher Reports will now hide fields related to User last Modified and Created to avoid cluttering the reports.  However, there is a Filter called Show Outputs where they can be optionally shown including the Row ID.
  • Add – Addition Field Input Styles for Web Channel Data Entry Forms.  New ones are Multi-select, Multi-Select – Checkbox and Multi-Select / Code – Checkbox
  • Add – New Field Lookup options to override the number of rows displayed in Lookups, set the Column Sort and pass parameters to Lookups to better scope the values displayed.

Studio

  • Add – Field Lookups can now pass parameters that reference a Filter value or Data Entry value based on it’s code path.  e.g.  DB|{/Site} passes two parameters to the target Lookup table DB and the code path to the filter value or data entry value with the code site. If joins are involved the report most likely use the code path {/Site} while the Data Entry Form will use something like {/Site/Code} in which case both cases can be searched for by using the + syntax e.g.  {/Site+/Site/Code}. In combination with this the new State Value {_Lookup.Lookup.Sql.Where} was created so instead of just getting the value a SQL where clause including operator logic can be obtained e.g.  >= ‘ABC’ or LIKE ‘%ABC’ or in (‘A’,’B’,’C’) in case complex filter criteria has been entered.  Note for Data Entry Forms it will always be a simple value.  By default, the data type is assumed to be nvarchar but there are variations of the State Value to specified non-Unicode varchar and numbers.  E.g. {_Lookup.Lookup.Sql.Where.NChar[1]}, {_Lookup.Lookup.Sql.Where.Char[1]} and {_Lookup.Lookup.Sql.Where.Num[1]}

Web Channel

  • Change – Azure Entra ID sign-in multi factor timeout was extended due to it being too short a time to allow for users to confirm multi-factor authentication.
  • Fix – Azure Entra ID sign-in would redirect to main index page if Dashboard Pages were the root URL link and the sub content required sign-in.
  • Add – Dashboard Pages now require sign-on unless the Requires Logon checkbox is unticked. Note that even when unchecked, if there are any Sharperlight sub content URL requiring sign-on then this setting is ignored.

Query Builder

  • Add – Expression called UserProductAccess( productCode ) to complement the existing expression UserIsAdmin(). The existing function UserIsAdmin() was true if the user account in Site Setup was set as an administrator.  However, Foundry or Studio can create Datamodels where an Administrator can assign other User Accounts as an Application-level administrators within the scope of that Datamodel. The new expression returns true if the current User Account has been set as an Application-Level Administrator. The flag to define the Users Application Level admin rights is done by create a User Logon event State Value called Perm-AppLevel::IsAdmin and setting it to 0 for false or 1 for true.
  • Add – Menu Editor now support Product-level Administrator when supported by Datamodels that define the AppLevel::IsAdmin State Value in the User Logon event.  When the checkbox Only administrators can access is set it then defines an admin user as either having admin permissions set in Site Setup or set within the Datamodel as seen with Foundry produced Datamodels that have an Application-level permissions table.