Replies posted by mark-theotcentre

17 Replies

mark-theotcentre
mark-theotcentreNew Participant

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

Update: This issue was fixed yesterday but unfortunately it isn’t working again.

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

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

@genietim that doesn’t sound good. What’s your experience of getting issues reported and resolved?

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

Field Update Webhook API and Pipefy Public Start Form

Public Form. My understanding now from Pipefy Support is that public forms don’t trigger the API.

4
Lucas Democh
1 year ago
mark-theotcentre
mark-theotcentreNew Participant

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

@genietim yes reported to support twice yesterday (via Pipefy Support Chat). The reason for posting here is my experience with Pipefy Support on Chat is terrible. The responses I got we’re ‘let me check that for you’ and then they disappeared - both times.Desperately hoping their team have some kind of eye on these forums ...

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

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

Hi guys, hope you are good! The best way to report some issue to our support team is through the chat inside the plataform as is the mainly channel to support our users. The email is not  the best way as there is no immediate follow-up and the message could be lost.@mark-theotcentre Are you still facing this issue?  I’m checking this issue and I will be back to you soon! @Lais Laudari Hi Lais, thanks for poking this. Yes the issue is still alive unfortunately. Field Conditionals do not trigger when a field is updated via the API. THis is a major issue for organisations using the API. Really need this fixed asap before we can go into production with our workflow

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

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

@mark-theotcentre I just confirm that its a bug and it has already been forwarded to the development team to be fixed as soon as possible.   @Lais Laudari Great, I think! But how do we get visibility on;what priority cases like this have when they are allocated for work

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

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

@Lais Laudari thanks for DMing the ID to me, much appreciated. I've never been given a case ID for any issue or help request I've placed with Pipefy either via chat or email

16
natalia-manffre
Pipefy Staff
11 months ago
mark-theotcentre
mark-theotcentreNew Participant
asked in Customs Apps & Integrations

Managing Asynchronous Communications with products like ZAPIER

This is a very nice writeup of an actual problem, thank you @mark-theotcentre  I am not using Make anmore but my own code to interact with the API, yet the problem is the same. In my case, I was fortunate enough to be able to restructure the workflow and the external automations such that they do not require previous webhooks to have occurred / i.e., they perform error correction where needed. In the worst case, using a similar procedure as you have but without hiding the fields, I just show the user a “Dynamic Content” field (an uneditable field) with a warning, that the state might not be current yet, and what the consequences of proceding anyway would be. I think, these problems are therefore very dependent on your dataflow / your pipe. Can you share any details, such that we might suggest an alternative?   Assuming there is no way to loosen your restrictions, I do not see a simpler solution than the one you have come up with. @genietim thanks for giving this some thought.The issue

4
mark-theotcentre
11 months ago
populohub
populohubNew Member

Be able to create a redirect on form submissionSubmitted

Argh. No redirect! Really?

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

Conditional FlowsSubmitted

Hi @marcosmelo  THanks for this, much appreciated. Unless I’m misunderstanding that implementation, then I agree it works *but* from a card user’s perspective it is confusing.For example, let’s say a card flow is Phase A → Phase B →Phase C → Phase D most of the time. But when a Card sits in Phase B and has a specific condition (based on Data in Phase A) then when the user submits the Card to Phase C, an Automation will skip Phase C and move it to Phase D.The problem I have is that in this circumstance, even though the card takes the correct route (skipping Phase C), I don’t want the user to see the “Phase C” button. It’s sometimes confusing when the user clicks the Phase C button only to discover that the card moved to Phase D.Or am I simply not implementing this in the right way? Appreciate your help. THanks

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

Parallel Flows

Hi @marcosmelo thanks! Kind of helps but it sometimes makes sense, conceptually, to have parallel phases within a Pipe rather than breaking out into parallel pipes. It would make Pipe design, implementation and maintenance eaasier.Incidentally, we use Database Connections and Pipe Connections using the Connect field on a particular Phase, but we’ve never created a connection on a whole Pipe - can you help me understand the difference (I read the article link you posted for me but I don’t quite get the difference between a connect field on created on a phase and a connection created on a whole pipe?)THanks again

3
marcosmelo
1 month ago
mark-theotcentre
mark-theotcentreNew Participant
asked in Ask the Community

Field Conditionals need to recognise 'current user'

Hi @marcosmelo thank you so much for your posts I really appreciate it.That’s interesting. We’ve used Phase Connections before but not in this way. I feel I’m missing a lot of opportunities with Pipefy perhaps due to my inflexible thinking and the Pipefy documentation isn’t always great at helping us translate the tools into effective solutions for real world scenarios. Are there documents or training videos you could particularly recommend.Meantime, I’ll create a separate connected Pipe for parallel approvals for this Pipe.Thanks again.

5
marcosmelo
1 month ago
mark-theotcentre
mark-theotcentreNew Participant
asked in Ask the Community

Field Conditionals need to recognise 'current user'

Hi @marcosmelo thanks again. I’ll check it out. I’ve been experimenting with you suggestion for Approvals by creating a separate Approvals Pipe. All makes sense but there are a couple of wrinkles I wonder whether you might offer some insight on?SoI’ve created an “Approvals” Pipe which (I’m hoping) will be re-used on any number of Pipes so I’m trying to keep the Approvals Pipe reasonably generic. I’ve connected the Pipe to the *phases* on the ‘parent’ Pipe which require approval (using the Pipe Connection field)THis all hangs together just fine, except;when an Approval is created from a Phase in the parent process, it isn’t possible to work out which phase in the parent pipe the approval came from. Is there any way we can grab this at the time the approval card is created? when an Approval request is processed with an outcome (eg Approved or Rejected) we can’t seem to find a way to message the requestor?Any help appreciated, many thanks 

5
marcosmelo
1 month ago
mark-theotcentre
mark-theotcentreNew Participant

Conditional FlowsSubmitted

Hi @marcosmelo thanks again, much appreciated. Yes we make comprehensive use of field conditionals and waterfall conditions. Best regards

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

Synchronize card's field with this fixed field

Hi @marcosmelo Thanks for replying to this post.I’m sorry I don’t quite understand this setting “Synchronize card fields with this fixed field” for the Assignee field. For example, when I disable “Synchronize card fields with this fixed field” on an Assignee field, the Card’s Assignee is still inherited from the Assignee Field?

6
marcosmelo
11 days ago
mark-theotcentre
mark-theotcentreNew Participant
asked in Ask the Community

Synchronize card's field with this fixed field

Hi @marcosmelo , thanks for bearing with me whilst I try to understand this better.TO be clear, we have two Assignee fields:The Assignee field in the card header An Assignee field in a PhaseIf I set “Synchronize card fields with this fixed field” (on the Phase field) to ON then I don’t see any difference in behaviour when I also set it to OFF?Kind regards 

6
marcosmelo
11 days ago
mark-theotcentre
mark-theotcentreNew Participant

Database Connection Fields: Usability ImprovementsSubmitted

New→Submitted @Priscila Rodrigues Hi, any progress. As a Pipfy subscriber it feels like ideas and bug fix requests fall into a black hole.With the current database functionality, we are having to create multiple databases as reference files when we could create one if Pipefy allowed filtering on Database Field Connections

4
mark-theotcentre
10 days ago

Community Experts Leaderboard

Terms & ConditionsCookie settings