The workflows detailed below are installed by default.
|Reporting aggregates||reportingAggregates||This workflow updates aggregates used in reports. It is triggered every day at 2am by default.|
|Billing||billing||This workflow sends the system activity report to the 'billing' operator by email. It is triggered the 25th of every month by default.|
|Number of active billing profiles||billingActiveContactCount|
This wokflow counts the number of active profiles. It is triggered every night at 1am by default.
“ Profile ” means a record of information (e.g.: a record in the nmsRecipient table or an external table containing a cookie ID, Customer ID, mobile identifier or other information relevant to a particular channel) representing an end-customer, prospect, or lead. Billing only concerns Profiles that are “active”. A Profile is considered “active” if the Profile has been targeted or communicated within the past 12 months via any channel.
Facebook and Twitter channels are not taken into account.
You can have an overview of the Number of active profiles from the Administration > Campaign Management > Customer metrics menu.
|Alias cleansing||aliasCleansing||This workflow standardizes enumeration values. It is triggered every day at 3am by default.|
|Update for deliverability||deliverabilityUpdate||This workflow lets you create the list of bounce mail qualification rules, as well as the list of domains and MXs in the platform. This workflow only works if the HTTPS port is open. These lists are not updated unless the Deliverability module is installed.|
This workflow is the database maintenance workflow: it makes different calculations from the statistics and processes, and deletes obsolete data from the database according to the defined configuration in the deployment assistant. It is triggered every day at 4am by default.
For more information, refer to this page .
|Paused workflows cleanup||cleanupPausedWorkflows|
This workflow analyzes paused workflows that have severity set to normal and triggers warnings and notifications when they have been paused for too long. After a month, paused technical workflows are stopped unconditionally. By default, it is triggered every Monday at 5 am.
For more information, refer to Handling of paused workflows .
|Offer notification||offerMgt||This workflow deploys approved offers onto the online environment, as well as every category contained in the offer catalog.|
|Preview||forecasting||This workflow analyzes deliveries saved in the provisional calendar (creates provisional logs). It is triggered every day at 1am by default.|
|Tracking||tracking||This workflow performs the recovery and consolidation of tracking information. It also assures the recalculation of tracking and delivery statistics, especially those used by Message Center archiving workflows. By default, it is triggered once per hour.|