Configurator
Configurator lets you create, configure, and manage the processes that run through FIP solutions.
From this module you can:
View the available processes.
Create onboarding and authentication processes.
Configure their components and parameters.
Add and configure challenges.
Save processes as drafts.
Publish and unpublish processes.
Clone existing processes.
Archive and delete processes, depending on your permissions.
View the information needed to integrate a process.
Test a published process using demo mode.
Manage other configurations available for your tenant and your role.
Changes made in Configurator do not affect new executions until the corresponding configuration is published.
How it is organized
The main section of Configurator is Processes.
From there you can access the list of processes and open each one to view or modify its configuration.
Each process is defined, among other elements, by:
Its type.
The environment in which it runs.
The template used.
Its components.
The parameters for those components.
The configured challenges.
Its status.
Some additional configurations may be available depending on the contracted features and your profile permissions.
Access and permissions
The actions available depend on your role and the permissions associated with your profile.
Depending on your permissions, you can:
View processes.
Create processes.
Edit them.
Clone them.
Publish or unpublish them.
Archive them.
Delete them.
Run them in demo mode.
Access additional configurations.
When an action is not available for your user, it may remain hidden or disabled.
Published processes cannot be modified directly. If you need to change their configuration, you must first unpublish them when you have permission to do so.
View processes
Processes shows the processes available in the selected environment.
Each item in the list lets you identify the process, see its status, and access the available actions.
Search and filter processes
Use search to find a process by name.
When available, use filters to narrow the results by criteria such as:
Status.
Process type.
Environment.
Template.
Applied filters are shown above the list and can be removed individually.
Select Clear all to remove them all.
Results
Each process can show information such as:
Name.
Description.
Process ID.
Process type.
Environment.
Template.
Status.
Version.
Creation or modification date.
Depending on the view, indicators related to its usage may also appear.
Open a process
Select the process or the available view action.
Its detail view will open with the corresponding configuration.
The actions you can perform from the detail view depend on its status and your permissions.
No processes
When no processes exist yet, the list shows an empty state.
Select Create process to configure the first one.
New processes will appear in this list once created.
Process statuses
The status indicates where a process is in its lifecycle.
Draft
The process is being configured and is not yet available for new executions.
You can modify it and save changes until it is ready to be published.
Published
The process is published and can be used to start new executions.
The published version is immutable.
To make changes, you must first unpublish it when you have permission to do so.
Archived
The process has been removed from regular use, but it is kept in the system.
Depending on your permissions, you can restore it or delete it.
Create a process
Select Create process from the list.
Creation starts by defining the main characteristics of the process.
Select the process type
Select the type of flow you want to configure.
It can be:
Onboarding
Authentication
The selected type determines the templates and components that will be available.
Select the environment
Select where the process will run.
Available options may include:
Web.
iOS.
Android.
The environment determines the compatible components and configurations.
Select a template
Select the template that will serve as the initial configuration.
The template defines a base combination of:
Components.
Validations.
Parameters.
Dependencies.
Challenges, when applicable.
You can then modify the elements that are configurable.
Some values are defined by the process type, the environment, or the template and cannot be modified later.
Configure a process
Configuration is organized into different sections depending on the process type and the selected template.
It may include:
General information.
Terms & Conditions.
Components.
Parameters.
Challenges.
Additional technical configuration.
Editable fields
Editable fields let you change the configured value.
Each field can have:
An initial value.
A specific format.
An allowed range of values.
A minimum or maximum length.
The system validates the information before saving or publishing.
Read-only fields
Some values are shown but cannot be changed.
These fields represent configurations determined by:
The component type.
The template.
The environment.
The system itself.
A field that cannot be edited does not mean it is incomplete. Some values are part of the component's internal configuration and are shown only for reference.
System-managed values
Some parameters needed to run the process may not appear in the form because the system manages them automatically.
You do not need to configure them manually.
Validation of values
Fields accept only values that are compatible with their configuration.
If you enter a value outside the allowed range or with an incorrect format, correct it before saving or publishing.
Terms & Conditions
Terms & Conditions lets you configure the information the user must accept during the process.
The configuration may include:
Title.
Description.
Time available to complete the step.
There can only be one Terms & Conditions component within the same process.
If one already exists, you will not be able to add a second equivalent component.
Configure components
Components determine the captures, checks, and interactions that are part of the process.
The template includes an initial configuration that you can adapt within the allowed limits.
View a component
Each component shows its name, status, and available actions.
Depending on the component, you may find:
Edit
Disable
Restore
The available actions depend on its configuration and relationships with other components.
Edit a component
Select Edit to open its configuration.
Modify the available parameters and save the changes.
Select Cancel to close the edit without applying them.
Some parameters may appear as read-only because their value is determined by the system.
Disable a component
Select Disable when you want to keep the component within the configuration but prevent it from participating in execution.
Before disabling it, the system checks whether other components depend on it.
If it can be disabled, confirm the action.
The component remains visible in the configuration as disabled.
Dependencies between components
Some components need others to be active in order to work correctly.
For example, a validation may need a previous capture in order to have the information it must analyze.
When you try to disable a component with dependencies, the system informs you of the affected elements.
Depending on the relationship between them:
The action may be blocked.
It may be necessary to disable other components as well.
The system may request additional confirmation.
Always review the affected components before confirming a disable action. The change may modify the flow the user will experience.
Restore a component
Select Restore to reactivate a disabled component.
The system checks its dependencies before restoring it.
When other related components are also disabled, it may be necessary to restore them to recover the configuration correctly.
Depending on the case, the interface may allow:
Restore only the selected component.
Also restore the components needed to satisfy its dependencies.
Review the information shown before confirming.
After restoring it, the component once again takes part in the process execution.
Required components
Some components are necessary for the template to work correctly.
When a component is required:
It cannot be disabled, or
The action appears blocked.
The interface indicates when a configuration is necessary to keep the flow valid.
Configure challenges
Challenges let you add additional checks to the process.
The available ones depend on:
The process type.
The template.
The environment.
The enabled features.
Add a challenge
Select the challenge you want to add and complete the available parameters.
Each challenge can have its own:
Fields.
Initial values.
Ranges.
Limits.
Dependencies.
Edit a challenge
Select Edit to modify its parameters.
The system validates that the new values are compatible before saving.
Disable a challenge
When this action is available, select Disable to keep the challenge configured without running it.
The challenge remains visible, but stops participating in the process while it is disabled.
Restore a challenge
Select Restore to add it back into execution.
The system restores its configuration and checks the necessary dependencies.
Execution order
When the process contains several challenges, their order determines the sequence in which they can be executed.
If the interface allows you to change that order, arrange the challenges according to the expected behavior before publishing.
Save a process
You can save the configuration while working on it without needing to publish it.
Select the available save action.
The process remains in state Draft until it is published.
Validation errors
A process can be saved as a draft even if it still needs adjustments.
However, certain errors prevent it from being published.
Before publishing, review:
Required fields.
Values out of range.
Required components.
Dependencies.
Incomplete configurations.
Save and publish are different actions. Saving preserves the configuration; publishing makes it available for new executions.
Clone a process
Select Clone when you want to create a new process from an existing configuration.
The clone is created as a process independent of the original.
Use this option when you want to reuse a configuration as a starting point without modifying the existing process.
After cloning it:
Open the new process.
Review its identifying data.
Check the inherited components and parameters.
Review the challenges and dependencies.
Make the necessary changes.
Publish the new process when it is ready.
Changes made in the clone do not affect the original process.
Before publishing a cloned process, review all its configuration. A configuration valid for one process may need adjustments before being reused in another context.
Publish a process
Publishing makes a version of the process available for new executions.
Select Publish when the configuration is complete.
Validations before publishing
Before allowing publication, the system checks that the process is valid.
It can verify:
Required fields.
Required components.
Dependencies.
Configured values.
Challenges.
Other template requirements.
If there is any issue, correct the indicated elements before trying again.
Confirm publication
Select Publish and review the confirmation.
After publishing:
The process changes to Published.
An immutable version is created.
That version becomes available for new executions.
The published configuration cannot be edited directly.
Process versions
Each publication generates a version of the configuration.
Operations keep the reference to the version they were run with.
This allows a previous operation to continue representing exactly the configuration used at that time, even if the process changes later.
Modify a published process
To modify a Published process:
Unpublish it, when you have permission.
Make the necessary changes.
Save the configuration.
Validate the process again.
Publish it.
The new publication generates a new version.
Previous operations remain linked to their original versions.
The history and visual comparison between versions are not part of the current functionality.
Unpublish a process
Select Unpublish to prevent the process from continuing to be used to start new executions.
This action may be limited to certain roles.
Before confirming, review the impact of unpublishing the process.
After unpublishing it:
No new executions can be started with the removed version.
The configuration can be modified again when your permissions allow it.
Operations already started or recorded retain the information of the version used.
When you publish the configuration again, a new version will be generated where applicable.
Archive a process
Select Archive when you want to remove a process from regular use without deleting it permanently.
The system asks for confirmation before completing the action.
After archiving it:
The process no longer appears among active processes.
Its configuration is preserved.
Previous operations remain linked to their versions.
Depending on your permissions, you may later restore an archived process.
Delete a process
Deletion is available only when the status and your permissions allow it.
Select Delete and review the confirmation modal.
After confirming, the process is no longer available for regular management.
The evidence and references necessary to maintain the traceability of previous operations are not modified.
Deleting a process is an irreversible action from the interface. Use Archive when you need to remove it without losing the possibility of recovering it.
Process detail
The detail allows you to view a process's configuration and execute the available actions.
It can show:
Name.
Description.
Process ID.
Process type.
Environment.
Template.
Status.
Version.
Components.
Challenges.
Associated technical information.
Copy the Process ID
Select the copy icon next to the Process ID.
Use this identifier when you need to reference the process during an Integration or a technical query.
Available actions
Depending on the status and your permissions, from the detail you can find actions such as:
Edit.
Clone.
Publish.
Unpublish.
Archive.
Delete.
Demo.
Test a process in demo mode
Demo mode allows you to run a published process before using it in a real Integration.
The action is only available when:
There is a Published Version.
Demo mode is enabled.
Your profile has the necessary permissions.
Open the demo
Select the corresponding action from the process.
A modal will open with:
Process information.
QR Code.
Instructions to start the demo.
Web Demo
To run a Web process:
Open the indicated demo URL from a mobile device.
Use the camera to scan the QR Code.
Complete the process.
Mobile Demo
For a Mobile process, use the corresponding demo app and scan the QR Code when indicated.
QR validity
The QR Code associated with the process:
It is persistent.
It can be reused.
It does not expire.
It is not consumed after an execution.
It is not invalidated when closing the modal.
It does not need to be regenerated.
The same QR Code runs the Version Published that is active at that time.
If you publish a new Version, the QR Code uses that new Version.
What happens when unpublishing
When the process does not have an active Published Version, the QR Code stops starting new demos.
It is not necessary to generate another code.
When there is again a Published Version, the same QR Code can be used again.
The QR Code identifies the process, not a specific execution. That is why it can be used several times as long as there is a published version.
Additional configurations
Depending on the contracted features and your profile permissions, Configurator may include other configuration areas.
These surfaces can manage elements that affect more than one process.
Only consult the options available in your tenant and avoid modifying global configurations without first reviewing their impact.
Create and publish a process
As a reference, the usual Flow for preparing a process is:
Open Processes.
Select Create process.
Choose the process type.
Select the environment.
Choose a template.
Complete the required information.
Review Terms & Conditions.
Configure the components.
Check the dependencies.
Configure the challenges.
Save the process.
Correct any validation errors.
Select Publish.
Confirm the publication.
Check the process using demo mode.
Use the Process ID and the necessary technical information to perform the Integration.
Before publishing, review the full Flow and make sure the configuration matches the experience you want to offer the user.
Last updated