3 posts tagged with "features"

New features 🎉​

Segments UX & UI overhaul​

The segment block has undergone a UX and UI overhaul to enhance usability and further improve the user experience. The segment overview now includes various sorting options, allowing users to sort not only by name but also by creation date and last update date. Additionally, segments now clearly display the type of selection being made (query or fixed) and the number of matching cards for that segment at the time of viewing the page.

New creation flow​

Segment creation is now a guided experience, assisting the user throughout the entire setup process. Initially, users set the name, card, category, and select one of the newly available, stylish icons.

The selection type is displayed clearly, explaining the differences between the various types. Creating fixed segments from a CSV file is highlighted as a separate option for ease of use (more on that feature further down 🙃↓).

Segment types are out, categories are in!​

Previously, before creating a segment, users needed to create a segment type, which was a bit cumbersome. This step has now been removed and replaced with segment categories. Categories provide a way for users to structure segments based on the same card into a subgroup (a categorization, if you will 😉). Categories are either created or selected during the segment creation process. If no specific category is actively selected, the segment will be automatically categorized with the card name.

New filtering panel​

The filter panel has been moved to pop out from the right-hand side when opened and now displays all properties of the card by default. The interaction of all property types (e.g., text, boolean, timestamp, etc.) has been improved to cater to a more user-centric experience.

Better visualization of excluded items​

Finding which cards were manually excluded from a segment was previously practically impossible, stirring waves of uncertainty. The presentation of excluded items in the UI has been enhanced, and functionality has been added to easily display the entire list of excluded items for a better overview.

Create fixed segments directly from a CSV file​

It is now possible to create a fixed segment based on a pre-existing CSV file containing card IDs. During the creation process, the list is validated against the current dataset in Occtoo. Any missing IDs are flagged, making them available for download and further analysis.

New features 🎉​

User management​

We are excited to announce the release of our new user management feature, designed to streamline and enhance the way you manage user roles within Occtoo Studio. This feature introduces a structured approach to user permissions, ensuring that your team members have access to the tools they need without compromising security or operational efficiency. With the addition of three distinct user roles—Administrator, Contributor, and Reader—you can now tailor access levels to align with individual responsibilities and organizational needs.

The Administrator role is the most comprehensive, offering full access to all Occtoo blocks and operations, including user management. This role is ideal for team leaders or IT personnel who require the ability to oversee and modify user permissions, manage content, and perform any administrative tasks. On the other hand, the Contributor role provides similar extensive access but excludes the capability to manage users. Contributors can interact with and modify all Occtoo blocks and operations, making this role perfect for content creators and developers who need robust tools to carry out their tasks effectively without the additional responsibility of user administration.

Lastly, the Reader role is designed for users who need to access and view data without the ability to make any changes. This role ensures that important information can be disseminated across the organization without risking unintended modifications or deletions. Readers can access all content within Occtoo, making it suitable for analysts, stakeholders, or any team members who require insight into the system’s data without engaging in operational actions. This new user management feature not only enhances security but also improves workflow by clearly delineating user responsibilities, empowering your team to work more efficiently and securely.

New features 🎉​

Update existing destination​

With this latest update to the Occtoo Studio, users now have the possibility to make non-breaking changes to their destination endpoints. This means that for any additions to existing endpoints, one doesn't need to create a new destination version, making life much easier for any dependent experiences

Users now have the possibility to add new or previously excluded properties to an endpoint. It is also possible to enable facets on existing properties.

Additionally, users can add relations, including related information directly.

Last but not least, users now have the possibility to alter the segments used in endpoints. The new update gives them the ability to include or remove segments, altering the presented result to their liking.

More information can be found in the docs.

Connected blocks​

Each individual object in Occtoo blocks now has "connected blocks" section, visualizing and linking which other individuals they either contribute to or are dependent on. This makes the life of users easier as they now can follow the chain from any block in any direction, understanding how all things in between are connected.

In the example above we can see how the card "Customer" is based on the source named "Customer", and that it also is used by 3 segments and 8 destinations.

More information can be found in the docs per block: source, card, segment and destination.

Opt-in gzip response from destinations​

With the latest release, we also enable the possibility to request API content to be compressed using gzip. Gzip compression drastically reduces JSON response size, boosting network efficiency and accelerating data transfer. This optimization cuts down on redundant information, resulting in faster loading times and smoother user experiences, especially on slower connections.

By setting the content header property Accept-Encoding to value gzip (NB! lower case) the response will be returned using gzip compression. Side note: This will only apply on new destinations and destination versions.