Coming soon: Core Workflows (Dynamic Object Screens)

UPDATE

It’s happening! :star_struck: The feature will be part of our upcoming release, Zammad 5.0.

In our recent Twitter Poll, we asked you what the feature should be called. Some users reached out in a DM and shared their concern that neither of the options provided in the poll properly represented the full scope of possibilities that this feature offers. :thinking:

We took this feedback and their suggestions into account, and have now decided on a name which unfortunately doesn’t fully reflect the poll results. However, we believe that it perfectly describes the functionalities of the feature.

Drumroll please! :drum:
Say Hello to… :tada: Core Workflows (Dynamic Object Screens) :tada:

A big thank you to everyone who participated in the poll, and who shared name ideas.

:face_with_monocle: Want a sneak peek?

We are looking for ten beta testers to give us their feedback on the new feature. If you want to be one of them, shoot us a message at enjoy@zammad.com and we’ll discuss the details. But hurry, there are limited spaces!

We are super excited! Are you?


ANNOUNCEMENT

:rocket: Together we move Zammad forward! :rocket:

That’s exactly what our name says :upside_down_face: But now it’s up to YOU to start a new era in Zammad ticket creation and processing with us and other feature sponsors!

With :heartbeat: tingles, we’ve been watching the use cases of Zammad grow for a while now. The more broad use cases involving more teams wanting to work with Zammad, the greater are the requirements for Zammad.

One issue that comes up again and again, especially for Zammad use with several teams, is the rigid ticket mask.

What are the current limitations? :construction:

Up to now, Zammad has only offered the possibility of creating and editing screens for agents and customers.

However, different teams must use the same ticket entry screens.

What is the solution? :dart:

Just as big as the requirement is, is the solution approach that we want to put into practice. But we tell you, it’s worth it:

We call it: :star2:Object-Form-Flow :star2:

With this new feature, it will be possible (i.e.) to provide different teams (groups) with their own, individual ticket masks.
But not only that: the current field selection in the ticket also dictates further fields.

This means: Depending on the current ticket object selection, further ticket objects:

  • can be shown or hidden AND
  • selection options can be limited AND
  • can be defined as mandatory or optional

Sounds good? Do you want it? :tada:

So do we! But as already mentioned, the development effort is enormous. We have done other feature sponsorships before, but the scopes have been much smaller so far. Since we know that there are many of you who want to support Zammad but each have different budgets, we have come up with something new.

We are offering different sponsorship packages so that you can support development according to your own means.

What is included in the sponsorship packages? :gift:

By sharing the cost, you bring this feature to the top of our roadmap out of order. We have many feature requests that we work on as best we can (as described here: Zammad Support Knowledge Base - Request a Feature). The priority increases with each sponsorship. Meaning: the more sponsors, the more focus on that feature.

You also get some publicity for your organization on the release day (if you wish) as well as other benefits:

:medal_military:Platinum sponsorship :medal_military:
Already awarded

:1st_place_medal: Gold sponsorship :1st_place_medal:
Participation: 16.000€

Benefits:

  • Is only handed out once!
    Benefit from exclusive marketing measures tailored exactly to your needs and preferences
  • Mention in our release notes & Social Media Posts
    we are happy to support the SEO performance of your organization with backlinks.
  • Easy start:
    In a free consulting workshop (3h) we will support you in detail with the setup of the functionality in your existing instance.
  • Be among the first:
    Get a test version with the add-on already before the release date

:2nd_place_medal: Silver - Sponsorship :2nd_place_medal:
Participation: 4.500€

Benefits:

  • Mention in our release notes & Social Media Posts
  • Getting started is easy: In a free consulting workshop (1h) we show you how to set up the new feature.
  • Be among the first:
    Get a test version with the add-on already before the release date

:3rd_place_medal: Bronze Sponsorship :3rd_place_medal:
Participation: 1.500€

Benefits:

  • Mention in our release notes & Social Media Posts

How to become a sponsor? :bouquet:

It’s very simple: contact us by mail or phone. We will send you an offer immediately and discuss everything else with you.

We look forward to hearing from you!
[/quote]

:

It’s happening! :star_struck: The Object Form Flow Feature will be part of our upcoming release, Zammad 5.0.

:timer_clock: What happens now?

The exact release date is still TBD. In the meantime, you can help us out:

We are looking for a name for the new feature!
Head over to Twitter to vote for your choice in our poll:

:face_with_monocle: Want a sneak peek?

We are looking for ten beta testers to give us their feedback on the new feature. If you want to be one of them, shoot us a message at enjoy@zammad.com and we’ll discuss the details. But hurry, there are limited spaces!

We are super excited! Are you?


ANNOUNCEMENT

:rocket: Together we move Zammad forward! :rocket:

That’s exactly what our name says :upside_down_face: But now it’s up to YOU to start a new era in Zammad ticket creation and processing with us and other feature sponsors!

With :heartbeat: tingles, we’ve been watching the use cases of Zammad grow for a while now. The more broad use cases involving more teams wanting to work with Zammad, the greater are the requirements for Zammad.

One issue that comes up again and again, especially for Zammad use with several teams, is the rigid ticket mask.

What are the current limitations? :construction:

Up to now, Zammad has only offered the possibility of creating and editing screens for agents and customers.

However, different teams must use the same ticket entry screens.

What is the solution? :dart:

Just as big as the requirement is, is the solution approach that we want to put into practice. But we tell you, it’s worth it:

We call it: :star2:Object-Form-Flow :star2:

With this new feature, it will be possible (i.e.) to provide different teams (groups) with their own, individual ticket masks.
But not only that: the current field selection in the ticket also dictates further fields.

This means: Depending on the current ticket object selection, further ticket objects:

  • can be shown or hidden AND
  • selection options can be limited AND
  • can be defined as mandatory or optional

Sounds good? Do you want it? :tada:

So do we! But as already mentioned, the development effort is enormous. We have done other feature sponsorships before, but the scopes have been much smaller so far. Since we know that there are many of you who want to support Zammad but each have different budgets, we have come up with something new.

We are offering different sponsorship packages so that you can support development according to your own means.

What is included in the sponsorship packages? :gift:

By sharing the cost, you bring this feature to the top of our roadmap out of order. We have many feature requests that we work on as best we can (as described here: Zammad Support Knowledge Base - Request a Feature). The priority increases with each sponsorship. Meaning: the more sponsors, the more focus on that feature.

You also get some publicity for your organization on the release day (if you wish) as well as other benefits:

:medal_military:Platinum sponsorship :medal_military:
Already awarded

:1st_place_medal: Gold sponsorship :1st_place_medal:
Participation: 16.000€

Benefits:

  • Is only handed out once!
    Benefit from exclusive marketing measures tailored exactly to your needs and preferences
  • Mention in our release notes & Social Media Posts
    we are happy to support the SEO performance of your organization with backlinks.
  • Easy start:
    In a free consulting workshop (3h) we will support you in detail with the setup of the functionality in your existing instance.
  • Be among the first:
    Get a test version with the add-on already before the release date

:2nd_place_medal: Silver - Sponsorship :2nd_place_medal:
Participation: 4.500€

Benefits:

  • Mention in our release notes & Social Media Posts
  • Getting started is easy: In a free consulting workshop (1h) we show you how to set up the new feature.
  • Be among the first:
    Get a test version with the add-on already before the release date

:3rd_place_medal: Bronze Sponsorship :3rd_place_medal:
Participation: 1.500€

Benefits:

  • Mention in our release notes & Social Media Posts

How to become a sponsor? :bouquet:

It’s very simple: contact us by mail or phone. We will send you an offer immediately and discuss everything else with you.

We look forward to hearing from you!

7 Likes