Workflow | Allow Re-enrollment based on 'updated in last' trigger

[romi]

On some properties there is the ability to trigger the workflow based on 'updated in last' x days.

However, it is not possible to use this to Re-enroll.

It would be exceptionally useful if:

1. 'updated in last' was available for all properties on all records
2. This trigger could be used for Re-enrollment

Solution

Turns out that the "is known" filter option on properties will do this, i.e. if you would like a workflow to be triggered when a property is updated, select the property 'is known' option and then select this under re-enrollement - every time the property is updated, the record will be re-enrolled

[romi]

Hi all,

I was in talks with our team to figure out if we can give a better estimate. It's as frustrating for us as it is for all our customers to have this discrepancy in features which is why we're working hard to finish that migration. Unfortunately it's dependent on a few other teams' work and we really have been working on this for over a year now! I still can't give an update but know that we haven't dropped this work at all, if anything we're ramping up to get it over the finish line. 

Sorry I couldn't give a better update, but thanks for checking in! I'll try to give an update again as soon as I hear of any progress we make,

Zeke

[romi]

@richardwalsh Yeah! The main reason is that while our contact workflows are now mostly in the new Workflows system, what drives enrollment events is a system (Lists) that is also undergoing a migration to a new system. All non-contact workflows are already using the new enrollment system which is why this feature only applies to those workflows. Once Lists finishes that migration, we will be able to bring this feature to contact workflows as well!

I don't have a timeline for the Lists migration, though it is an active project and something that us in the Workflows team are very excited about!

[romi]

Like some other functionality recently released, this will start being available for all workflows except Contacts.

[romi]

We are actively working on this feature and should be out soon! See below a screenshot of the upcoming functionality:

[Herschel]

This feature would be very useful for us as well.

[zeke]

We are actively working on this feature and should be out soon! See below a screenshot of the upcoming functionality:

[zeke]

Like some other functionality recently released, this will start being available for all workflows except Contacts.

[richardwalsh]

@zeke is there a specific reason as to why this won't roll out on contact workflows? Or is it just down the roadmap a bit for that object type?

[zeke]

@richardwalsh Yeah! The main reason is that while our contact workflows are now mostly in the new Workflows system, what drives enrollment events is a system (Lists) that is also undergoing a migration to a new system. All non-contact workflows are already using the new enrollment system which is why this feature only applies to those workflows. Once Lists finishes that migration, we will be able to bring this feature to contact workflows as well!

I don't have a timeline for the Lists migration, though it is an active project and something that us in the Workflows team are very excited about!

[Adam_D]

Hello guys, 

I have noticed that the option "updated in last X days" is still not available for contact workflows.

Can we please get an update about the migration? It has been a year since the last post here.

Thanks

Adam

[zeke]

Hi all,

I was in talks with our team to figure out if we can give a better estimate. It's as frustrating for us as it is for all our customers to have this discrepancy in features which is why we're working hard to finish that migration. Unfortunately it's dependent on a few other teams' work and we really have been working on this for over a year now! I still can't give an update but know that we haven't dropped this work at all, if anything we're ramping up to get it over the finish line. 

Sorry I couldn't give a better update, but thanks for checking in! I'll try to give an update again as soon as I hear of any progress we make,

Zeke