In the following example, you can define an application submission milestone by selecting an event type, primary key, and filters. The mandatory filters to limit the events for this milestones are Type, Application, Tier, andBusiness Transaction. The primary key is defined as loanId. Fields such as loanAmount, loanType, and customerEmail, are extracted in this milestone.

Similarly, the milestone for underwriting is defined with a different event type:

Since third-party service providers perform the underwriting, the status is updated in logs; Logsis considered the Typeof event source. To define a milestone, click + Add Milestone.

Occasionally the individual steps in a workflow, such as the application submission, can occur in different methods. You can differentiate these stages with unique filter conditions. For example, a user that submits an application through a browser performs the same action as a user that submits an application through mobile, but the filter conditions are uniquely defined. To track a milestone with several entry points, click + Add Event and define your mandatory filters (application, tier, and business transaction), primary key, and optional filter conditions, including your custom fields.

You can only define the entry points for milestones if the entry points are of the same event type; if one entry point is in Transaction and the other is in EUM, you cannot track the entry points under the same milestone.

Define your remaining milestones, validate, and save the Business Journey. It takes a few minutes to display the generated records from the associated events.