Support all entity types in token replacements

Created on 7 March 2023, almost 2 years ago

Updated 11 August 2023, over 1 year ago

Problem/Motivation

Currently, only some entities are supported with the token replacement in email body, subject, or even the sender, any one have a custom entity will not be able to get the tokens for this custom entity.

Steps to reproduce

Create a custom entity and add a workflow field to it, then try to create an email notification, browse tokens and you will not get the tokens for your custom entity.

Proposed resolution

Support any type of custom entities

Remaining tasks

patch

User interface changes

none

API changes

none

Data model changes

✨ Feature request

Status

Fixed

Version

3.0

Component

Code

Created by

🇯🇴Jordan Anas_maw

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment over 1 year ago →
🇯🇴Jordan Anas_maw
I have been using the patch on a live website form more than 4 months without any issues, so I will mark it as RTBC
Comment over 1 year ago →
System Message

Anas_maw → authored 96e66786 on 3.0.x
Issue #3346429 by Anas_maw: Support all entity types in token...
Status changed to Fixed over 1 year ago3:12pm 11 August 2023
Comment over 1 year ago →
🇯🇴Jordan Anas_maw
Comment over 1 year ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024