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
 
← Back to post

Revisions 2

Original
Hiding Extensions Based On Account Product Type
Hiding Extensions Based On Account Product Type
Tanner, Thank you for the question! Are you referring to a tecton extension to be linked via account dropdown and/or displayed in an account tab? Currently, filtering tecton extensions by account type in such a scenario is possible - but the filter is *inclusive* rather than *exclusive*. Typically, our usecases either require an extension to only show for a very specific type of account, or a broader set of accounts. Excluding for a specific acccount type is not a use case we've encountered. Making an extension link as a dropdown in every account EXCEPT goals is possible, but it means you would have to create several entrypoints with the same baseURL for the extension in question, for each of the following context categories: 1. Checking Accounts (Account::Checking) 2. Money Market Accounts (Account::MoneyMarket) 3. Savings Accounts (Account::Savings) 4. CD Accounts (Account::CertificateOfDeposit) 5. Goal Accounts (Account::PlanBasedInvestment) 6. Plan Investments (Accounts::IRABasedInvestment) 7. IRA Investment Accounts (Account::IRABasedInvestment) 8. Brokerage Accounts (Account::BrokerageBasedInvestment) 9. All Loan Account Types (Account::Loan) 10. All Credit Card Account Types (Account::Credit Card) 11. All External Account Types (Account::External) 12. All PFM Account Types (Account::PFM) For details on configuring tecton modules to show in tabs or dropdowns, please review this documentation: https://cdn4.onlineaccess1.com/cdn/base/tecton/v1.25/Documentation/guides/creating-new-outlets In it, there is a video covering the use of the `q2 tecton` command which can be used to add the entry points, as well as place them into tabs for each category. If you need further assistance with this or would like to discuss your use case, please open a ticket.
Tanner, Thank you for the question! Are you referring to a tecton extension to be linked via account dropdown and/or displayed in an account tab? Currently, filtering tecton extensions by account type in such a scenario is possible - but the filter is *inclusive* rather than *exclusive*. Typically, our usecases either require an extension to only show for a very specific type of account, or a broader set of accounts. Excluding for a specific acccount type is not a use case we've encountered. If you're writing against such a use case - we'd love to know more. So while making an extension link as a dropdown in every account EXCEPT goals is possible, it means you would have to create several entrypoints with the same baseURL for the extension in question, for each of the following context categories: 1. Checking Accounts (Account::Checking) 2. Money Market Accounts (Account::MoneyMarket) 3. Savings Accounts (Account::Savings) 4. CD Accounts (Account::CertificateOfDeposit) 5. Goal Accounts (Account::PlanBasedInvestment) 6. Plan Investments (Accounts::IRABasedInvestment) 7. IRA Investment Accounts (Account::IRABasedInvestment) 8. Brokerage Accounts (Account::BrokerageBasedInvestment) 9. All Loan Account Types (Account::Loan) 10. All Credit Card Account Types (Account::Credit Card) 11. All External Account Types (Account::External) 12. All PFM Account Types (Account::PFM) For details on configuring tecton modules to show in tabs or dropdowns, please review this documentation: https://cdn4.onlineaccess1.com/cdn/base/tecton/v1.25/Documentation/guides/creating-new-outlets In it, there is a video covering the use of the `q2 tecton` command which can be used to add the entry points, as well as place them into tabs for each category. If you need further assistance with this or would like to discuss your use case, please open a ticket.
3 years ago
Hiding Extensions Based On Account Product Type

Tanner, Thank you for the question! Are you referring to a tecton extension to be linked via account dropdown and/or displayed in an account tab? Currently, filtering tecton extensions by account type in such a scenario is possible - but the filter is *inclusive* rather than *exclusive*. Typically, our usecases either require an extension to only show for a very specific type of account, or a broader set of accounts. Excluding for a specific acccount type is not a use case we've encountered. If you're writing against such a use case - we'd love to know more. So while making an extension link as a dropdown in every account EXCEPT goals is possible, it means you would have to create several entrypoints with the same baseURL for the extension in question, for each of the following context categories: 1. Checking Accounts (Account::Checking) 2. Money Market Accounts (Account::MoneyMarket) 3. Savings Accounts (Account::Savings) 4. CD Accounts (Account::CertificateOfDeposit) 5. Goal Accounts (Account::PlanBasedInvestment) 6. Plan Investments (Accounts::IRABasedInvestment) 7. IRA Investment Accounts (Account::IRABasedInvestment) 8. Brokerage Accounts (Account::BrokerageBasedInvestment) 9. All Loan Account Types (Account::Loan) 10. All Credit Card Account Types (Account::Credit Card) 11. All External Account Types (Account::External) 12. All PFM Account Types (Account::PFM) For details on configuring tecton modules to show in tabs or dropdowns, please review this documentation: https://cdn4.onlineaccess1.com/cdn/base/tecton/v1.25/Documentation/guides/creating-new-outlets In it, there is a video covering the use of the `q2 tecton` command which can be used to add the entry points, as well as place them into tabs for each category. If you need further assistance with this or would like to discuss your use case, please open a ticket.