- Product documentation
- Latest updates
- Release Notes
- Getting Started
- Sending Messages
- Get started with messages
- Delivery best practices
- Key steps when creating a delivery
- Sending emails
- Sending messages on mobiles
- Sending push notifications
- Sending direct mail
- Using delivery templates
- Personalizing deliveries
- Using seed addresses
- Subscriptions and referrals
- Monitoring deliveries
- Tracking messages
- Deliverability management
- Content management module
- Orchestrating Campaigns
- Reporting
- Designing web content
- Web applications
- Editing HTML content
- Web forms
- Get started with web forms
- Using a web form template
- Adding fields to a web form
- Static elements in a web form
- Defining web forms layout
- Form rendering
- Defining web forms page sequencing
- Web forms answers
- Publishing a web form
- Defining web forms properties
- Translating a web form
- Use cases: web forms
- Online surveys
- Integrating with Adobe Experience Cloud
- Automating with Workflows
- Introduction
- General operation
- Executing a workflow
- Targeting activities
- Flow control activities
- Action activities
- About action activities
- Delivery
- Delivery control
- Continuous delivery
- Recurring delivery
- Cross-channel deliveries
- Local approval
- Data loading (RDBMS)
- Loading (SOAP)
- Data loading (file)
- Content Management
- Data extraction (file)
- SQL code and JavaScript code
- SQL Data Management
- Nlserver module
- Update aggregate
- Event activities
- Use cases
- Monitoring workflows
- Advanced management
- Technical workflows
- About technical workflows
- Deliveries
- Campaign
- Web Analytics
- Distributed Marketing
- Deliverability monitoring
- Inbox rendering
- Interaction
- Control of offer engine
- Message Center (Control)
- Message Center (Execution)
- Mobile App Channel
- LINE Channel
- Marketing Resources (MRM)
- Social Marketing
- Integrations with Adobe Experience Cloud solutions
- Privacy Data Protection Regulation
- Transfer to Mid-sourcing
- Mid-sourcing platform
- Managing Offers
- Transactional Messaging
- Integrating with Social media
- Installation and configuration guide
- Architecture principles
- Deployment guidelines
- Deployment types
- Campaign on Windows
- Campaign on Linux
- Initial configuration
- Additional configurations
- Accessing an external database
- Appendices
- Monitoring guide
- Introduction
- Production procedures
- Data processing
- Updating Adobe Campaign
- Database maintenance
- Troubleshooting
- Performance and throughput issues
- Images missing
- Image display issues
- Temporary files
- Database performances
- Modules and frequent issues
- Log precision
- Tracking logs issues
- Workflow execution
- Failure to connect
- Connection thresholds
- Stack trace in Linux
- Encoding of the Oracle database
- Console update
- Lost password
- JSP behavior
- Developers guide
- Migration guide
Technical workflows
You must ensure that the technical workflows on the control instance and the different execution instances have indeed been created and started before deploying any transactional message templates.
The various technical workflows related to transactional messaging (Message Center) are broken down between the control instance and the execution instance(s).
Control instance workflows
On the control instance, whether you have one or several execution instances registered, you must create one archiving workflow for each Message Center execution instance external account. Click the Create the archiving workflow button to create and start the workflow.
These workflows can then be accessed from the Administration > Production > Message Center folder. Once created, the archiving workflows are automatically started.
Execution instance workflows
On the execution instance(s), the technical workflows for transactional messaging can be accessed from the Administration > Production > Message Center folder. You just have to start them. The workflows in the list are:
-
Processing batch events (internal name: batchEventsProcessing ): this workflow lets you break down batch events in a queue before they are linked to a message template.
-
Processing real time events (internal name: rtEventsProcessing ): this workflow lets you break down real time events in a queue before they are linked to a message template.
-
Update event status (internal name: updateEventStatus ): this workflow lets you attribute a status to the event.
The following event statuses are available:
- Pending : the event is in the queue. No message template has been assigned to it yet.
- Pending delivery : the event is in the queue, a message template has been assigned to it and it is being processed by the delivery.
- Sent : this status is copied from the delivery logs. It means that the delivery has been sent.
- Ignored by the delivery : this status is copied from the delivery logs. It means that the delivery was ignored.
- Delivery failed : this status is copied from the delivery logs. It means that the delivery failed.
- Event not taken into account : the event could not be linked to a message template. The event will not be processed.