Documentation for a newer release is available. View Latest
Esta página no está disponible actualmente en Español. Si lo necesita, póngase en contacto con el servicio de asistencia de Icon (correo electrónico)

Getting Started

Prerequisites

This starter guide assumes you have access to the following:

  • A flow which is preloaded with the IPF Business Functions.

Integrating with a flow

1. Add The duplicate check solution and model to your MPS solution and model

From within the flow you want to add the duplicate check to, press Ctrl+R twice. Search for and select the IPF Duplicate Check model from the search bar that opens.

Image of import model search bar for IPF duplicate check

Select OK in the pop up window asking if you would like to import the modules automatically.

The checkDuplicate domain function will now be available to use within your flow.

2. Use the check duplicate function within your flow

Use the checkDuplicate function within your flow in the same way as you would for a domain function you have defined yourself.

Image of check duplicate function being called from flow

You will need to define the input behaviour for all checkDuplicateResponse response codes and map to your chosen event selection.

Image of input behaviour defined for all response codes

You can find more details on using domain functions at DSL 3 - Using a Domain Function. This shows all the associated MPS based changes to fully use a function within your flow.

3. Add the ipf-duplicate-check-floclient-service dependency

Add the ipf-duplicate-check-floclient-service as a dependency to the module that includes the bean for your domain declaration. If you generated your project from the icon archetype this will be named <your-project-name>-service

    <dependency>
        <groupId>com.iconsolutions.ipf.businessfunctions.duplicatecheck</groupId>
        <artifactId>ipf-duplicate-check-floclient-service</artifactId>
    </dependency>

Providing Custom Purging Configuration

The Duplicate Check Floclient uses a TransactionCachePurgingScheduler with the following default configuration.

ipf.duplicate-check-floclient.purging {
  scheduling-specification = "0 0 0 ? * *"
  retain-from-time = "00:00:00"
  retain-from-offset = "0 days"
}

Provide your own values in your ipf-impl.conf or application.conf in order to custom the schedule to your needs.

You can find more details on providing configuration values for the TransactionCachePurgingScheduler in the transaction cache documentation.

Automated Retries

If the MongoDB instance providing the transaction cache fails to respond, or responds with a failure, no response to the checkDuplicate function call will be received by your flow.

You can implement Action Retries within your flow to manage such circumstances. DSL 7 - Handling Timeouts provides an example of their use.