Business Workflows Processor

The Business Workflows Processor uses rules-driven business transitions between statuses to help a bank generate reports and see what is the status of a user, customer, bank account and more. It renders the status of a record in the workflow in its life cycle. For the Online and Mobile Banking, there are multiple flows for several entities.

User Enrolment and Administration

FTOS_IB_UserEnrolment_Flow

The name is FTOS_IB_UserEnrolment_Flow attached to the entity FTOS_IB_UsersEnrollment.

It has the following statuses:

Status Description
Initiated When the online process has started and the information from the first step has been saved.
Dropped When the user does not finish the request online, does not confirm the email or on the mobile phone number using the OTPClosed One-Time-Password. It is a password generated by the system to validate a piece of information or sign a document. sent via SMS.
Requested When the online request has been registered, the user is on the confirmation page (after the email and phone have been confirmed by the user).
Confirmed When the user visits the branch and the bank employee marks the request as Confirmed in the FintechOS environment.
Not confirmed The user did not visit the branch or the bank employee did not mark the request as Confirmed in the FintechOS environment.

FTOS_IB_UserXCustomer_Flow

The name is FTOS_IB_UserXCustomer_Flow attached to the entity FTOS_IB_UserXCustomer.

It has the following statuses:

Status Description
Initiated The initial status of the User – Customer relation when the association is done by the Financial Institution’s employee.
Active The status of the relation after the approval of the Checker. Any record in Active status is a production working status.
Modified Records are automatically set to Modified when the Maker wants to change something which is already Active. The Modified records need to be Approved in order to become Active again.
Manually Blocked The UserxCustomer relation is blocked by the back-office.
To be inactivated Records are manually set to To Be Inactivated by the maker when they want to disable the user for that customer.
Inactive The modification needs to be Approved in order to become Inactive. Any record in the inactive status no longer has effect in production.
  

FTOS_IB_UserxBankAccount_Flow

The workflow named FTOS_IB_UserxBankAccount_Flow is attached to the entity FTOS_IB_UserXBankAccount

It has the following statuses:

StatusDescription
  • Initiated
    		• The record UserxBankAccount has been created.
  • Active
    		• The record UserxBankAccount is valid and can be used in the Customer List.
  • Modified
    		• The an element from the record UserxBankAccount has been modified.
  • To be inactivated
    		• The record UserxBankAccount will be inactivated by a checker.
    InactiveThe record UserxBankAccount is inactive and, therefore, cannot be used furthermore.

    FTOS_IB_UserXTransactionType_Flow

    The workflow named FTOS_IB_UserXTransactionType_Flow is attached to the entity FTOS_IB_UserXTransactionType.

    It has the following statuses:

    StatusDescription
  • Initiated
    		• The record UserxTranscationType has been created.
  • Active
    		• The record UserxTransactionType is valid and can be used in the Account/Transaction Selection.
  • Modified
    		• The an element from the record UserxTransactionType has been modified.
  • To be inactivated
    		• The record UserxTransactionType will be inactivated by a checker.
    InactiveThe record UserxTransactionType is inactive and, therefore, cannot be used furthermore.
     

    Homepage of Online and Mobile Banking application

    FTOS_IB_ChangePassword_Flow

    The business workflow named FTOS_IB_ChangePassword_Flow is attached to the entity FTOS_IB_ChangePassword.

    It has the following statuses:

    Name

    Description

    Initialized

    The process of changing a user's password was commenced.

    OTP in Progress

    The One-Time_Password was sent.

    Phone Confirmed

    The user inserted the OTP successfully.

    Password change in Progress

    The password is changing.

    Password Changed

    The password was changed.

    Final Rejected

    The phone number was not confirmed or the password was not changed.

    Signature Engine

    FTOS_IB_SigEngcustomerRules

    The business workflow named FTOS_IB_SigEngRule is attached to the entity FTOS_IB_SigEngcustomerRules.

    It has the following statuses:

    StatusDescription
    InitiatedWhen a new rule is created it has automatically the status initiated.
    Active Once the rule has been approved, it passes from Initiated to Active, hence, the record is valid for use. All transactions for that customer/group of customers are evaluated for authorization based on all active rules.
    ModifiedThe rule that has been modified by the maker and that will require approval to become Active again.
    To be inactivatedThe maker wishes to make the rule inactive and requires approval for the transition to the last status.
    InactiveA rule which is no longer use in production or it has never been used in production.

    Payments

    FTOS_IB_Payment_Flow

    The business workflow named FTOS_IB_Payment_Flow is attached to the entity FTOS_IB_Payment.

    It has the following statuses:

    StatusDescription
    DraftThe first status of the payment which matches the Make a payment screen.
    InitiatedThe status of the payment after the "Review payment'' button has been clicked.
    AuthorizationRequiredAn authorization is required for payment to go through.
    CanceledThe status when the user quits the flow.
    ExecutedThe payment is done.
    AuthorizedThe payment was authorized by a user ( for single signature/utility payments) or only when all the required signature (joint signatures) are received.
    PendingAvailableBalanceRecords are manually set to To Be Inactivated by the maker when they want to disable the User for that Customer.
    RejectedThe system rejected the payment.
    SentToCorebankingThe modification needs to be Approved to become Inactive. Any record in the inactive status no longer has effect in production.
     

    On the transition SentToCorebanking_Executed, there is an Action Group configured named FTOS_IB_SyncAccountListActionGroup with the Entity Workflow Transition Action:

    Field

    Data Type

    		Description

    Name

    Text

    FTOS_IB_RefreshAccountDataOnExecuted

    Code

    Text

    FTOS_IB_RefreshAccountDataOnExecuted

    Action Stage

    Option set

    After

    Apply Always

    Bool

    		TRUE

    Action Type

    Option set

    Run Custom Script

    Custom Script

    JSON

    		The code executed.
     

    FTOS_IB_PaymentsQueue_Flow

    The business workflow named FTOS_IB_PaymentsQueue_Flow is attached to the entity FTOS_IB_PaymentsQueue.

    It has the following statuses:

    StatusDescription
    Authorized When a payment has the status Authorized in FTOS_IB_Payment, a new record is created in the queue.
    SentToCorebanking When a payment has the status Authorized in FTOS_IB_Payment, a new record is created in the queue.
    PendingAvailableBalanceWhen the status in FTOS_IB_PaymentQueue becomes Pending available amount, then the payment status in FTOS_IB_Payment changes to Pending available amount.
    Rejected When the status in FTOS_IB_PaymentQueue becomes Rejected, then the payment status in FTOS_IB_Payment changes to Rejected.
    Executed When the status in FTOS_IB_PaymentQueue becomes Executed, then the payment status in FTOS_IB_Payment changes to Executed.

    FTOS_IB_UtilityPaymentContract_Flow

    The workflow named FTOS_IB_UtilityPaymentContract_Flow is attached to the entity FTOS_IB_UtilityPaymentContract.

    It has the following statuses:

    StatusDescription
    InitiatedThe payment of a contract has been initiated.
    Authorization requiredThe payment needs to be authorized.
    AuthorizedThe payment has been authorized.
     

    Bulk Payments

    FTOS_IB_BulkFiles_Flow

    The workflow is named FTOS_IB_BulkFiles_Flow and it is attached to the entity FTOS_IB_BulkFiles.

    It has the following statuses:

    StatusDescription
    ImportedThe file has been imported into the system.
    Format ErrorThere is an error with the way in which the file was written, therefore, it was not imported.
    Validated onlineThe file was validated.
    Under Core ValidationThe file is analyzed by Core Banking.
    Core errorCore Banking has returned an error.
    Validated CoreCore Banking has validated the payments.
    AuthorizedThe bulk payments have been approved.
    SentThe payments have been sent.
    SuccessfulThe payment has been executed successfully.
    Rejected CoreCore Banking has rejected the file.

    Template Beneficiaries

    FTOS_IB_Templates_Flow

    The workflow named FTOS_IB_Templates_Flow is attached to the entity FTOS_IB_Templates.

    It has the following statuses:

    StatusDescription
    ActiveThe template is available to be used in future payment.
    InactiveA template that holds an obsolete (missing or unusable value) detail(s) which prevents the using in the payment.
    DeletedThe template was deleted by the user and no longer available for future use in a payment.
     

    For more details, see Business Workflow.

    FTOS_IB_Mail_Out_Message

    The business workflow named FTOS_IB_Mail_Out_Messages is attached to FTOS_IB_Mailbox_OUT_Messages.

    Status Description
    Sent to Bank The status of a message after it was sent by the user. 
     

    FTOS_IB_Mail_In_Message

    The business workflow named FTOS_IB_Mail_In_Messages is attached to FTOS_IB_Mailbox_IN_Messages.

    Status

    Description

    Sent to Mailbox Final status for a message delivered in Mailbox list and that has not been opened. It applies to pop-up messages that need to be accepted to access the homepage to be granted. If message is accepted, the next status is Read.
    Read Final status for a message delivered in Mailbox list and that has been opened at least one time.