Recherches récentes
Pas de recherche récente

Tim Leder
Adhésion le 26 sept. 2023
·
Dernière activité le 17 juil. 2024
Suivis
0
Abonné
1
Activité totale
11
Votes
3
Abonnements
3
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Tim Leder
Tim Leder a ajouté un commentaire,
Hi Daniel Aron :) For example .eml files since in some scenarios we need a full original unaltered mail for further investigation (e.g. only the header of the email or processing logs would not be enough).
Afficher le commentaire · Publication le 17 juil. 2024 · Tim Leder
0
Abonnés
0
Votes
0
Commentaire
Tim Leder a ajouté un commentaire,
Gareth Elsby Thank you!! We have similar monstrous examples, and I get easily lost tweaking stuff in the flow.
Afficher le commentaire · Publication le 17 oct. 2023 · Tim Leder
0
Abonnés
0
Votes
0
Commentaire
Tim Leder a créé une publication,
Feature Request Summary:
Add the ability to use simple functions like to get the current time, format text, initialize variables and so on.
Description/Use Cases:
Allows for more usability/variety and does not require third party tools to be used instead.
Business impact of limitation or missing feature:
For an API call after the customer provided some data I needed the current time and time before 365 days. To complish this I needed to create a Microsoft Power Automate flow which could be queried with an API to get the current time there since there is possibility to get the current time in the format I needed from Zendesk since also responses can not be formatted.
Other necessary information or resources:
-
Publication le 26 sept. 2023 · Tim Leder
3
Abonnés
4
Votes
2
Commentaires
Tim Leder a créé une publication,
Feature Request Summary:
After branching out, allow branches to lead again to a single branch.
Description/Use Cases:
This would allow more complex flows and eliminate redundant final steps (e.g. several branches lead to the same finish and right now the same thing has to be created over and over again)
The following diagram should illustrate what we would like to accomplish.
Business impact of limitation or missing feature:
Right now the same thing (e.g. last step) has to be created over and over again which leads to unnecessary overhead in flow, bad maintainability, scalability and it is more prone to user errors.
Other necessary information or resources:
-
Publication le 26 sept. 2023 · Tim Leder
3
Abonnés
5
Votes
4
Commentaires
Tim Leder a créé une publication,
Feature Request Summary:
Possibility to insert a step which request the upload of a file and make it easily accessible for creating a ticket.
Description/Use Cases:
Example file is needed and after going through the bot flow a ticket should be opened with said file attached.
Business impact of limitation or missing feature:
It limits the ability of the bot to handle scenarios where a upload with following ticket creation is needed. For example right now it is only possible to create a ticket via API call from the bot flow then instruct to upload a file in the bot flow and trigger on ticket creation to check with SunCo for the attachment. Or paste a link to Help Center Forms in the Bot conversation and there the Upload field is optional.
Other necessary information or resources:
-
Modification le 27 sept. 2023 · Tim Leder
11
Abonnés
10
Votes
7
Commentaires