Create your own email

Jedox

Fill in the form, watch the email build, then download a tested Groovy script. Nothing you type leaves your browser.

This builder writes the same Groovy job as the Automated value emails post, with your wording in it. The script is generated from the tested version in that post, so the safety rules come with it: {{...}} markers instead of ${...}, single-quoted strings only, every value escaped, and test mode on by default.

The preview uses the site's made-up sample data. Your real emails will show your own cube's numbers. Every address in the examples is on example.com.

Email format

HTML email with a styled table.

Send one email per

Pick the dimension whose owners get their own email. It has to be a real dimension of your cube, not an attribute or a consolidation above it.

In the script and in recipients.csv, this is still called cost_center and {{COST_CENTER}}. Only the words around it change, so the tested code stays the same.

Subject job variable

Becomes the SUBJECT_TEMPLATE job variable. Use the markers below for values that change per email.

Markers you can use

Type these exactly, with two curly braces on each side. The script fills them in for each email.

{{COST_CENTER}}
{{COST_CENTER_NAME}}
{{OWNER_NAME}}
{{OWNER_EMAIL}}
{{PERIOD}}
{{VERSION_PLAN}}
{{VERSION_ACTUAL}}

Use {{...}}, never ${...}. Integrator replaces ${...} in job scripts before your code runs.

Greeting

The first line of the email. {{OWNER_NAME}} comes from recipients.csv.

Intro

One or two sentences above the table.

Columns

Account · Budget · Actual · Variance

These four columns are fixed in this version. Variance is Actual minus Budget.

Note under the table

A short line that explains the numbers. Leave it empty to skip it.

Footer

Every email goes to the test address. The subject starts with [TEST for owner.cc4010@example.com], so you can see who it was meant for.

The script is the same either way. It only changes the default you download. We recommend keeping it on and switching TEST_MODE to false in Jedox for one run when you're ready.

Test address job variable

Becomes the RECIPIENT_TEST job variable. Use your own mailbox when you run it in Jedox.

More settings

Period job variable

The month to report, as a Period element, for example 2026-03. Becomes PERIOD.

Plan version job variable

The version you compare against, for example Budget or Forecast. Becomes VERSION_PLAN.

Actual version job variable

Usually Actual. Becomes VERSION_ACTUAL.

Colors a variance when it's bad news for that account type. Becomes COLOR_VARIANCE.

Extract name job variable

The name of your Cube extract. Becomes SOURCE_EXTRACT.

Sample data: cost center CC4010, March 2026. In test mode the real subject also starts with [TEST for ...].

This is the job script. Paste it into a Groovy job in your Integrator project.

This is email-template.html. Put it in the local files folder. Keep all 12 {{...}} markers.

Next: run it in Jedox in test mode first

Put email-template.html, recipients.csv, dim_account.csv and dim_cost_center.csv in the local files folder. Create the four File connections: EmailTemplate, EmailRecipients, Accounts and CostCenters.
Create the Cube extract with Base elements only turned on and empty cells set to excludeEmpty, then run its preview. Check that the column names match the script. The value column's name isn't stated in the Cube extract docs, so check it in the preview; the script expects #Value.
Create a Groovy job, paste the script and add the job variables. Leave TEST_MODE set to true.
Run the job. Every email goes to your test address. Open them in Outlook, in web mail and on a phone.
When they look right, set TEST_MODE to false for that one run only, not in the variable's default.

If mail doesn't arrive, check the mail settings in Cloud Console. Since Jedox 24.2, the SMTP server and the From address are set there, not in the script.

The Automated value emails post walks through each step.