Release Date(s)
Release date | July 10th, 2023 |
What's New?
Description |
We've added the ability to create templates to our data export tool so that you can save the export configurations you use regularly to extract data from Skedulo. Read more about how to create templates in the documentation: Create export templates. |
Enum (picklist) values can now be displayed by their label in record pages and list views rather than values by using the enumLabel filter function in templates. This filter function requires both the enum value itself and the path to the enum on the record.
Example:Consider the enum diet with value NonVegetarian with label Non Vegetarian, the label can be displayed in a template with: {{{{ diet | enumLabel("diet") }}}} For nested values on records, or records that are on variables inside a template, consider this example. A Record variable (e.g. on a record page), where the record has a CreatedBy User field and we want to display the first UserType of that User. It would look like the following: {{{{ Record.CreatedBy.UserTypes[0] | enumLabel("CreatedBy.UserTypes") }}}}. Here is an example GIF of usage inside a record page and list view: |
When onboarding resources, deactivated resources now appear last in the list of resources with a warning next to the resource's name. |
Issues Resolved
Description |
Users reported that some Read only fields, such as FullName would sometimes block a user from saving. Skedulo Pulse Platform Pages with Read only fields will now save successfully. |
Read only fields are now hidden from the edit mode on Pulse Platform Pages. |
Comments
0 comments
Please sign in to leave a comment.