Create your own journey case to extend the list of existing journeys and to meet your specific business needs.

You must perform these steps to make a new journey type available. For more information, see the list of available Journey types and subtypes.

Create a new class under the root class for your journeys in Pega Client Lifecycle Management and KYC.

For example, if you plan to create a specific journey to manage the renewal of documentation, you can create a class with the following characteristics:

The system refers to the class that you create in many different operations, and so the class must be registered under the D_AppExtension data page used by the application for DCR.

1. In the Application Explorer under the class PegaFS-Data-AppExtension, create a new Text property with the name WorkClass_<journey-type>. For example, WorkClass_DocumentCollection.
2. Open the data transform AppExtension_ExtSettings available at PegaFS-Data-AppExtension to set the value of the new property with the name of the class that you create.

As the last step of the registration, the class must be added to the map value MapForCustomerJourney.

1. If this is the first time that you create a new journey, copy the rule MapForCustomerJourney from the CLM layer (PegaCLMFS-Work-CLM) into your implementation layer. If this is not the first journey, the rule should already be there.
2. Open the rule in the implementation layer and add an entry setting the new journey type (for example, DocumentCollection) in the left column, and a reference to the new class in the right column (for example, D_AppExtension.WorkClass_DocumentCollection).

After creating the new class, you must create the three field value rules that register the class as a journey type, with the following attributes:

Users can trigger journeys on the existing customer through the Actions menu for customer search results. The Actions menu lists all journey types and subtypes applicable to that specific customer. The applicability of the journeys is driven by a set of when rules, which when executed against the customer data, determine which of the journeys should appear.

To add a journey type and subtype available in the Actions menu, create a new when rule. For example, to make your journey available only to active customers, create a when rule with the following parameters:

If you do not trigger your journey from the UI but create it by a background process (for example, a recurrent job, an external service call), create the when rule so that it always returns false.

In the same way that you determine when your journey type is available, you must specify the conditions that make your journey subtype available. For example, to make a journey subtype available only to your organization, create another when rule with the following parameters:

You can also create journeys on the customer profile screen, known as the Customer 360 or Master Profile screen. On the customer profile screen, the Actions menu in the top-right corner of the screen lists all journey types and subtypes applicable to that customer.

The Actions menu is rendered using the navigation rule PegaFS-Work.CustomerSearchActions. To add a new journey to that menu, complete the following steps:

1. Make a copy of the rule to your implementation layer. If this is not the first journey you create, you might already have a copy available.
2. Create a new entry in the navigation rule for the journey subtype that you want to add to the menu. For example, Periodic Document Collection.
3. Configure the visibility condition of the new entry with a new when rule that determines when the journey subtype is applicable. The when rule must apply to the class of your customer search case type. You can use the rule CanCreateNewPrincipalSubJourney as a reference.
4. Configure the following actions associated to the Click event that you associate with the new entry:

   Type	Expected value	Parameters
   Run Script	CallCLMFSBusyIndicator	Not applicable
   Run Data transform	CLMPassParameters	Journey: DocumentCollection JourneySubtype: DocumentCollectionPeriodic SetCustomerIDFromWorkContext: true
   Create Work	Not applicable	Target: Default ClassName: UPFS-MyApp-Work-CLM-DocumentCollection FlowName: pyStartCase

• Implementing case types