Introductions to FLEX Ten

FLEX Ten FLEX Ten Quick References Introductions to FLEX Ten

FLEX Ten represents a significant evolution of the FLEX system, moving towards a browser-based environment with a focus on speed, user experience, and phased implementation. This document outlines its key features, operational changes, and deployment approach for the benefit of FLEX users.

1. What is FLEX Ten?

FLEX Ten is a browser-based program that can also be loaded as a desktop application. It is designed to work in conjunction with the current FLEX product (Juice), allowing users to simultaneously use both systems. This approach is part of FLEX’s plan for a staged implementation.

  • Browser-Based and Desktop App: Access FLEX Ten via a web browser, and IT groups can configure it as an app on the desktop for direct engagement.
  • Simultaneous Use: You can toggle between FLEX Ten and the current FLEX product to perform different processes. For instance, tellers can use FLEX Ten, while back-office tasks like maintenance might still be done in the current FLEX product until those modules are available in FLEX Ten.
  • Data Flow: Changes made in the current FLEX product flow to FLEX Ten, and teller transactions performed in FLEX Ten flow back to the current FLEX product for balancing and viewing.
  • Work in Progress: FLEX Ten is an ongoing project, not yet 100% complete. Implementation is occurring in stages as modules become available.

2. Key Advantages and Considerations

FLEX Ten introduces several enhancements, particularly in performance and user experience.

  • Speed: FLEX Ten is “super fast” compared to the current FLEX product, especially beneficial for branches with connection speed issues. Being browser-based, it results in fewer trips back to the servers, significantly improving speed.
  • Security: While browser-based, FLEX Ten is directly linked to your servers and IP addresses through firewalls, not a public address. For detailed security settings and lockdown procedures, users are advised to contact the FLEX hardware team or marketing representatives.
  • Tablet Technology Integration:
    • Tablets are used in FLEX Ten for signature capture.
    • Important Caveat: Once tablets are implemented with FLEX Ten on teller lines, users must stay in FLEX Ten for signature capture, as tablets are not backwards compatible with the Juice product. Signature pads (SIGP pads) work in FLEX Ten, but tablets do not work in Juice.
    • Tablets allow signing with a finger, display transactions, can present marketing messages, and take photographs of the person at the teller.
    • Larger tablets can be incorporated into lending platforms for digital form signing.

3. User Interface (UI) and Experience (UX) Changes

FLEX Ten introduces a redesigned interface for improved usability and efficiency.

  • Verbiage Change: The term “teller” is replaced with “user” throughout the system.
  • User Profiles & Security:
    • Login profiles remain numeric or alphanumeric, starting with a number.
    • Passwords are the same across both FLEX Ten and the current FLEX product, requiring no unique login for FLEX Ten.
    • All current security settings and transaction limitations are enforced within FLEX Ten.
    • Differences in settings among credit unions may require calling the support team for assistance.
  • Dashboard and Navigation:
    • Upon login, users are directed to a dashboard.
    • The dashboard includes FLEX Academy access and a customizable message board (widgets) controlled by administrative teams.
    • The main menu is on the left.
    • Notifications and messages work differently, with overrides and job completion messages appearing as notifications [8, see previous documentation on AT/CD].
    • User profile settings allow customization of hotkeys, light/dark mode, cash machine interfaces, and password changes.
  • Account Search and Linking (Critical!):
    • Faster Search: Account lookups by name or account number are significantly faster.
    • Account Linking is Paramount: FLEX Ten excels at showing multiple account records in a single view.
      • If staff have skipped the linking step in the current FLEX product when opening new accounts or making address changes, these links are broken and will not display in the single view.
      • A blue bar in search results indicates a primary account holder or someone with a social security number on the system.
      • Ideally, all accounts for one person (primary, joint, co-borrower, authorized signer) should appear under one blue header.
      • Multiple blue headers for the same person (e.g., same social security number) indicate broken links, meaning not all accounts will be visible when navigating to one.
      • FLEX will assist with addressing linking issues during implementation, including automated programs for large jobs.
      • All tracking in FLEX Ten is done by social security number, not just name or account number.
      • Users should navigate into the person they are doing business with, not just the account number, for proper validation.
  • Validation Steps:
    • A validation screen may appear based on credit union settings, potentially asking for a keyword or requiring note verifications.
    • Force notes will always be displayed at the bottom panel and require staff engagement (clicking on the note) before proceeding.
  • Account Inquiry and Transaction Entry Screen:
    • The screen layout shifts from up/down paneling to left/right paneling.
    • The member panel is typically on the left, and the teller drawer/transaction panel is on the right (this is a user preference).
  • Quick Edit Functionality: A small “edit” icon allows for quick address or telephone number changes directly from the account inquiry screen, distinct from full user maintenance.
  • Icons:
    • Icons for features like Mobison (internet banking user maintenance) are standard industry-wide and not customizable by credit unions.
    • Icons vary based on account type (e.g., savings/checking icons differ from loan icons).
    • Some icons are engageable into maintenance views.
  • Note System: A scrolled note line appears at the top, and users can click it or use F4 to access more notes.
  • Account Summary: Lists savings, checking, loans, and certificates in grouped sections.
  • Customizable Views:
    • Headers no longer have dual duties (e.g., hold is not also pledge).
    • Users can customize what appears in primary and secondary (expanded) views using an ellipsis button and drag-and-drop settings.
  • Recent Activity: A new feature that accesses logs for card cycle approvals and denials directly from the front line, eliminating the need to log into a card provider. (Available at 804 release).
  • Loan Payoff Screen: Provides all loans on an account and allows calendaring and printing payoffs for multiple loans at once.
  • Favorites and Quick Links:
    • Users can right-click items to set a favorite or quick link.
    • Favorites are stored under a heart icon in the transaction panel.
    • Quick links appear as actual links on the right panel.
    • Their use is a user preference.
  • History and Table Formatting:
    • Clicking an account type in the left panel opens history by default in the right panel.
    • Filter buttons, printer icons (for PDF export), and general export options are available in many places.
    • Buttons require hovering to see their function descriptions.
    • Arrows allow expansion and collapse of rows in tables to view additional details (e.g., transaction details, Reg E items, disbursement details).
    • Tables limit the number of history records displayed (e.g., 10-50, with 20 being common) to maintain speed, with navigation arrows for more records.
    • Users can sort on headers (e.g., effective dates, balances) and use filters for specific information (e.g., check numbers).
  • Quick Transactions:
    • Allows building shortcut codes (e.g., “DP” for deposit).
    • Staff no longer need to know transaction codes (e.g., a “2” for deposit), they can use pick lists or type words like “deposit”. Seasoned staff can still use numeric transaction codes.
    • Transactions can be stacked (multiple entries) before being built and posted.
    • The system reduces “noise” by only showing relevant fields for a transaction (e.g., deposit only shows account and amount by default), with a “plus” button for additional fields if needed.
    • Supports different input methods: 10-key, keyboard typing, dropdowns.
    • Hyperlinks (e.g., “checks in” to engage scanners) are underlined.

4. Implementation Process

FLEX Ten implementation follows a phased and structured approach.

  • Phased Rollout:
    • Teller Platform: This is the initial and required first step. It is available for credit unions on release 804.
    • Open New Accounts: The second phase, also available at release 804.
    • Lending Platform: This phase will be available at release 805. Credit unions must be on release 805 and have completed the Teller and Open New Accounts implementations before moving to Lending.
    • Back Office and Maintenance Programs: FLEX is actively working on back office functionalities like General Ledger, Share Draft, and various account maintenance programs. Many account maintenance programs are ready at release 805.
  • Train-the-Trainer Model:
    • For initial implementations (Teller, New Accounts, Lending), FLEX will engage two to three key staff members from your credit union.
    • These key staff will receive formal training from FLEX, learn the system, and perform tasks like balancing.
    • They will then become the “train the trainer”, responsible for training the remaining staff at your credit union. FLEX will not provide individual training for all staff members.
    • FLEX will check in on your progress, but the discretion for full staff implementation lies with the credit union.
  • General Maintenance and Smaller Programs: For smaller programs like address maintenance or card maintenance (available at later 805 releases), formal independent training will not be provided for each credit union. Instead, overview sessions are recorded and placed on FLEX Academy for users to watch and implement at their discretion.
  • Discovery Process: When purchasing FLEX Ten, a discovery process is conducted to configure the system to your credit union’s initial preferences, with the ability to tweak settings later.

5. Support and Resources

  • For questions or issues, users are encouraged to reach out to the FLEX support team.
  • FLEX Academy serves as a resource for recorded training sessions and information.
  • Marketing representatives are knowledgeable and can assist with questions, especially regarding security and scheduling demos.