Set Journeys, Scope, and the Landing Page

In these exercises, you send each kind of transaction through the right workflows, change step names and sections by transaction type, and choose the page users land on. For every option, see Editor Page and Scope, Access, and Conditions.

19. Journeys

Task: Send renewals and changes through the quote's workflows, and give cancellations and reinstatements short workflows of their own.
Look at: After you deploy, create a renewal and a cancellation; a transaction keeps the workflow it started in, so one created before this exercise still shows the quote's steps. On Policy Details, choose "Renew" in the actions menu (⋮), and look at the renewal's step list. Go back to Policy Details, choose "Cancel", select a reason, click "Start Cancellation", and look at its step list. Don't issue either one.
Where: pages.editor.journeys in products/HO3/config.json.

Before

After

What you can use (see Journeys and Scope):

One product editor serves quotes and every transaction.
scope on a journey: quote, or transaction.<category> (change, renewal, cancellation, reinstatement, aggregate; see Policy Transactions)
The first journey that matches wins, so put specific journeys before general ones.
A quote or transaction that matches no journey gets every workflow, in the order of the workflows keys. End with a journey that has no scope as the fallback.

Hint

The first two journeys:

{
	"journeys": [
		{
			"scope": ["quote"],
			"workflows": ["submission", "underwriting", "issuance"]
		},
		{
			"scope": ["transaction.change", "transaction.renewal"],
			"workflows": ["submission", "underwriting", "issuance"]
		}
	]
}

The answer also adds the cancellation and reinstatement workflows, and ends the list with a journey that has no scope.

Answer: ex-19 (what changed)

20. Scope: Vary by Transaction Type

Task: Title the first step Submission Details on a quote and Renewal Details on a renewal, and show a matching first section on each.
Look at: The renewal from exercise 19, first step (open it from the policy's history if you closed it).
Where: The first step's name and first section in products/HO3/config.json.

Before

After

What you can use (see Scope and Gated Variants):

A list of variants wherever a value can differ: the first whose scope matches wins; a last entry with no scope is the default.
Variants work on journeys, step names, section slots, section titles, and menus. Buttons aren't variant lists: each button carries its own scope, so add one button per transaction type (see Buttons and Navigation).
Selectors: quote, policy, transaction, transaction.<category>, transaction.<category>.<type>; ! excludes a selector, as in ["transaction.cancellation", "!transaction.cancellation.non_payment_premium"]
Scope narrows going down: a section can't apply to more than its step does.

Hint

The step's name, as variants:

{
	"name": [
		{
			"scope": ["quote"],
			"name": "Submission Details"
		},
		{
			"scope": ["transaction.renewal"],
			"name": "Renewal Details"
		},
		{
			"scope": ["transaction.change", "transaction.aggregate"],
			"name": "Midterm Adjustment Details"
		},
		{ "name": "Quote Details" }
	]
}

The answer also gives renewals and changes their own names on the later steps, their own titles on the "Generate Quote", "Bind Quote", and "Issue Policy" buttons, and a transaction menu with "Reset" and "Discard" beside exercise 14's quote menu.

Answer: ex-20 (what changed)

21. Landing Page

Task: Make the operations home, where the dashboard shows, the page users land on after they log in.
Look at: Log out and back in, or click "Dashboard" in the top bar.
Where: A new file, userExperiences/config.json.

After

What you can use (see Landing Page and Dashboard):

defaultLanding: operations, lastAccessedTenantWorkManagement, or lastAccessedTenantAccounts
landings: a landing page per role, as { role, page }; the first match wins.
The dashboard comes from plugins/config.json, which the starting configuration includes because the tenant configuration has work management tasks. If you remove its dashboard entry, users land on the Operations Workbench's default landing page instead.

Hint

{
	"defaultLanding": "operations"
}

Answer: ex-21 (what changed)

What You Built

In this tutorial, we built a UI configuration for a homeowners product, starting from a minimal one. Along the way, we configured fields and sections, a quote editor with workflows and buttons, an exposure editor, the policy and account pages, and journeys and scope by transaction type.

The same concepts apply to any product. Use the finished configuration as a reference when you build the UI configuration for your own.

Set Journeys, Scope, and the Landing Page

19. Journeys

20. Scope: Vary by Transaction Type

21. Landing Page

What You Built

Next Steps

See Also

On this page