{
    "generalData": {
        "displayName": "Test"
    },
    "description": {
        "about": "Test"
    },
    "documentMeta": {
        "documentLanguage": "sv",
        "documentAnonymous": false,
        "compactMode": false,
        "numberOfCategories": 1
    }
}

The variables documentLanguage and documentAnonymous do not have any values when document is generated…… but…. if we move it around like this:

{
    "documentMeta": {
        "documentLanguage": "sv",
        "documentAnonymous": false,
        "compactMode": false,
        "numberOfCategories": 1
    },
    "generalData": {
        "displayName": "Test"
    },
    "description": {
        "about": "Test"
    }
}

Then we do get values in the fields. “sv” and false.

I have presented a simplified version of the json which otherwise:

• Is json valid
• Has no repeating field names
• All camelCase
• Has max 3 levels in other data sections

Is there an END CUSTOMER signal that may have been automatically created that I have missed?

Can anyone explain it?

Fingers crossed.

Is there an posts that describes Exstreal Cloud Native Installation with Kubernetes servers.

I got many issues with that

And how you could run it with postman for testing.

We are looking into implementing our current solution into Exstream Cloud Native.

Our current solution is build on Communication Builder service, where we have one StoryTeller process exposed to StoryBoard and here we have created 200+ Themes which all have a Theme rule when to be triggered. The value which decide the Theme rule is coming from inputdata. All input data is delivered within one channel (HTTPS), one input = one output document

We know that Exstream CN work differently, but our goal is to do something similar as above, and to reuse both design elements and content across all, which should aim to have one basic design with the content placeholders, just like the StoryTeller and reuse this into many content Authors/communications. We want to reuse textfragments with and without merged data fields.

Bare with me if the naming is not quite correct for the Exstream CN world, but I hope you understand.

So I have some questions that I like to hear your opinion or guidance about:

1. How would you distingue the different document context, I don't whant to have all in one communication or group rules within Content Author. I like the idea of the current solution Theme where I can make changes to one Theme without making changes to another.
2. How can I select which Content Author/Communication to be triggered when the value of decision is coming from the input data (could properly also be available within the https header if needed)?
3. How would you build up your content, we have mostly text and images and lists which we want to reuse between documents context.

We are current working on latest Exstream CN version.

Hope to hear from some people who have some ideas, please :)