Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Unanswered
← Creating a custom first time login disclosures!

Hello,

A Custom login disclaimer can be created via Central. You can reach out to your CEM if you need help setting it up.

-Trey

0
Posted one year ago
pic
⠿More
Trey Teter
489 × 4 Administrator
0

My question was regarding more of the front end custmization of the UI the way it is displayed more than the actual contents. We will be using the existing Q2 first time login disclosure document but just customizing the way it is displayed for the users.I tried creating a custom extension for this but somehow it does not show up on sandbox. Is there any special configuration that needs to be setup on sandbox for this custom disclosure to show.
Thanks!

— Test   one year ago
-1

For various reasons, this is generally not a good idea. A mistake with how the login disclaimer is made can lead to end users not being able to log in to online banking. I recommend using the existing tools.

— Trey Teter   one year ago
0

The main aim of creating a custom disclaimer is to avoid for the customers to have to scroll down to the bottom of the Login disclosure UI to see the accept and Reject buttons. This is tiresome on mobile banking. Is there a way to stick the buttons on the Login Disclosure UI so that the buttons are always visible even without scrolling to the bottom of the UI to accept?

— Test   one year ago
Report
45 Views
0 Answers
one year ago
one year ago