Configuration

Lime Admin

Activate default configuration

If you just want activate the default configuration you will need to press Save in Lime Admin->Settings->Basic Lead

It can look like it's filled/saved due to default values, but you need to press save to actually store it.

General Lead configuration

In the top section of the config you configure if you use person/company or both and what limetypes they represents in the lead flow. You can also configure which of the two should be required to be able to proceed to the next step.

Person/Company mapping

Here you configure what fields each object needs in the qualification step. Some of the fields are optional and can be set to - (Empty) in the configuration if you don't have/want them in the flow.

Limetype to transfer lead to

In the last step of the lead flow you'll create another limeobject to work with. In our default config it will be a deal, but can be configured to something else.

Warn user about ongoing "objects"

We can inform the user about ongoing objects (related to the person and/or company) to prevent duplicates when using the last "convert step" in the flow.

This is done by configuring the following properties:

• Ongoing filter - What filter that represents an ongoing object (For instance non-closed deals).
• Person/Company property - What relations on the Convert limetype to use to see if it's connected to the ongoing object.

It can look like this:

If there's no configuration for "Ongoing filter", the user will see a tip about configuring it:

Example of ongoing configuration:

By default these callouts will be visible in the Qualify dialog of the lead flow.

Want the warning to be seen on the lead card as well?

Then you can add the widget lwc-limepkg-basic-lead-callout-ongoing-convert-card to the card view config.

And use the following properties to set the size of the callout:

{
    "style": {
        "grid-column": "2 span"
    }
}

Field mapping - {Convert limetype}

Here you can specify what fields other than the Person relation that should be copied from the lead to the newly created object.

Some examples to transfer are Source, Company, Responsible coworker

Rejection - Follow up

When a lead is set to Rejection, you'll get a question if you want to follow up on the rejection.

Here you can set what default values that should be set on the follow up to-do.

Customize lead flow

You can change localization on fields and steps, but leave database names and keys.

Add more steps in the flow

It's possible to add new steps in the flow by adding them options on the leadstatus property, as long as the default ones remain the same.

These steps will only set the status and won't do anything special.

Customize steps in the flow

If you want to add more customized steps or change default behaviour on the existing steps you'll need to create your own command and configure it in the Status flow configuration.

You can then write custom logic for each step, and if you want the default behaviour for some of them you can just trigger the original command in your custom command.