Share your ideas to improve Pipefy and collaborate with our Roadmap.
Seria muito bom fazer a Inclusão de um PDF criado no Pipefy dentro de um template de e-mail atraves de campos dinamicos
It’d be amazing to be able to combine the value of 2 fields or more when creating a conditional formatting. In the picture below I made a very simple example, where the condition for hiding of showing a certain field would be that the sum of field A +B equals X, or is greater than Y, for example.
Permitir que os códigos gerados pelo campo #ID sejam personalizáveis, e não os números extensos e criados automaticamente pela plataforma.
Dentro do conteúdo dinâmico, queria poder criar uma tabela e, nas células dessa tabela, inserir uma seleção de lista (como fazemos no excel/google sheets: imagem abaixo)
Seria bem útil poder organizar os cards por ordem de entrada na fase atual, pois somente ficam organizador por ordem de criação, atualização, alfabética e manual. Isso ajudaria a priorizar os casos que estão há mais tempo na fase, ajudando a minizar o sla.
Olá pessoal, Gostaria de sugerir a opção de data de vencimento sem horário, como no campo de data simples, ter as opções de vencimento com ou sem hora, pois o que costuma acontecer muito em nossa empresa é que as pessoas lançam algo com vencimento para hoje no calendário mas não modificam o campo de horário, acarretando em um card vencido imediatamente pois o padrão é 00:00. Seria interessante ter a opção sem o horário, ou que o horário padrão considerasse 23:59 do dia atual, para que automaticamente o dia útil atual fosse o prazo de vencimento, ou para o caso da opção sem horário, o card venceria na virada do dia para o próximo.
It’d be great to be able to use automations on the start form to auto-populate fields that are commonly related to each other. This might actually make most sense in the Conditionals area rather than Automations. Ideally what I’d like to see is a way to set up this conditional/automation :When X field is filled out on the Start Form or has a specific answer > make the answer to Y field “this”. It would save people having to fill in lots of information that usually is the same for most submissions. As a silly example, let’s say I had a pipe that was tracking what kind of sandwiches people want. It might have questions like : what is the first topping you want? what is the second topping you want? It’d be nice to automate it so that when someone picks “Peanut Butter” as their first topping, it automatically fills in “Jelly” as the second topping (because Peanut Butter and Jelly go together a lot). If someone doesn’t actually want Jelly as the 2nd topping, they could manually change it, but for all the people who do want a PB&J sandwich, they’re saved a step because of the automation.
We seem to have some issues with the reports, where selecting a field for the summation, a field which exists with the same name in two different phases, leads to the field being selected twice (for the sum).This is not ok; it’s not even clear which of the two fields is finally used for the sum.On a side note: it would make sense to have the same list of fields (particularly including the phases as subtitles) in the list of fields to use for the sum as in the list of fields to use for columns. Changing all fields to have different names is not an acceptable solution (though a workaround for now); we have many pipes with many duplicate fields (reason: one field for each article to input in the one phase how many of this article to list in the offer, and then in a later phase, how many of these articles to charge/invoice).
Show a total card count in a data sets within Interfaces.
The forms are great, but if you want to use it on your website, it would be better to be able to have redirect on submission. This would open it up to be easier recorded for conversions in google analytics, ads etc.
The “field change” automation is run whenever a field is changed. However, when a connected card is changed, this automation is not run, even though it would make sense. Examples:pipe with connection to “client” database. “Client E-Mail” field on pipe’s card, since it could not be used e.g. in PDFs, or reports. However, when the E-Mail field on the connected client (database) card is changed, the “Client E-Mail” field would not be updated, and there does not seem to be a straight-forward way to get it to (even though, as I see it, it would totally make sense) pipe with connection to “articles” database. Updating the price in the database card would not update on the card if synced with an automation, as described for the client example above pipe with connnection to “client” database. Automation to update the card’s title to include the client’s name whenever the client field is updated. Again, here as well, if the name of the client in the database changes (e.g. due to marriage), one would have to manually update all titles, even though one might expect that the automation does it
In the reports, there is one list of fields to use for columns, which is nicely grouped by phase. However, the button right next to it, the Sigma, gives a rather unstructured list of fields. Would be very nice to also see which phase each field belongs.
Olá,Qual a possibilidade de criar um novo nível de permissão?uma mesclagem entre “Somente leitura” e “Visão restrita”Somente leitura: Pode ver todos os cards e fazer comentários neles. Não pode criar cards e/ou modificar cards existentes; Visão restrita: Pode criar novos cards mas só pode visualizar/editar cards que criou ou pelos quais é responsável. Não tem acesso aos relatórios do pipe; Novo Nível: Pode visualizar todos os cards, mas só pode editar os cards pelos quais é responsável.
I find it very annoying that I now have to press three times on “Show more pipes” to get to the pipe I actually want. This is very bad user experience, and I see no reason why you would change it to be like this.I could imagine reasons, but only iffI could sort them myself. But I can’t: if my pipe is alphabetically last, I will have to press multiple times. The decision would be stored: if I want to show all, give me all the next time as well, and maybe a button to hide the last row again. Pressing once is enough. That’s how it used to be, and this makes so much sense: don’t show all, such that one may decide between databases and pipes on one view. Once the decision is made, there is no reason to hide more, when I know what I want to see
Olá! Estou testando criar meus cards via importer, o problema é que quando eu não consigo colocar mais de 1 opção no mesmo campo, mesmo colocando o código ID do database de todos os meus produtos. Em conversa com o suporte fui informado que atualmente não é possível. Creio que seria bem útil a possibilidade de colocar mais de 1 opção via importer.
Hi Pipefy team All the user and permissions part (user and role) needs to be redesigned to provide greater access security for users.To improve access control and adhere to the LGPD law.Suggested Roles:ORG - Administrator - Full AccessPipe - Administrator - Full Access over Pipe and related tablesPipe - Co-Admin - Cannot modify the structure of forms, phases, and other general attributes of PipePipe - User - Have CRUD access (being optional) for better access control to Pipe and tablesUsers/Groups:Allow grouping users into Groups and these being associated with the aforementioned roles.Especially when working with external customers, it is essential that a customer does not have access to data, cards from other customers. I hope that suggestion could be useful. With regards.Ezequiel Souza
As we use Pipefy, hundreds of cards are generated that, over time, could be moved to an archive area that allows the connection to be maintained, but are not processed when opening the Pipes, thus reducing loading time. of pipes and cards.An example:When you have a pipe with service catalogs, due to intense use, hundreds of connections are created from the same card.When it is necessary to make any changes, charging takes a long time. If there is a way to have an archive of cards connected for more than 2 years, despite having the connection it would not be loaded, keeping only the 1 year old or the most recent ones.Is it possible to team?
Prezados, bom diaComo sugestão de melhoria: o usuário apesar de estar com “Visualização Restrita” deveria conseguir extrair relatório daquilo que possui visualização. Esse ponto nos ajudaria e resolveria a não depender de um usuário administrador ficar extraindo e filtrando relatório, dependendo da demanda, acaba ficando inviável.AttLeonardo Cabral
Price fields in US dollars have decimal fields separated by a dot and other currencies with a comma, so far so good. However, when using a numerical field, it has to be separated by a dot. This might sound silly because for me it is obvious that if one does not work, the other will, but for others it is not obvious.It would be helpful if users could choose their preferred decimal separator. We've received a few requests where people commented, for instance, 'It was supposed to be 9,5, but I put 10 because it does not allow decimals,' even though it does.Would be cool if we could choose!
As suggested, this product feedback follows-up on this post. As for our use case, we’ll be using Pipefy for some transactional communications with applicants. The Pipefy branding is not small, and takes away the attention that could instead be focused on our own brand, which really is the relevant one here in the eyes of the applicant. While I do understand why a company would want branding for free or small paid plans, I do not expect such branding to be present on enterprise plans. As a company that focuses on providing smooth operations for both our customers (employers) and all applicants, we really do the best we can to offer omnichannel like communications. Imagine if all the product and services we pay and use to provide those services would end up publicly tagging all that goes out of our systems with their brand So, yeah. Please allow paid (or at least enterprise) customers to remove Pipefy branding from emails and any public pages or communications, when feasible :)
Hoje os cards trazem um resumo dele na pré visualização e pode ser ustomizado (como aparecer nota fiscal, ou um e-mail, ou o nome do criador do card, a tarefa a ser executada ou enfim) mas não é possível customizar ele por etapa, a idéia seria disponibilzar essa customização. Exemplo:1- Na etapa de análise Fiscal o título do card será o nome do fornecedor e na capa o número da nota.2- Na próxima etapa será a entrada de produto onde na capa do mesmo card agora irá mudar para mostrar a categoria do produto entregue e o nome do fornecedor.3- Nessa etapa agora é de pagamento e irá mostrar na capa o código do fornecedor e conta bancária para depósito. Todas as informações já preenchidas seja no formulário inicial ou em outra etapa anterior.
We have dashboards where we can see how many cards were designated to each person. However, when someone leaves the company, those cards erase the responsible person, and they disappear from our dashboards. We have found a way to fill the void by adding another field for responsible people without a license, but it's not the ideal solution, and it's not aesthetically pleasing.I was hoping that there would be a way to remove someone's access without impacting existing cards and dashboards!
Olá Time Pipefy, gostaria de sugerir uma opção de recorrência para o “Último dia do mês” na automação de atividade recorrente.Ao iniciar os trabalhos com as automações de recorrência criei várias para dia 31, 30 e 29 e percebi que não estavam sendo realizadas devido ao fato do mês não possuir aquele número de dias.Acredito que muitos usuários gostariam de criar automações para o último dia do mês sendo essa uma data variável.
Pipefy has updated its endpoint for card creation, and now we need to provide values for all fields marked as required, even if there is a condition hiding these fields. As a result, we will be forced to allow multiple-choice fields to have options such as "-" and make fields that should be required optional.I would like to request that Pipefy review this update or allow us to revert to using the old version of the endpoint.The example below is a attachment field that should be required only in a specific situation, as defined by the conditional.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK