Create a journey to define a flow such as registration, authentication or payment. The definition connects the steps to process, the data to map and the assessment logic to run. See Journeys, steps & events if these terms are new.
In Workflows, work in the repository for your selected test node. For a website, the Journey Recorder can generate steps as you browse; this article explains manual creation and the configuration you should review either way. The result is a journey file ready to build and deploy—not a live change as soon as the file is saved.
Creating a new Journey
To create a new Journey, add a file into the root of the repository.
Journey files in root folder
Make sure to place all journey.yaml files in the project root folder
Where the journeys.yaml file is

The new Journey file must have the file extension ".journey.yaml".

If you accidentally create the file in a folder, you can simply drag the file to the root folder.
Activating your new Journey
To include the journey in a build, add it to "journeys.yaml" in the repository root. Review and deploy the built revision before expecting the journey to process live traffic.

Setting up a new Journey
Click on your newly created Journey file in the File Explorer to launch the Journey Editor. A newly created Journey file must have some initial configuration done before it can be used. Click on the Settings icon in the top right of the Journey Editor.

Give the Journey a name to uniquely identify it within the Journey Name setting.
Journey Cookie Configuration
Request cookies are used by Darwinium for both Journey Management and Device Identification.
Darwinium can create new Cookies or be instructed to use existing ones.
See profiling article for further advice on configuring those cookies.
Session cookie helps resolve a `journey_id` ; not needed if using a `*_tie` attribute or `journey_id` direct
Device cookie helps resolve a `profiling.device.identifier' ; highly suggested on web, not needed on mobile SDK
Adding a Step
When a Journey is first created is is empty. Use the Add button within the Journey Editor to add a new Step to the Journey.

Clicking on the newly created step will open the Step Editor within the right hand side of the Journey Editor.

You are now ready to Edit this and other steps on the journey.
See: Creating and Editing Steps.
(optional) Remove validation for non-card attributes
Darwinium has platform wide protection to refuse consuming potential card number into unrelated input attributes.
The event will still process, but attribute will be treated Null and will return a
422 Unprocessable EntitySpecific details are given in response attribute:
invalid_input_attributes
"invalid_input_attributes": {
"identity[ACCOUNT].account_number.account_number": "validate NonCreditCard failed A potential credit card number was provided. This cannot be processed by darwinium at this time. at line 27 column 40"
},However: some legitimate non-card attributes can require to be passed into an input field (eg. a generic customer number taking 16 digit format).
The validation on confirmed non-card input attributes can be skipped by listing them in the journey file:
confirmed_non_card_attributes:
- identity[BENEFICIARY].account_number.account_number
- identity[ACCOUNT].account_number.account_numberContinued assurance your side
Including attributes under confirmed_non_card_attributes is committing that now and continuously, no card details will ever appear under the mapping of those specific attributes.
After configuring the steps, follow Deployment confirmation and find a test event in Investigations.