Topics started by mark-theotcentre

16 Topics

mark-theotcentre
mark-theotcentreNew Participant
asked in Ask the Community

Synchronize card's field with this fixed field

Can someone help me understand the purpose of the “Synchronize card's field with this fixed field” capability on fields like Assignee, Label, Due Date?Perhaps someone can suggest some real-world use cases which would help me see how/why.Also, what direction is sync? eg;if an assignee field is set, does this update the Assignee field on the Card if the Assignee field on the card is set, does this update Assignee fields on Phases?THanks for any help

4
marcosmelo
5 hours ago
mark-theotcentre
mark-theotcentreNew Participant

Conditional FlowsSubmitted

RequirementThere are many circumstances where Card Flow through a Pipe needs to be based on Data Condition(s)ProblemCurrently Pipefy Flows are static. Movement of a Card from Phase A to Phase B might be invalid for cards with certain data field values. In these situations, a card user has to push a card from Phase A to Phase B anyway which can be confusing for the user but also represents an unnecessary step and process delay.Pipefy’s ‘solution’ for this currently is either to create an Automation to move the Card out of the redundant phase. However, the user first has to move the card to the redundant Phase!The other ‘solution’ for this is to get the user to disable the move button for the redundant phase, but this is clunky.SolutionAllow Conditions to be created on Flows

7
Rodrigo Subirá
Pipefy Staff
22 days ago
mark-theotcentre
mark-theotcentreNew Participant
asked in Ask the Community

Clarify "connected card" and "parent card" terminology on Pipe Connections

Could someone help clarify terminology on “Advanced Options” for a Connection Field on a Pipe Phase Am I correct in thinking that the Pipe Phase Card is the “parent card” and any cards associated with it in this pipe or any other pipe are “connected card”? Thanks

1
marcosmelo
25 days ago
mark-theotcentre
mark-theotcentreNew Participant
asked in Ask the Community

Field Conditionals need to recognise 'current user'

RequirementIn the absence of Parallel Flows in PipefyApproval Processes can hold up an entire process when some phases in a process could continue whilst an Approval is sought.For example, imagine Phases A,B and C need approval before Phase F can be undertaken but Phases D and E could be undertaken whilst approvals are sought on A,B&C.SolutionPhases A,B and C have an Approval Assignee field.  When Fred, the user assigned for Approval opens Phase A, a field condition detects that ‘current user’ = Phase A Approval Assignee and shows a (previously hidden) Approval Date fieldWith this approach, a Card needn’t move to a dedicated Approval Phase. Approval is possible in the Phase in which it was requested

5
marcosmelo
28 days ago
mark-theotcentre
mark-theotcentreNew Participant
asked in Ask the Community

Parallel Flows

RequirementThere are many circumstances where a Card needs to flow into several Phases at the same time so that the card can be worked on by multiple people at the same time for different purposes. There are also circumstances where parallel flows need to operate dynamically based on field conditions (see my separate post here ProblemCurrently Pipefy Flows are linear so a card must exit one Phase before it can be worked on in another. Business Flows/Processes don’t operate like this in reality, linear processes cause delays, sometimes huge delays!SolutionAllow Parallel Flow creation

3
marcosmelo
28 days ago
mark-theotcentre
mark-theotcentreNew Participant

Allow Card to link to a Card on another Pipe even if the latter card is closedSubmitted

There are circumstances where it is important to be able to link a card back to Cards on another Pipe even if those cards on the other pipe are in a phase which is marked as “end of process” and the pipe is on a public form.

3
Rodrigo Subirá
Pipefy Staff
1 month ago
mark-theotcentre
mark-theotcentreNew Participant

Control sort order of Database Connection FieldsSubmitted

Database Connection Fields on a Form display items in the order they were created in the Table which is very unhelpful for Form Users.The Form designer should be able to specify the sort order of items on the Field based on one or more Database Fields

3
Desirée Hoppe
Pipefy Staff
8 months ago
mark-theotcentre
mark-theotcentreNew Participant

Database Connection Fields: Usability ImprovementsSubmitted

Sorting: allow sorting controls on the field so that data ordering can be controlled for the user experience Filtering: allow filtering controls on the field so that data item visibility can be controlled Select All: expose a ‘select all’ option for the user when the field is configured to allow multiple selections General presentation: style and font-size need to be in keeping with other form elements. Presentation style at the moment is not conducive to the user experience

3
Priscila Rodrigues
Pipefy Staff
8 months ago
mark-theotcentre
mark-theotcentreNew Participant

Dropdown Select & Radio Select Fields : allow disabling of list values rather than deleting valuesSubmitted

It isn’t currently possible to delete a list option from a dropdown select or radio-select field without deleting those values from any Cards which have already been assigned those values. What’s the problem?We need to be able to ‘disable’ list values in Drop-Down and Radio-Select fields, as we can with Database Table entries. What’s the solution?The ability to disable a list option in a drop-down or radio field will ensure that options can be ‘hidden’ from user selection but any cards already assigned to that value will not be affected and thus reporting on historical data will not be affected

4
Ezequiel Souza
8 months ago
mark-theotcentre
mark-theotcentreNew Participant
asked in Customs Apps & Integrations

Managing Asynchronous Communications with products like ZAPIER

We’re building out our first Workflow using Pipefy and alongside this are using Make (an integration tool, akin to ZAPIER) to process data and keep in sync with our other systems.All very straightforward except when it comes to the challenge of ensuring that the integration engine keeps in step with events on Pipefy.I’ve developed a solution for this but I want to know whether anyone has a better approach. My solution is as follows;Whenever a Card is moved, we want the Make integration engine to process data. A webhook is setup accordingly. However, we need to ensure that;if the Make integration fails for whatever reason, then any further processing on Make is halted until the issue is resolved. if the Webhook fails to fire (it happens!), then any processing of subsequent Phase changes on Make is halted a warning message appears on the Pipefy Stage if any of the above conditions have occurredIgnoring the warning message, then this is the solution I’ve come up with;1. the Pipefy Pipe ha

4
mark-theotcentre
11 months ago
mark-theotcentre
mark-theotcentreNew Participant

Reporting a Bug: Field Conditionals do not trigger when the API updates a FieldSubmitted

Field conditionals are triggered whenever a user updates a field at the user interface. This ensures that when a user enters a value, Pipefy checks the “field conditionals” to determine whether any actions need to be taken based on the Conditional Rules.Great.However, when we update a field via the API, Field Conditionals are not triggered.This is either a known bug or a product limitation and desperately needs addressing.Thanks

16
natalia-manffre
Pipefy Staff
11 months ago
mark-theotcentre
mark-theotcentreNew Participant
asked in API

Dynamically populate permissible values for a Card or Phase drop-down field via API

We have a field on an external system which is a drop-down, for example;UK Counties:AvonCarmarthenshireetcWe want to ensure that the same field on a Pipefy Card has the same drop-down value list whenever the Card enters the Phase which has the County field.Does the Pipefy API allow us to dynamically create the drop-down options for a “dropdown select” field. We can’t work that out from the API documentation, sorry!Thanks

3
Lucas Democh
11 months ago
mark-theotcentre
mark-theotcentreNew Participant
asked in API

Field Update Webhook API and Pipefy Public Start Form

Can someone clarify for sure whether the Field Update Webhook is triggered when a field on the Start Form is updated.We are using Pipefy APIs and are finding that the Field Update Webhook *is* triggered when a field is updated on a Phase Form but does not trigger when a field is updated on a Public Start Form.I’m getting conflicting information on this!Thanks

4
Lucas Democh
11 months ago
mark-theotcentre
mark-theotcentreNew Participant

Field Updates on Public Start Forms should trigger the APISubmitted

At the moment, field updates on a Public Start Form do not trigger the API “Field Updated” Webhook.This is a very unfortunate limitation.Here are some examples of why this capability would be invaluable;customer fills out their postal code on the Start Form. This triggers a postcode lookup returning a list of corresponding addresses allowing the customer to select their address a returning customer enters their email address on the Start Form. This triggers a person lookup (eg on company CRM) which prefills the Start Form with the customer detailsCan we get this feature implemented pelase.

2
Priscila Rodrigues
Pipefy Staff
11 months ago
mark-theotcentre
mark-theotcentreNew Participant

Dynamic Fields need to refresh whenever a field is updatedSubmitted

Dynamic fields do not always refresh on an open Card.For example, a field hosted under the Start Form is updated from the API and that field is displayed on the Open Card via a dynamic field. The changed value is not displayed on the open card until the browser is refreshed or the Card is closed and re-opened.This is problematic when creating custom integrations which need to present real-time messages to a Card User via the open Card. Non-dynamic fields on an open card which are updated by the API show the changed value in real-time. This behaviour needs to be applied to Dynamic Fields also. 

4
Desirée Hoppe
Pipefy Staff
1 year ago
mark-theotcentre
mark-theotcentreNew Participant
asked in Customer Operations

Start Form Field Updates via Webhook API

We’re using the API for Field Updates and Card Moves. All good so far.However, when a Start Form field is updated, the field update webhook doesn’t seem to fire.Is this (an undocumented) limitation?Thanks for any help

1
Lais Laudari
Community Manager
1 year ago

Community Experts Leaderboard

Terms & ConditionsCookie settings