16.8.2024

So entwickelt sich Flyo - Update #202 🤩

Bist du neugierig, was es bei Flyo Neues gibt – und was sich geändert hat? Dann bist du hier genau richtig. Angezeigt werden jeweils die letzten 5 Updates. Den gesamten Changelog findest du hier.

Update #202 (03.10.2024)

[app] Improved several organization settings CRUD list views (connections, integrations, entities) to ensure sortable fields can be sorted or are disabled when not sortable.
[app] Made the badge count in the entity detail toolbar less visible and distracting.
[app] Removed social tag-related fields and entities from the system.
[app] Search in entity dropdown relation fields (schemas/schema) now supports searching in the subtitle field.
[app] Improved dark mode cursor visibility by increasing color contrast.
[app] Fixed various minor issues across the application (missing cross-conflict view, color picker form size in dense mode, donut chart errors).
[api] The field type "entities" can now be filtered in CRUD views using the filter dropdown.
[api] Ensured the Guidle integration XML does not contain invalid special characters for XML output.
[api] Handled WYSIWYG fields differently in schema subtitle mapping context (removed HTML values, stripped tags).
[api] Fixed i18n value unpacking for relation fields in the schema subtitle mapping context.
[api] Ensured agency members are correctly visible in the hover cards of the dashboard.
[api] The team member list API now supports searching by last name, email, and full name, not just first name.
[api] Prepared fields to be correctly formatted in a Canva integration context.
[venue] Improved handling of file/image upload errors, providing a more detailed error message explaining why the upload failed.
[venue] Clicking the back-to-list button now always forces a reload of the list.
[venue] The list of entries now includes time information (if present) as a separate column.
[venue] All fields in the list view can now be sorted by clicking on the column header.
[venue] Added a new search button to reveal the search input field for searching the list of entries.

Update #201 (27.09.2024)

[app] It is now possible to set a desired position when placing a row into a curated content pool. The entity row is inserted at the specified position.
[app] The team detail view now reveals more comprehensive information about the user's role context (e.g., is manager, is owner, is member, is venue user, can edit venue, can insert into venue). This makes it clearer what permissions the user has. Additionally, this information is now available on the "My Profile" page for the logged-in user.
[app] The venue app users list now displays whether a user can update and/or insert entries.
[app] Added a total item count to curated content pools for better tracking and overview.
[app] Aligned the team member configuration views (Pools, Edit, Focusboards) with global styling for a more consistent UI experience.
[app] Improved the role permission views for clearer distinction between content functions and permissions, enhancing overall usability.
[app] Ensured organization owners always have full permissions (e.g., creating a new integration platform).
[app] Fixed an issue where field configuration was not appearing under certain conditions.
[app] When an i18n field has an error in a form, the error message now appears below the field instead of just in a snackbar toast for better visibility.
[api] Improved the uniqueness validation behavior of fields (commonly used for slugs) in an i18n context, enabling uniqueness checks for specific languages.
[api] Integrations can now track files/images they have used, preventing deletion of files/images that are still in use.
[api] The file detail API now returns a list of used integrations, currently supporting Nitro CMS.
[api] The venue integration now tracks whether a user can only create entries or also update them.
[api] Made the manager role more consistent: the manager can now create entries for all entities, not just update or list them.

Update #200 (19.09.2024)

[app] Renamed the "Administratoren" tab entity to "Venue" for clarity, indicating that these users are not part of the Flyo team.
[app] Fixed an issue where the content pool data condition builder did not refresh the field list when the entity was changed.
[app] In the Nitro CMS integration, when a content pool is replaced by another (in the mapping section), the mapping fields will now only reset if the newly selected content pool is incompatible with the old one.
[app] Improved handling of widgets in Focusboards created in legacy versions.
[api] Introduced a new Agency Core API endpoint.
[api] Social tag permissions are no longer displayed when entity tags are disabled.
[api] The organisation owner now has full permissions across the organisation, not limited to roles and member permissions as before.
[api] The "link" field type is now correctly handled in the embed integration, utilizing the href property for links.
[api] Enhanced security when team members are deleted.
[api] The user token now uses a binary comparison for improved security.
[api] Optimized the Venue integration to handle a larger number of entity users displayed in the venue integration (users table).
[api] Improved readability of the Venue log text.

Update #199 (06.09.2024)

[app] The Focusboard and Dashboard widgets can now be dragged and dropped to reorder them.
[app] Improved the loading behavior of dashboard widgets for a smoother experience.
[app] The Plausible dashboard widget chart has been improved to use lines instead of bars. Additionally, wording has been refined, and dates now include weekdays for better data clarity.
[api] Improved the stability of Algolia sync integrations.
[api] Fixed an issue where the entity row file count was not updated correctly.

Update #198 (30.08.2024)

[app] The Organization Dashboard can now be customized, allowing organization managers to select which widgets are displayed. The dashboard can be tailored to show only the most relevant information. Customization is applied at the organization level, meaning it is not personalized per user.
[app] By default, all widgets on the dashboard are now visible, even if they don't have any data. In such cases, an image and a message indicating that no data is available will be shown. This change is necessary because widgets can now be placed but cannot be hidden when they are empty.
[app] Redesigned the look and feel of the Focusboard widget placement. The widget configuration is now hidden by default and needs to be expanded, making the Focusboard edit and add process clearer.
[app] Updated the curated content pool view to be more consistent with other card views. A full-sized add button has been added, and the generic "Contents" title has been removed.
[api] Focusboard validation security has been significantly improved to ensure that only authorized components can be used as widgets.
[api] Ensured that users are correctly removed from a Focusboard when they are removed from Flyo.
[api] Improved handling of pinned items that might no longer exist.
[api] Fixed an issue where the API did not return the correct content pool "is_single_entity_type," which could lead to displaying the entity type label unnecessarily.

Update #197 (23.08.2024)

[app] Reduced reaction time when searching in entity relation fields.
[app] The WYSIWYG editor now hides the toolbar if there isn't enough space to display the buttons, making it easier to use on smaller screens.
[app] Added heading options to the WYSIWYG editor's "bubble menu," which appears when selecting text in the editor.
[app] Display all related files for an entity row on the dashboard and in the new "Files" tab.
[app] Improved the "connected content" interface in the file detail modal. Files are now grouped by their entity and can be toggled.
[app] Fixed a bug where the file manager's entity filter dropdown did not reset the rows dropdown correctly when changing the entity.
[app] Added more helpful information for the Guidle integration and grouped the mapping fields for better readability during mapping.
[app] Fixed a bug where toggling WYSIWYG custom elements did not work correctly when the custom element utilized the "recursively content" option.
[app] Refactored the UX of the integration group view to hide the toolbar and moved the edit button next to the title and image in the sidebar. This creates more space for the integration itself and reduces UI distractions.
[app] The integration is now available in the recently used items history, replacing the integration group, which has been removed from this history.
[api] Added new Guidle integration mapping options for media services in events.
[api] Images and files can now be internally associated with the entity row, even when used in a WYSIWYG editor. This significantly improves file and image search functionality in the file manager.
[api] The Nitro OpenAPI definition now includes Field models such as image, file, and WYSIWYG. These models can be used in SDKs to enhance Type Hinting in applications.
[api] Added missing fields to the Guidle API and ensured the cache is purged when API data is updated.
[api] Added the platform image to the integration when pinned.

Update #196 (16.08.2024)

[app] Enhanced the lat/lng fields by adding error messages to provide clear feedback when there are issues with the coordinates.
[app] Resolved an issue where Focusboards failed to load the correct data for i18n Nitro CMS integrations, ensuring proper localization and content display.
[app] Updated row navigation elements (Dashboard, Edit, Connections, Activity, etc.) to dynamically use the color associated with each entity, improving visual consistency and user experience.
[api] Fixed a bug in the lat/lng field where it incorrectly required a value even when the field was not marked as required.
[api] New integration with the Guidle-Service, released for public beta testing, allowing seamless data synchronization to the Guidle platform. This integration helps ensure that your content is always up-to-date, complete, accurate, and relevant for your target audience.
[api] New Canva integration for internal testing phase, enabling users to sync their designs directly with our platform, streamlining the creative process and enhancing design capabilities.

Update #195 (09.08.2024)

[app] A new indicator in the WYSIWYG editor helps insert elements into the content at the current cursor position. Additionally, custom elements can now be minimized to save space in the editor.
[app] The default YouTube and Image insertion options have been removed from the WYSIWYG editor and need to be replaced with new custom elements.
[app] UX overhaul of the WYSIWYG custom elements configuration panel when managing WYSIWYG fields. A new help article has also been added.
[app] Added Vimeo and Google Maps as templates for WYSIWYG custom elements, making it easier to add these elements to the content. Adjust the templates to your needs, but they provide a good starting point.
[app] The Co-Pilot interface has a new option to target a specific language when creating prompts and to specify a target language for multilingual fields. It is also possible to define whether the Co-Pilot should create a proposal instead of directly modifying the content.
[api] Fixed an issue where trigger delays were also affecting content pool changes, which was not intended. The trigger delay should only apply to content changes.
[api] Improved the handling of WYSIWYG editor output for i18n-enabled fields.
[api] The file upload throws an error if there is no file provided in the upload.
[api] The activity log for i18n fields has been improved to display more accurately what value has changed in the given language context.
[venue] Field types for address and YouTube are now available in venue forms.
[venue] Deprecated social tag requests have been removed.

Update #194 (02.08.2024)

[app] Beta release of a new virtual folders feature, allowing users to organize their files into virtual folders built like filters.
[app] Option to reset grid filters with a single click, without opening the filters dropdown.
[app] Indicate whether a language is translated or not in the language selector. This makes it easier to see which languages have been translated and to switch to the given language.
[api] Improved data fetching for compatible pools with lat/lng fields stored in a direct location. This is useful for creating maps with events where an event has a location entity storing the lat/lng information.
[api] Default meta description and image definition for all Nitro CMS pages.
[api] New option for integration trigger delay, useful for triggering an integration after a certain time. This applies when content changes and the connected integration is triggered with a delay. See the documentation.
[api] New YouTube field type formatter, ensuring that an embeddable link is always returned.
[api] Improved error messages for when a timed social media post fails due to a missing (deleted) channel.

Update #193 (24.07.2024)

[app] You can now sort the "dynamic information" mapping field in both grid and list views for entities.
[app] Enhanced the onboarding process: if the authentication challenge expires, a login button will appear, redirecting you back to the onboarding process.
[app] Fields defined as i18n have undergone a UX overhaul. Only the first language is visible by default, and the other languages can be toggled, significantly reducing the length of forms with i18n fields.
[app] The image and YouTube insert buttons are deprecated. Instead, custom element templates for image and YouTube are available, reducing unnecessary default elements for certain use cases.
[app] Introduced a new YouTube field type, allowing the insertion of YouTube videos with a preview image and an embeddable link.
[app] Fixed an issue where language-dependent pages were unavailable in the Nitro CMS page selector.
[app] Fixed an issue where legacy blocks appeared incorrectly in the blocks overview (grayed out).
[app] Fixed an issue where the "visibility" dialog always appeared for all fields when a new field was added to an entity.
[app] Removed the web builder integration type when creating new integrations, as it is deprecated and will be removed soon.
[api] Dropdown fields are now automatically included in the list of filter attributes in the grid view.
[api] Added a new endpoint to resolve integration details, replacing the need for complex expansions.
[api] Removed the deprecated JSON-LD from the model response. It is now placed in its own JSON-LD section key for entity responses.
[api] The content pool field type now includes the online items count in API responses.
[api] Improved API performance for Nitro CMS page preview requests, which update the Nitro page content for the development token.
[api] Ensured a consistent default behavior for checkbox list field types, always returning an object with values, options, and labels, even if they are empty.
[api] Added a missing rule attribute to the create and update form to include min/max length counters in the app.
[api] Fixed the organization dashboard when a SoMe channel is missing in the schedule timings list.
[api] Newly created organizations now have a default prepaid credit amount.
[api] Switched to the new GPT-4o-mini model for faster responses and lower costs.
[api] Until the web builder integration is dropped, the development token for Nitro CMS won't track any requests, reducing credit usage when developers work on the website. The development token should never be used in production due to slow response times, which result in slow websites.

Update #192 (10.07.2024)

[app] Added new configuration options for entity fields: "required when" and "visible when" conditions.
[app] When adding an image to the WYSIWYG editor, copyright and caption/title information will now be included.
[app] Refactored create and update forms for entities to improve performance.
[api] Improved OpenAPI example code documentation for image and file field types in SDK Integration.
[api] Added a new endpoint for entity-based forms to render and build all information on the server side.
[api] Introduced a new entity field option to make a field required only if a specific condition is met based on another field.
[api] Introduced a new entity field option to make a field visible only if a specific condition is met based on another field.

Update #191 (21.06.2024)

[app] The Flyo help sidebar now searches within the help.flyo.cloud documentation, providing more and better results for any problems.
[app] Automation triggers and schedule information are now displayed in a Focusboard widget.
[app] Clicking on the edit icon in the list of entities (grid or list view) now directly opens the edit form, instead of the dashboard.
[app] Info modals are now referenced to the new help.flyo.cloud documentation.
[app] I18n proposals are now correctly displayed, showing only the changes made to the given languages.
[app] When a Nitro integration block has no config, content, or items, a message is displayed and the UX has been improved.
[app] Fixed issue with Nitro preview frame language context for the default (home) page.
[api] Replaced the internal wiki with the help.flyo.cloud documentation.
[api] Ensured an organization always has a default language, even if there is just one language.
[api] Removed files for the "fixed entity" concept, so no activities are created for file changes anymore.
[api] The new proposal system can now handle i18n field diffs.
[api] Fixed issue where it was not possible for integration editors to update integration content pools due to missing permissions.

Update #190 (14.06.2024)

[app] The content pool filters option has been relocated behind an icon, with default filters added for creator, status, and crosscheck status.
[app] Added the organisation name to the new proposal email dialog, allowing it to be sent to the proposal creator.
[app] Display the column bar chart legend even if there is only a single entry. This helps users understand the data shown on the chart.
[app] Enhanced the file upload dialog to always allow adding new files after uploading.
[app] Fixed a bug that prevented configuration settings in Nitro page properties under certain conditions.
[app] Venue integration now allows optional fields to be shown or hidden.
[app] Integrity checks can now be enabled or disabled for specific entities.
[api] Added new entity filters for grid views.
[api] Changed the Nitro JSON-LD response to an Article instead of a Thing, adding more default values.
[api] Removed URL check integrity tests due to numerous incorrect test results for pages behind certain CDN systems like Cloudflare, Vercel, Netlify, etc.
[api] Improved language handling in multilingual Nitro integration setups. Default pages for each language are now possible, meaning entries like fr and en can be used, with the primary language home page being an "empty" slug.
[api] Original uploaded files are now kept intact if they fall within a certain max pixel density range, ensuring they are not modified and can be used for other purposes.
[connect] Updated to the latest LinkedIn API version.
[webbuilder] Adopted the new Article-based JSON-LD schema for detail pages.

Update #189 (06.06.2024)

[app] Launched a new proposal API, enabling email notifications for proposal creators and featuring a redesigned user interface.
[app] Enhanced activity log details for images and text areas.
[api] Developed a new proposal API.
[api] Disabled URL integrity checks due to the high volume of failing requests, reducing unwanted notifications.

Update #188 (31.05.2024)

[app] You can now sort entity form designer sections using drag and drop.
[api] Various performance and stability improvements have been made to the venue API. Additionally, a new OpenAPI endpoint is available in beta for the venue API, enabling integration without the need for the Embed Code.
[api] A password strength validator has been added for creating team members.
[api] Fixed a bug where users did not receive an email when a new team member was created.
[api] Fixed an issue where a Nitro CMS page path appeared in the list of valid paths (in the config request) despite the page being offline.
[api] Enhanced error messages for password reset and login forms.
[api] Improved the token comparison function to address case sensitivity issues.
[venue] The venue system now supports the new pool-based entity/entities field configuration.
[venue] Removed deprecated entity types (POI and events) from the embed system code.