Skip to main content

ResolveNotificationPlaceholdersNodeConfiguration

Namespace: Meshmakers.Octo.MeshAdapter.Nodes.Transform

Configuration for node ResolveNotificationPlaceholders@1.

One resolver for every send path, which is what AB#2569 asks for: "placeholder resolution must happen where the email is rendered, so that ALL send paths share one resolver". Before this, each send pipeline carried its own generated PlaceholderReplace@1 rule blocks plus hand-written converter nodes, so a fourth send path meant a fourth copy and a token wired in one pipeline but not another produced different mail from the same template.

A resolver pipeline called through ToPipelineDataEvent@1 awaitResult cannot be shared: that node requires the target to live in the same DataFlow and names its queues per DataFlow, and the send pipelines sit in three different ones.

Only the sources a path actually has are configured. A token whose source is not configured fails the node rather than rendering as a blank - see the node's own documentation.

public record ResolveNotificationPlaceholdersNodeConfiguration : NodeConfiguration, INodeConfiguration, IEquatable<NodeConfiguration>, IEquatable<ResolveNotificationPlaceholdersNodeConfiguration>

Inheritance Object → NodeConfiguration → ResolveNotificationPlaceholdersNodeConfiguration
Implements INodeConfiguration, IEquatable<NodeConfiguration>, IEquatable<ResolveNotificationPlaceholdersNodeConfiguration>

Properties​

SubjectPath​

Path to the subject template, as GetNotificationTemplate@1 wrote it.

public string SubjectPath { get; set; }

Property Value​

String

SubjectTargetPath​

Where the resolved subject is written.

public string SubjectTargetPath { get; set; }

Property Value​

String

BodyPath​

Path to the body template.

public string BodyPath { get; set; }

Property Value​

String

BodyTargetPath​

Where the resolved body is written.

public string BodyTargetPath { get; set; }

Property Value​

String

CustomerPath​

Path to the entity carrying the recipient's contact record - a customer on a bulk send, or the billing document itself on a dispatch, since the document keeps the contact snapshot the invoice was issued with.

public string CustomerPath { get; set; }

Property Value​

String

CommunityConfigPath​

Path to the community configuration entity.

public string CommunityConfigPath { get; set; }

Property Value​

String

BillingDocumentPath​

Path to the billing document, on a path that sends one.

public string BillingDocumentPath { get; set; }

Property Value​

String

RenderingTypePath​

Path to the template's rendering type, as written by GetNotificationTemplate@1.RenderingTypeTargetPath. Only an Html template can show the community logo; in a plain-text one that token renders as nothing rather than as markup the reader would see as characters.

public string RenderingTypePath { get; set; }

Property Value​

String

LogoContentId​

Content id the send node attaches the community image under, and which ${community.logo} addresses. Must match the attachment entry on SendEMail@2.

public string LogoContentId { get; set; }

Property Value​

String

Description​

public string Description { get; set; }

Property Value​

String

Constructors​

ResolveNotificationPlaceholdersNodeConfiguration()​

Caution​

Constructors of types with required members are not supported in this version of your compiler.

public ResolveNotificationPlaceholdersNodeConfiguration()