Apply detail layout on item create form

Provide ability to set which detail layout to apply on module item create/edit forms

• hidden field with `DetailLayoutID` name.

• Value equals the Detail Layout ID

  • <input type="hidden" name="DetailLayoutID" value="12345">

Logic

• when submitting the form

  • if such field is provided

    • try to find detail layout using provided id

  • if field is not provided OR detail layout wasn't found

    • apply current logic of selecting a detail layout

Secure to CartID and crm member cookies

Set Secure attribute on the following cookies

• CardId

• treepl.member.auth

Site Information (Site Globals) Enhancements/Fixes

https://webinone.com/public-backlog-state/in-process/site-information-enhancements-fixes

A few minor adjustment requests for Site Information module:

dateTime field is still just a Date field. Is it possible to update this to select Time as well (as per dateTime field update throughout the rest of the admin)

When setting an Alias (particularly a ‘Short Alias’) there is a validation that runs to check for conflicting names. However, this seems to look at ALL properties in ALL groups, not just the group you are in, which starts to make it harder to set up short aliases. For example: In a group called ‘Company Info’ with a property of ‘Licence’ you might have Short Alias of {{si.ci.l}} Then in another group called ‘Company Branding’ with a property of ‘Logo’ you might want Short Alias of {{si.cb.l}} . But the validation only checks against the last Liquid reference of l (which conflicts) rather than the whole path (which is unique).

The textarea field type is labeled as Text (Multiple), but I think it should be Text (Multiline).

Liquid:

It would be great to recursively nest site information items. To do so they would need to render liquid, which they currently don’t.

For example if I have a site information company name and I want to nest that in a copyright notice so the client can just embed the copyright notice at the end of their blog posts.

Please make liquid work inside site information fields.

Other:

1. Ability to shuffle items once added.

2. Add a checkbox in the Group level determining whether that group’s properties are added to the Component toolbox or not.

• Checkbox title:

  • Add to the toolbox

3. HTML Layouts for formatted output.

Analytics Dashboard - Google Data Studio (now Looker Studio) Option

https://webinone.com/public-backlog-state/in-process/analytics-dashboard-google-data-studio-option

Added Looker Studio Embeded

Create Default JS Validation

https://webinone.com/public-backlog-state/in-process/create-default-js-validation

Default validation for mandatory fields

Add the option on the Settings tab "Enable Default JS Validation". If this option is enabled, `data-cms_validation` will be added on the form tag and add a validation js script in the head. If a form element is not valid it will add class "validation-error" on the element and if valid "validation-success" will be added.

File Manager: Show Date + List View in "Slide-In"

https://webinone.com/public-backlog-state/in-process/file-manager-show-date-list-view-in-slide-in

The list view in file manager should include the date of the upload like in BC to make it easier to handle e.g. media files, which are updated on a regular basis.

The slide-in file manager (when selecting media or other files from within module item) should have an option for list view. It makes it hard to select files with similar long file names in thumbnail view.

Custom Reports (further refinement)

https://webinone.com/public-backlog-state/in-process/custom-reports-further-refinement

"Select/Deselect All" option for these areas to expand our custom report filtering results

https://prnt.sc/9UHS5GSlxeyG

File Upload On Mobile Devices

https://webinone.com/public-backlog-state/in-process/file-upload-on-mobile-devices

The ability to upload files to the file manager from mobile devices.

Custom Module: Remove Downloadable Media Checkbox

https://webinone.com/public-backlog-state/in-process/custom-module-remove-downloadable-media-checkbox

When adding a ‘Media’ field type in a Custom Module the “Downloadable file” option is automatically added under the field.

I like to see this removed as it would surely not be used all that often and creates confusion and clutter in the interface.

Instead, could it be added as an option when setting up the Media property? So we can control whether or not it’s displayed:

UX/UI Request: List Template Used Against System Pages + enable/disable system pages

https://webinone.com/public-backlog-state/in-process/ux-ui-request-list-template-used-against-system-pages

Would be nice to see at a glance the template that is applied to system page. I’d image this would be a simple fix too.

System pages can now be disabled via an 'Enable' checkbox. Disabled pages will resolve to the 404 page. If the 404 page is disabled, a blank page will resolve (with a 404 document status)

Google Analytics Global Time Selector

https://webinone.com/public-backlog-state/in-process/google-analytics-global-time-selector

The ability to change all time periods at once in the analytics overview

UX Improvement - “Global Component Builder” and “Global File Manager”

1)

https://webinone.com/public-backlog-state/in-process/ux-improvement-global-component-builder

Anywhere in the admin console I press something like ‘Shift + Control + C’ on Windows (Shift + Command + C on Mac).

A modal appears with the same functionality as the component draw you get it various modules.

I always find myself needing to build a component in my IDE, but I have to go to the admin console, then to something like pages to be able to pull to create a component.

Would be nice if we could just access a builder anywhere in the admin console.

2)

Likewise, also add ‘Shift + Control + F’ on Windows (Shift + Command + F on Mac) to open the File Manager anywhere in the admin.

Fields/columns Added To The E-commerce/Gift Vouchers Module

https://webinone.com/public-backlog-state/in-process/fields-columns-added-to-the-e-commerce-gift-vouchers-module

Please add the following fields/columns to the gift voucher module:

• Date Purchased/Created Date

• Purchasers Name

• Order Number

• Link to order on list view

Add “Delete All Items” toggle for Admin User Roles

https://webinone.com/public-backlog-state/in-process/add-delete-all-items-toggle-for-admin-user-roles

Case: To stop the ability for Admin Users to be able to accidently delete all module items. Can we get an extra flag added in the Admin User Roles that gets generated for each custom module or anywhere this appears

Have it unchecked by default. Else, everyone will forget to configure it until it’s too late. So, essentially, ‘Delete All’ function is for Partner/Reseller admins only, unless configured otherwise.

Custom Modules Properties: Making Mandatory Items More Visible

https://webinone.com/public-backlog-state/in-process/custom-modules-properties-making-mandatory-items-more-visible

When you check the custom properties of any custom module and want to know which ones are defined as mandatory, you need to click each one into edit mode.

It would be nice if we could see which ones are mandatory right in the properties list.

Module Item Notes: Option To Display Notes More Prominently

https://webinone.com/public-backlog-state/in-process/module-item-notes-option-to-display-notes-more-prominently

Module item notes are great! But they are a bit small and users can miss them. Sometimes I want to add big bold notes that will give users instructions that they can’t miss.

Issues: Currently module field notes are displayed in a small icon that needs to be hovered to see them. Clients may miss this subtle icon.

Solution: Add a check box that will allow notes for a module field to be displayed inline:

Add Release And Expiry Dates/Time To Menu Items

https://webinone.com/public-backlog-state/in-process/add-release-and-expiry-dates-time-to-menu-items

When sites are being updated, it is common to have a release time for updates. This release time may be at an inconvenient time for the developer. Frequently site updates will mean new sections of the site are being added or removed. To add and remove sections of the website it would be great to have the ability for new sections of the menu to be automatically released, and old sections of the menu to expire and be hidden.

I propose adding the ability to enable release and expirty date/times to menu items.

Similar to custom modules, we would have the ability to enable release and expiry under settings for the menu.

Admin UI/UX Adjustments

https://webinone.com/public-backlog-state/in-process/admin-ui-ux-adjustments

1) Add the item preview icon at the top of item edit pages so it’s readily accessible (the current Preview link is often out of reach when you want it).

2) Add a new sticky box with the Components and File Manager buttons on the create/edit module item page and also to places where it’s not currently available, such as; ‘System Pages’, ‘System Emails’ and anywhere an editor region is present like; Form layouts, email/autoresponder/workflow contents.

3) This new sticky box will also include the ‘Properties’ icon along with the ‘File Manager’ and ‘Component Manager’ icons in the editor pages for module Layouts.

Create Folder Within Image/Media Manager

https://webinone.com/public-backlog-state/in-process/create-folder-within-image-media-manager

The ability to add a folder within Media/Image Manager

Custom Module: Custom Properties. Rename "Text (String)" To "Single Line Text" Or "String (Text)".

https://webinone.com/public-backlog-state/in-process/custom-module-custom-properties-rename-text-string-to-single-line-text-or-string-text-

When creating lots of fields it's time consuming to click on the dropdown and scroll to the correct property. It would be nice if you could just push "s" to jump to string. Ideally every type of field would have a name with a unique starting letter so you could use keys to jump to them. Also recommend having string as the default field type when creating a field.

1 hour refresh issue fix

Fix losing updated data on saving operations when the actual token is expired.

1) Presave to session storage flow

• Once any changes are made on any form in the admin UI

  • save them to session storage

• on saving operation if the token is expired and reload is performed

  • restore saved to session storage data and perform save operation so data will be saved with the new token

Feature flags changes (v6.10)

Apply the following changes to feature flags:

• Move to the external section

  • Site load speed improvement

  • Description

    • Improved logic of saving, updating, and deleting module items without a long delay on the page loading.

This feature flag switches the logic of saving module items, pages, etc.

New logic will take less time to load any page after saving if you have many module items.

The opposite part of this logic is the increasing time of any import module item process for sites that have many module items.

It is applicable to the sites with a lot of module items created.
On sites that do not have a lot of module items there is almost no difference between current item saving logic and improved version of it.

Internet connection checker (UI)

Add internet connection monitoring in the admin panel.

If internet connection is lost - show message:

"No Internet Connection"

Liquid Date Formatting Issue fix

Liquid Date Formatting Issue

An issue with the Liquid date formatting filter (`| date`) has been identified. Below is a description of the issue, possible conflicts with existing implementations, and our proposed fix.

ISSUE:

When using the date filter syntax of `%I` for outputting the hour in 12-hour time with a leading zero (eg: `{{ "now" | date: "%I" }}`) the output will be incorrect for the hour of 12 (am or pm), in that it will output `00` instead of `12`.

This is purely a formatting issue for this particular filter syntax and does not affect Liquid date calculations.

CONFLICTS:

We don't anticipate this fix will negatively impact any current implementations of this feature - on the contrary, any date-related Liquid implementations using the 12-hour filter output would currently be breaking under the conditions described in this issue and therefore, the fix will correct those implementations.

In the rare case that you have an implementation relying on the hour of 12, in 12-hour time, with leading zero output, being "00" (which is incorrect), you will need to adjust your code to allow for this correction.

PROPOSED FIX:

As there is a small chance of this change affecting existing implementations and due to the issue's low criticality, we will add the feature flag "Apply fix to liquid date filter".

The fix itself will then be rolled out as a hotfix to all sites during their data center non-business hours.

No downtime is expected for the admin or site front-ends during this hotfix and a notification will be posted once it has been fully completed across all data centers.

FEEDBACK:

If you have any questions, feedback, or concerns regarding this fix, please reach out to support via a support ticket before the proposed fix date is reached.

NOTES:

The similar `| format_date` Liquid filter does not suffer from the described issue and is therefore unaffected by this fix and continues working normally.

Improve workflow sending logic based on plan restrictions

1) Fix the ability to send custom workflows if the site plan is lower than Pro.

When the site plan is Business or Essential (lower then Pro):

• Logic in table representation

  Plan/Type	System WF + defaul email	System WF + custom email	Costom WF + defaul email	Custom WF + custom email
  Essential	send	replace to default email	skip	skip
  Business	send	replace to default email	send	replace to default email
  Pro	send	send	send	send
  eCommerce	send	send	send	send

• OR logic in description representation

  • If the workflow has a custom email assigned

    • Allow sending workflow BUT with system email instead of the assigned custom email

  • Continue validation if the workflow has a system email assigned:

• When the site plan is Essential:

  • Disallow sending workflow if it has IsDefault = false

  • Allow sending workflow if it has IsDefault = true

• When the site plan is Business:

  • Allow sending workflow

https://prnt.sc/bh8RQGPoHV_c

2) Improve displaying of the workflows with forbidden emails applied on workflow listing

Show label for workflows with custom email applied

Pattern

• <WorkflowName> (<label>)

Label

• forbidden email applied available starting Pro plan

Color

• red

Example

• My custom workflow (forbidden email applied available starting Pro plan)

​3) Show inactive email field on workflows on plans lower than pro

• On edit workflow form

Empty tables UI improvements - Admin

Empty tables logic/UI

Show message "Nothing here yet" instead of empty table if no searching-filtering is applied

Show empty table if any search or filtering is applied to the list view

Case sensitivity FTP improvement

1) Pages and folders case change on migration

Description:

On migration we would collect all url slugs of "Page" and "Folders" module items that has at least one uppercase letter and convert them to lowercase.

Then we will rename the files and folders for the following items accordingly in the "/Content/Pages" folder

2) Liquid incorrect paths change on migration

Places to be operated:

• Item description

• Snippet

• Content Template

• Email Template

• Email content

• Module Layouts

• Form content

• Includes (that are included in any of the places above and inside includes as well)

Liquid tags to be fixed (example regexp: https://dotnetfiddle.net/t8939t ):

• {% include "[[path]]" %}

• {% component ... layout:"[[path]]" %}

• {% component source_type: "path", source: "[[path]]", type: "json" ... %}

• {% component folder: "[[path]]", type: "api" ... %}

Description:

On migration we would scan page content, templates, snippets, module layouts, etc for using liquid include and component with custom layout path tags and replace paths to match case-sensitive actual path (for example if we found {% include "/Content/Pages/testfolder/TestIncludeFile.inc" %} we will fix it to match actual path - /Content/Pages/TestFolder/TestIncludeFile.inc and it will become {% include "/Content/Pages/TestFolder/TestIncludeFile.inc" %})

3) JS, CSS, and image URLs change on migration

Places to be operated:

• Same as above

HTML tags to be worked with (example regexp: https://dotnetfiddle.net/t8939t ):

• <script ... src="[[path]]"...>

• <link... href="[[path]]"...>

• <img ... src="[[path]]"...>

Description:

Same as in previous but working with html tags insted of liquid

4) Improve the logic of operation files and folders in the "/Content/Pages" folder

Description:

Any files that would be created in the "/Content/Pages" folder should be lowercase from now on.

If they would be created not fully lowercased - they would be ignored.

So if you create a file Test.html in the folder /Content/Pages/ - it WOULD NOT create a page with slug Test.

But if you create a file test.html in the folder /Content/Pages/ - it WOULD create a page with slug test.

Also renaming test.html to Test.html would unlink the Test.html file from the "/test" page. If you save the "/test" page from the admin UI it will create a test.html file and it will be linked with the page (the main rule is that the page slug is fully equal to the file name (case sensitive)).

Any operations with the Test.html would not be reflected in any way on the pages at all.

However, if you rename it back to the test.html - it will be linked back to the page "/test" but without content sync (it means that if you rename test.html to Test.html, change content in Test.html and rename it back to test.html - the content of the page "/test" would not be the same as in the test.html file. The first save of the file or page would determine - what content would be saved to opposite entity in that case - if the save file - page content would be updated. If the save page - the file content would be updated).

5) System and custom email file name fix

Description:

On migration we would change all file names that reflect all system and custom (workflow, followup, abandoned cart) emails so it is the same as the email Name (right now if you have a workflow email with the name "My Custom Email" - it has a file on FTP with the name "my-custom-email.html". This step will rename the file to become "My Custom Email.html").

NOTE:

So if you already have the backup version of the site you are working with then just make a fresh copy right after your site would be updated to the v6.10

More documentation on this change can be found here.

Angular 15 refactoring

• new datetimepicker

• migration from moment to luxon

• Clear styles when pasting

  • Clear all styles when pasting content into wysiwyg. If you try to paste some content from MS Word should be shown a modal to choose to keep or not styles pasted from Word.

Event calendar month by URL accessibility

Add month-year accessibility via URL to the event calendar

URL parameters names:

• CMSEventCalendarMonth

• CMSEventCalendarYear

If page requested via URL like

• /page?CMSEventCalendarYear=2021&CMSEventCalendarMonth=09

Calendar should open the appropriate year and month view

File Manager - move file

Ability to move files in file manager via context menu and drag and drop.

DESIGN:

https://invis.io/XH107NKQ9UZF

File Manager - move folder

Ability to move folders in file manager via context menu and drag and drop.

DESIGN:

https://invis.io/XH107NKQ9UZF

Pagination refactoring

Rework all paginations on all admin UI layouts to work through server side.

This would allow optimizing a list load speed on all layouts that previously used client-side pagination.

Also this update would standardize pagination UI on all layouts

Added pagination to the following list layouts:

• templates

• mailing lists

• email campaigns

• admin users

System emails

a-z sorting by name

All system emails now sorted alphabetically
Plus a "Template" column was added to the system emails table list.

• https://prnt.sc/qB9Vnd__-Cmh

"New Item" button name standardization

"New Item" button text was changed from ADD to CREATE throughout the admin.

Case insensitive search in admin UI

Search in admin UI now works in case insensitive manner

• https://prnt.sc/yCaMSvXAlmvd

Email data widget improvement

Now Email data widget would show only data that corresponds to current type of email (workflow email, follow-up email or abandoned cart notification email)

• https://prnt.sc/NnyR2GejC8zT

Custom module - filter by Author

SLACK:
https://treepl.slack.com/archives/C023SU50YQP/p1673542315877379

Go to Components -> Choose custom module with Author -> Filter by Author -> ONLY In code should be display ID, not name https://prnt.sc/fShwUL0TmW8a

Should be
{% component source: "create item from front ", layout: "List", filterBy: "Author", filterValue: "8406", type: "module" %}

Secured Content - twice click on one page

Go to some Secure Zone -> Secure Content -> click on several page and use ctr/command and click twice on one page -> after that move pages from left window in right window - not all pages moved https://drive.google.com/file/d/17O5OyXaUY9yQTp-k1BBBi-mQ293lYaoa/view?usp=sharing

https://treepl.slack.com/archives/C023SU50YQP/p1656082426131989

Categories - Missing parent Category names

BUG: Missing parent Category names https://the-second-site-owner.trialsite.co/admin/module/1827/item/2053/settings?view=list-view&pageIndex=0&moduleId=1827&parentId=1827

JSON output is different to Liquid output: https://prnt.sc/qiM8nHB-GvGo

SLACK:
https://treepl.slack.com/archives/C023SU50YQP/p1676598883293619

custom module - delete item with custom redirect

SLACK:
https://treepl.slack.com/archives/C023SU50YQP/p1673548831805979

• Go to Custom module which you can create item from front
• Add in List layout possibility to delete item from front
• In ?redirect put custom page like in screenshoot https://prnt.sc/iDKkb8JWesld
• Go to front and try to delete item -> custom redirect doesn't work

Custom module - broken list

• create a new custom module with settings https://prnt.sc/Gvk0WfFBgzs8 https://prnt.sc/cLnkaE7zrxp5
• go to the module list view
• errors were displayed https://prnt.sc/bLcj2KD07EkI

Products - InStock value doesn't show in frontend after import

• create a new product by import (file attached) with "Enable Inventory Control" - true, and In Stock - 1000 https://prnt.sc/mlPYOEGCiEuK
• add <pre>{{this}}</pre> in product detail layout
• go to frontend this product
• value "InStock" : 0 , but must be equal to the value in the import file = 1000
• after this go to product detail in admin and click save https://prnt.sc/fBjMhWORc89h and go to the frontend value "InStock" = 1000 https://prnt.sc/Afg55sGjcQZv

Custom module - import with invalid parent URL

• create a new custom module without the module URL https://prnt.sc/MWwIL99fScU6
• create a new item in this module https://prnt.sc/BSvzHkec58z7
• do export module items https://prnt.sc/odqeQQszfPQ_
• in the excel file, copy the created element and paste it into the next line and change "1" to "2", and delete ID https://prnt.sc/NFZ47vLWv7lo and save
• import this file https://prnt.sc/xjGOCWPW9KK_
• an error was displayed https://prnt.sc/0ClVoPCtcBst , reload the page and the item will be created https://prnt.sc/f8IxEWqCJhw-

Custom reports - results don't show the CMR group values

• go to custom reports
• create a new report with a "Contacts and Secure Zones" type https://prnt.sc/36w6qaqfvXK8
• add CRM group fields https://prnt.sc/tQIXE3KeSTNg
• add a filter with my test contact email "bestttest2023333@gmail.com" https://prnt.sc/gkLRjcu9g11l
• go to the results tab
• all fields are empty https://prnt.sc/s1m-EO_DJjrg
  BUT
• go to the settings tab and change the report type on "Contacts and Cases" https://prnt.sc/cvmzJQkN2GGa
• add the same fields https://prnt.sc/Sfn8ZvPETlL8 and filters https://prnt.sc/xeRXrb9AcWDy
• go to the results tab https://prnt.sc/D6pL48bg0KcX

System email - Restore Admin User Password

When resetting the user admin password, the {{this.User}} model from which the “FIrst Name” is taken in the letter is not available https://prnt.sc/L0ELMfsrWu21 https://prnt.sc/iLDD43t9vqu7

Using Cases component you can not filter "equally" by form name

• If in component use "equally" condition - should display only the same name
• {% component viewType: "list", currentMemberOnly: "false", filterBy: "FormName", filterValue: "Registration", filterCondition: "contains", limit:"100", type: "cases" %}
  
  ----
  
  {% component viewType: "list", currentMemberOnly: "false", filterBy: "FormName", filterValue: "Registration", filterCondition: "equally", limit:"100", type: "cases" %}
• On page display not correct tag with "equally" https://prnt.sc/iSQPxriPa3Qk

Orders - discount prices

• create a two products with price 10 and two discounts 10 and 15
• go to orders
• create a new order
• go to products tab https://prnt.sc/4Fq2qbXurNKr
• add created products to this order https://prnt.sc/yA7W49ImxXVk
• select first discount 10 https://prnt.sc/PvfVfhyQdIpb then select discount 15 https://prnt.sc/M5YtjU5HN5AY
• again to discount 10 https://prnt.sc/LKcttKgZHEv_ shows the incorrect discount price

E-commerce Quoting Option

Original Description:

E-commerce quoting option so that when an order goes through the admin it can be edited or completed before the quote is transformed into an order and the invoice is issued for payment in full or for a deposit payment. A workflow can then also be generated for the order to go to the client/accountant/franchisee.

DESIGN

https://invis.io/YAX7PB2EC3Q 

1) Create Order functionality

Provide ability to create new order from the admin

Default status is ‘New’

Invoice Number should not be generated during this action

• Form fields
  • Order Name
  • Domain (Dropdown - list of available site domains)
  • Status (Dropdown - list of available statuses)
  • Assigned To (Required - CRM lookup field)
  • Invoice Number
  • Invoice Date (preset to current date)
  • AWB Number
  • Tracking Url
  • Shipping address
  • City
  • State
  • Zipcode
  • Country
  • Advanced CRM groups assigned to the order
  • Add Custom Fields (available after saving the order)

2) Change products in the order

Provide ability to edit order products from the admin

BC reference:
https://prnt.sc/s2oblz 

Design:

https://projects.invisionapp.com/share/YAX7PB2EC3Q#/screens/415110743

Implement following functionality:

• Add/Edit product
  • add via side panel: https://projects.invisionapp.com/share/YAX7PB2EC3Q#/screens/415110742
    • datasource search box for products (in sidebar add product panel)
    • attributes control same as on regular product edit page
• Disallow adding products if they are recurring products
  • Show error message “Recurring product is not allowed to be added”
• Disallow editing products data if an order is a recurring order
  • Show error message “Orders with recurring products are not allowed to be edited”
• Change inventory accordingly if there is are quantity changes to any ecommerce product order lines
• Provide the ability to edit the product name
• Provide the ability to change prices https://prnt.sc/x5cffi
  • implement linked recalculation between
    • Unit Price, Units, and Total Price
      (the Unit Price and Total Price should be calculated according to the applied tax)
  • once Unit Price or Total Price change is applied
    • do not apply volume discounts to this orderline any more
    • tax settings still should be applied to this product after quantity change
• Provide the ability to delete the product from the order

If saving order with changed products, gift vouchers, discount codes, or shipping options and the order has an active recurring subscription:

• show error
  • This order data is not allowed to be changed for orders with recurring subscriptions

3) Change overall order data

Provide ability to change the following data for an Order:

• tax
• giftvouchers
• discount codes
• shipping options
• Disallow editing this data if:
  • an order contains an active recurring subscription

Provide ability to Generate Invoice Number via admin UI ( https://projects.invisionapp.com/share/A8W5SNPF5QX#/screens)

• if generate invoice number action performed to the order that already has a system or custom invoice number
  • show an error message “This order already has an invoice number”
• Show ‘Generate Invoice Number’ button only on orders that don't have a system generated or manually added invoice number.

4) New Payment type of “Refund”

Provide ability to add “Refund” as a payment type

• Refund type can be added:
  • manually from the admin (in Order payments tab)
  • via webhooks:
    • Stripe: refund, cancel(only automatic flow)
    • Paypal: refund
    • Authorize: refund, void(cancel)
    • Bambora: -
    • Eway: -
• Allowed to be deleted (if manual added only)
• Value should be shown as a negative value (currency format should be taken according to the current format setting on the current domain)
  • https://prnt.sc/cjhUDIhdlBKR

5) Form changes

Create a new form type of “Quote” (for requesting a quote in the ecommerce quoting process)

• Logic is the same as for the Checkout but
  • generates order without an invoice number.
• On Edit form action (tab ‘Form Builder’ or tab ‘Settings’)
  • do not show recurring secure zones on the Settings tab if the selected form type is Quote
  • if the selected type is Quote and there are paid secure zones attached to the form
    • Show error message “Quote form can't be saved with the attached recurring secure zones”
• On Edit form action (tab ‘Form Builder’)
  • if Form Type is Quote
    • If the "Accept Payment" field is selected on the form builder - show an error: “Quote form can't be saved with the "Accept Payment" field”
    • Do not show the following field buttons in the system fields list https://prnt.sc/GtfaxcIGuoPO
      • Accept Payment
      • Discount Code
      • Gift Voucher
      • Accept Event Booking
  • if Form Type is Checkout
    • Do not show the following field buttons in the system fields list https://prnt.sc/GtfaxcIGuoPO
      • Discount Code
      • Gift Voucher
      • Accept Event Booking
• On Form submit:
  • if Form Type is Quote AND "Accept Payment" field is selected on the form builder - show an error: “Quote form can't be submitted with the ‘Accept Payment’ field”
  • if Form Type is Quote AND there is no shipping option selected on the shopping cart DO NOT stop processing the form.
  • if Form Type is Quote AND there is at least one recurring product in the shopping cart - show an error: “Quote form can't be submitted with recurring products in the shopping cart”
  • if Form Type is ‘Quote’ OR Form Type is ‘Checkout’ and there is a product in the shopping cart that was deleted - show an error: “Your shopping cart contains deleted products. Please review and remove all deleted products from the shopping cart and proceed once again”
• On loading ‘Checkout’ or ‘Quote’ page from the shopping cart:
  • if there is a product in the shopping cart that was deleted - show an error: “Your shopping cart contains deleted products. Please review and remove all deleted products from the shopping cart and proceed once again”

6) Shopping cart changes

Add request quote button to shopping cart liquid object:

{% component type:"shopping_cart" %}

• QuoteButtonHtml:
  <button class="system_button" data-cms_cart_quote="">Get a quote</button>
• clicking on the button should lead to /quote
• apply Before After and trigger js events
  • CMS_BeforeGoToQuote
  • CMS_AfterGoToQuote
  • CMS_TriggerGoToQuote
• clicking Quote button validation should not require a shipping option to be selected

7) Request a quote system pages

Create system pages for Quotes

• Get A Quote (/quote)
  • redirect here if clicked on the request quote button on the checkout
  • see content in page ‘Settings’ > ‘System Pages’ > ‘quote’
• Quote Receipt (/quote-receipt)
  • user will be redirected here after quote form submission (default page)
  • see content in page ‘Settings’ > ‘System Pages’ > ‘quote-receipt’

8) System emails

Create System email for Quotes

• For Quote Orders, send in place of Invoice email
  • sent on quote order create
  • ability to send quote if clicked ‘send quote’ button in the Order detail page (instead of ‘send invoice’)
• Default From Email
  • admin@trustedemail.co
• Default Subject
  • Quote
• Default From Name
  • Admin
• Content
  • see content in file ‘Email Notifications’ > ‘System Emails > ‘Quote’

9) Secure zone logic

On Quote form submit with Secure Zones assigned:

• If there are paid secure zones assigned - show error message “Recurring secure zone subscription is not allowed for the ‘Quote’ form type”
• else; immediately subscribe user to all free secure zones assigned to the form.

10) Precreate Request Quote form on all sites with default styles

Replicate default HTML/styles from the Checkout form, but remove payment fields and Total Amount field.

Create the form on all sites with the alias of ‘quote’

Fields on formbuilder:

• firstname
• lastname
• email
• phone
• Shipping Address
• reCAPTCHA v3

11) Plan restrictions

Disallow submission of forms with type ‘Quote’ on plans lower than eCommerce.

Show error message “Quote forms are not available on current site plan”

12) Admin User Role Restrictions

Add following admin user role restrictions

• Orders
  • Can Add
  • Can Edit Details
  • Can Edit Payments
  • Can Edit Products

For all roles that have Orders -> Can View=true set Orders -> Can Edit Details=true (for backward compatibility)

For all roles that have Orders -> Can View=true set Orders -> Can Edit Payments=true (for backward compatibility)

Logic

• Orders -> Can Add=false
  • Blocks add new order request
  • Removes Add New Order button from UI ( https://prnt.sc/3kND8xikawwT)
• Orders -> Edit Details=false
  • Removes Edit button from UI ( https://prnt.sc/qJv5vry38oQU)
  • Blocks update order details form url /admin/orders/123456/details
  • Blocks update order details request
  • Blocks generate invoice request
  • Removes Generate Invoice button from UI
• Orders -> Edit Payments=false
  • Removes Add Offline Payment button from UI ( https://prnt.sc/B0YqlLBAT_aX)
  • Removes Edit Delete buttons from payment records UI ( https://prnt.sc/svzcrrdDszLv)
  • Blocks Add Edit Delete payment record requests
• Orders -> Edit Products=false
  • Blocks all update request for
    • orderlines
    • taxes
    • giftvouchers
    • shipping options
    • discounts

eWay payment field expiration workaround

1) Extend eWAY payment gateway settings

Adds new option for how the payment integration displays in payment forms.

When configuring eWay as a payment option under ‘Settings’ > ‘Payments’ new option for:

• Checkout Integration Type (dropdown)
  • Inline (default - current implementation)
  • Modal (new implementation)

2) Logic for Modal

Do not show payment fields on the form.

Instead, once form is submitted show popup modal with payment fields.

3) Improve payment fields validation

After form submit:

• if payment fields error occurred
  • reload payment fields iframe

This should avoid issue when credit card data determined as expired after second form submit even after payment data was fixed

Event payment to include tax and volume discounts

Event payments now honor tax settings and volume discount brackets assigned to Event prices.

Liquid output improvement of the event item:

Add following properties to liquid output of the event item:

"priceWithTax": 11.00, 
"RecommendedPrice": 5.0000, 
"RecommendedPriceWithTax": 5.50, 
"taxRate": 0.1000, 
"VolumeDiscount": 
[ 
{ 
"Price": 10.0000, 
"Quantity": 0 
}, 
{ 
"Price": 8.0000, 
"Quantity": 5 
}, 
{ 
"Price": 5.0000, 
"Quantity": 10 
} 
] 

JS for volume discount:

When changing allocation field:

• recalculate total amount based on volume discount settings of the price

On page load:

• recalculate total price via API call based on
  • price in data-event_one_item_price
  • quantity in Payment_ItemQuantity
  • quantity discount
• and paste totalAmount to the value of
  • field by selector [name="Payment_Amount"]
  • field by selector #PaymentTotalCost

Headers settings custom setup

1) Add header settings page

Add new menu item and page under ‘Settings’ > ‘HTTP Header Settings’

DESIGN

https://invis.io/M4107BHKYUDC

Content

• list of allowed headers
• Ability to enable/disable header
• Ability to setup header's specific settings
  • ability to enable header
  • ability to setup header value (described below)

>> Strict-Transport-Security

• Documentation
  • https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security 
• Options
  • max-age (text - allows only numbers)
    • 63072000 (default)
  • preload (checkbox)
    • false (default)
  • includeSubDomains (checkbox)
    • false (default)

>> X-Content-Type-Options

• Documentation
  • https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options 
• Options
  • nosniff (checkbox)
    • false (default)

>> X-Frame-Options

• Documentation
  • https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options 
• Options
  • value (dropdown)
    •  (default “empty”)
    • DENY
    • SAMEORIGIN

>> Access-Control-Allow-Origin

• Documentation
  • https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin 
• Options
  • origin (text)
    • * (default)

>> Content-Security-Policy

• Documentation
  • https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
• Options (text)
  • child-src
  • connect-src
  • default-src
  • font-src
  • frame-src
  • img-src
  • manifest-src
  • media-src
  • object-src
  • prefetch-src
  • script-src
  • script-src-elem
  • script-src-attr
  • style-src
  • style-src-elem
  • style-src-attr
  • worker-src
  • base-uri
  • sandbox
  • form-action
  • frame-ancestors
  • navigate-to
  • report-uri
  • report-to
  • require-sri-for
  • require-trusted-types-for
  • trusted-types
  • upgrade-insecure-requests

>> Referrer-Policy

• Documentation
  • https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy 
• Options (checkbox)
  • no-referrer
  • no-referrer-when-downgrade
  • origin
  • origin-when-cross-origin
  • same-origin
  • strict-origin
  • strict-origin-when-cross-origin
  • unsafe-url

>> Permissions-Policy

• Documentation
  • Actual header info:
    https://github.com/w3c/webappsec-permissions-policy/blob/main/permissions-policy-explainer.md 
  • (deprecated header):
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy 
• Options (text - disallow to input following characters: ,() [replace to empty string])
  • accelerometer
  • ambient-light-sensor
  • autoplay
  • battery
  • camera
  • display-capture
  • document-domain
  • encrypted-media
  • execution-while-not-rendered
  • execution-while-out-of-viewport
  • fullscreen
  • gamepad
  • geolocation
  • gyroscope
  • layout-animations
  • legacy-image-formats
  • magnetometer
  • microphone
  • midi
  • navigation-override
  • oversized-images
  • payment
  • picture-in-picture
  • publickey-credentials-get
  • speaker-selection
  • sync-xhr
  • unoptimized-images
  • unsized-media
  • usb
  • screen-wake-lock
  • web-share
  • xr-spatial-tracking
• Example of usage:
  • fullscreen
    • self "https://example.com" "https://another.example.com"
  • geolocation
    • *
  • camera
    • 'none'
• Resulting Header from example:
  • Permissions-Policy: fullscreen=(self "https://example.com" "https://another.example.com"), geolocation=*, camera=()

>> (For page requests) Cache-Control

• Content is same as below

>> (For files requests) Cache-Control

• Documentation
  • https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control 
• Options (text - allow only numbers)
  • max-age
  • s-maxage
  • stale-while-revalidate
  • stale-if-error
• Options (checkbox)
  • no-cache
  • must-revalidate
  • proxy-revalidate
  • no-store
  • private
  • public
  • must-understand
  • no-transform
  • immutable

>> (For page requests) Age

• Content is same as below

>> (For files requests) Age

• Documentation
  • https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Age
• Options
  • Age (text - allow only numbers)

>> (For page requests) Expires

• Content is same as below

>> (For files requests) Expires

• Documentation
  • https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expires
• Options
  • Seconds (text - allow only numbers)
• Logic
  • Add seconds to the current datetime and set resulting http-date

2) Logic

For ANY URL request (to any page or file) that is NOT related to the admin files and requests

• add selected and configured headers to the response
  • if header is enabled AND there is at least one not empty option inside
    • add header with the selected options
      • checkbox options
        • if true - add option to the header. Else - ignore this option
      • text options
        • if NOT empty string - add option with the value to the header. Else - ignore this option
      • dropdown options
        • if NOT empty option selected - add option with the  selected value to the header. Else - ignore this option

3) Admin user role restrictions

Add following admin user role restrictions

• HTTP Header Settings
  • Can View
  • Can Manage

4) Site plan restrictions

Show ‘Settings’ > ‘HTTP Header Settings’ page starting from plan

• Pro

----------

Headers Validator Site: https://securityheaders.com/

Checklist values with commas improvement

1) Request params improvement

Add new property to ‘request.request_url’ liquid object

• request.request_url.originalParams

Value is an object of all URL params however arrays should be represented as arrays instead of as CSV string

Example:

• /lab?myArrayProp=option%201&myArrayProp=opti,on%202&myTextprop=textValue

<pre>{{request.request_url.params}}</pre>

Outputs:

{ 
"myarrayprop": "option 1,opti,on 2", 
"mytextprop": "textValue" 
} 

<pre>{{request.request_url.originalParams}}</pre>

Outputs:

{ 
"myarrayprop": ["option 1", "opti,on 2"], 
"mytextprop": "textValue" 
} 

2) Advanced CRM group field liquid object improvement

Add ‘ArrayValue’ property. If a field is checklist or dropdown (multiple) - paste selected options as an array to this property.

For all other fields paste value as first element of the array

Example:

{% component groupAlias: "MyAdvancedCRMGroup", entityType: "contact", entityId: "12345", collectionVariable: "groupFieldsList", layout: "", type: "CRMContactCustomGroup" %}

{{groupFieldsList}}

Output:

{ 
"Name" : "My Checklist", 
"Alias" : "MyChecklist", 
"Value" : "check 1,che,ck 3,check 4", 
"ArrayValue" : ["check 1", "che,ck 3", "check 4"] 
}, 
{ 
"Name" : "My Text", 
"Alias" : "MyText", 
"Value" : "my, some text", 
"ArrayValue" : ["my, some text"] 
}, 
{ 
"Name" : "My Number", 
"Alias" : "MyMuber", 
"Value" : 123, 
"ArrayValue" : ["123"] 
} 

3) Save entity improvement

For the following property types:

• checklist
• dropdown multiple

View selected options of the property of type checklist or dropdown multiple as CSV string on list and detail layouts in Admin UI

• If options are like
  • option 5
  • option 6
  • option 7,7
• CSV string should be like
  • option 5 5,option 6,option 7,7

Provide the ability to save selected options if they contain "," character

• via Admin UI
  • Create module item
  • Edit module item
  • Create CRM Contanct (advanced CRM fields)
  • Edit  CRM Contanct (advanced CRM fields)
  • Create CRM Form Submission  (advanced CRM fields)
  • Edit  CRM Form Submission (advanced CRM fields)
  • Create CRM Event Booking (advanced CRM fields)
  • Edit  CRM Event Booking (advanced CRM fields)
  • Create CRM Order (advanced CRM fields)
  • Edit  CRM Order (advanced CRM fields)
• via save/edit entity frontent form
  • Form submission
  • Edit account form
  • Create module item form
  • Edit module item form

Entities that requires this improvement (admin UI)

• module item
• case
  • custom form fields
  • advanced crm fields
• order
  • advanced crm fields
• event booking
  • advanced crm fields

Add also following updates to module item update and search forms (site frontend forms)

• Module item update form
  • For Checklist property type
    
    var propertyValues="{{this.ListcheckboxList | join:","}}".split(',');
    
    change to
    
    var propertyValues="{{this.ListcheckboxList | join:"|||;/;|||"}}".split('|||;/;|||');
    
  • For Dropdown (multiple) property type
    
    var values='{{this.ListListbox_list}}'.split(',');
    
    change to
    
    var values='{{this.ListListbox_list | join:"|||;/;|||"}}'.split('|||;/;|||');
• Module item search form
  • For Checklist property type
    
    var propertyValues="{{request.request_url.params.prop_ListcheckboxList}}".split(',');
    
    change to
    
    var propertyValues="{{request.request_url.originalParams.prop_ListcheckboxList | join:"|||;/;|||"}}".split('|||;/;|||');
    
  • For Dropdown (multiple) property type
    
    var values='{{request.request_url.params.prop_ListListbox_list}}'.split(',');
    
    change to
    
    var values='{{request.request_url.originalParams.prop_ListListbox_list | join:"|||;/;|||"}}'.split('|||;/;|||');

4) Custom report improvement

According to the Save entity improvement improve custom report results searching by filters that contain value with "," character

• filtering by custom form field on the following report types
  • Contacts and Cases
  • Contacts and Orders
  • Contacts and Event Bookings
• filtering by advanced crm field on the following report types
  • Contacts
  • Contacts and Cases
  • Contacts and Orders
  • Contacts and Event Bookings
  • Contacts and Secure Zones

5) Import/Export improvement

Add following logic to import/export process for the following entities:

• Module item
• Contact
• Case
• Booking
• Order

Logic:
For any property with type Checklist or Dropdown (multiple)

• On Export
  • When generating CSV string of selected options replace "," substring with "%2С"
• On Import
  • After retrieving list of selected options from CSV string for each option replace "%2С" substring with ","

Example:

• Export
  • options
    • option 5
    • option 6
    • option 7,7
• CSV string for the property (to the excel cell)
  • option 5,option 6,option 7%2С7
• Import
  • CSV string for the property (from excel cell)
    • option 5,option 6,option 7%2С7
  • result list of options to be applied
    • option 5
    • option 6
    • option 7,7

6) Improve filters on custom reports

`In` and `NotIn` filters:
Add a new setting to the filter called:

• Values Filter Condition (dropdown)
  • OR (default)
  • AND

Logic:

• If OR selected (current logic will be applied) - will find all items that have at least one value from the filter values list
• If AND selected - will find all items that have all values from the filter values list

Design: https://prnt.sc/KsffJVqXl2pm

Example:

Add an advanced CRM group with the field “theChecklist” to the contact of type Checkbox:

• options
  • 1
  • 2
  • 3
  • 4

Select the following values for the contacts:

• Contact1
  • theChecklist
    • 1
    • 3
• Contact2
  • theChecklist
    • 1
    • 3
    • 4

• Contact3
  • theChecklist
    • 2
    • 3

Setup Custom report for contacts and:

• Add filter (using OR):
  • theChecklist
    • 1
    • 4
  • Values Filter Condition
    • OR
  • Results should be
    • Contact1
    • Contact2
• Add filter (using AND):
  • theChecklist
    • 1
    • 4
  • Values Filter Condition
    • AND
  • Results should be
    • Contact2

"Remember Me" for CRM login form

Provide the ability to remember the logged-in state for CRM Members and configure its duration

Settings:

Add new setting to ‘Settings’ > ‘Misc’ > ‘CRM Settings’

• Remember me lifetime (numeric)
  • 30 (default)
• Logic
  • Determines how many days should logged in state be held after login form submit

Login form upgrade:

Add Remember me checkbox to login form layout when retrieve login form from Components toolbox (Secure Zone -> Login Form)

Add following html code to the form layout (after password fields):

<label for="RememberMe">Remember me</label>
<input type="checkbox" name="RememberMe" id="RememberMe">

Example: https://prnt.sc/mhd_q974tKDb

Login form logic:

When user submit login form with checked Remember me checkbox

• set member logged-in cookie lifetime based on Remember me lifetime setting

if not checked

• Member logged-in cookie lifetime defaults to 1 day

Improve Site load speed while saving module item

Replace the current solution with a materialized view to the DB table supported by triggers to sync data.

Improve the following logic that using the Table solution

• Add DB Table solution to drafts
• Improve saving module item when keywords was changed
• Improve Import module items process

Tax rounding strategy setting

1) Add a new eCommerce setting

Add new setting to ‘Ecommerce’ > ‘Settings’ > Tax and Shipping’ > ‘Tax Settings’

• “Tax rounding strategy” (dropdown)
  • Banker rounding + error compensation (unit price and total price) [default]
  • Banker rounding (unit price only)

2) Rounding Logic on shopping cart calculation

When banker rounding + error compensation (unit price and total price) applied

• use current price rounding strategy (banker rounding + error compensation)
• rounding applied to
  • unit price separately
  • total price separately

When banker rounding (unit price only) applied:

• use banker rounding to unit price. Then calculate orderline total price as rounded unit price multiplied by quantity.
  Error compensation mechanism is not needed here
• apply rounding to
  • unit price only

Abandon Cart Functionality

1) Extension setup

Add new Extension to the portal and to extension JSON file so portal user could enable and disable extension on the ‘Site’ > ‘Extensions’ tab in the Portal

“Abandoned Cart Recovery”

Short Description:
With abandoned cart recovery functionality (for logged-in users only), you can automatically send reminders to customers who add products to their cart and leave without completing an order.

Information:
According to statistics, about 80 percent of customers abandon purchases for different reasons after adding items to their shopping carts. With Treepl abandoned cart recovery you can automatically email users after a cart or checkout is abandoned. And you have the ability to set the time when the email will be automatically sent. So you can stay in touch with your customers while they still remember your store and products.

For logged-in users only.

Design: https://invis.io/JP13194K9QFA

​Pricing: Free during the beta period

Extension Restrictions logic:

• Disallow enabling the extension on the site if its plan is lower than eCommerce
• This extension is only available for Ecommerce plan

2) Abandoned Cart Recovery extension not installed or subscription expired error message

When admin performs any action related to Abandoned cart admin UI (listed in the list below) layouts AND Abandoned Cart Recovery extension is Disabled or Abandoned Cart Recovery extension subscription is expired

• Show error message: “This action can't be performed: Abandoned Cart Recovery extension is disabled or expired for this site”

Likewise, if the Restore cart functionality is attempted:

• Following the restore cart link
  • redirect to the system page "error-page" and set error message to the liquid - this.ErrorMessage

3) Add shop settings for abandoned carts and improve current settings

Add following setting to ‘eCommerce’ > ‘Settings’ > ‘Shop Settings’:

• “Abandoned cart time in Hours” (number)
  • 4 (default)
  • Default adjustment based on Shopping Cart Lifetime:
    • if shopping cart lifetime is less than or equal to 4 AND greater than 1
      • set Abandoned cart time to (shoppingCartLifetime minus 1) as default value
    • if shopping cart lifetime is equal to 1
      • set Abandoned cart time to 1 as default value
    • if shopping cart lifetime is equal to 0
      • set Abandoned cart time to 1 as default value
      • set shopping cart lifetime=1
  • allowed range between 1 and 876000

Logic:

Applied to the shopping cart created via add to cart process (skip shopping carts that is created on generic payment form submissions, event payment forms, and recurring forms):

• Number of hours after latest update in the cart that determine shopping cart as Abandoned (should be always less or equal to the shopping cart lifetime)
• When shopping cart becomes Abandoned; create a history record (Shopping Cart Become Abandoned Recording). See “History Data” below.

Validation:

• If Abandoned cart time is bigger than shopping cart lifetime, show Error Message “The abandoned cart time shouldn't be bigger than the shopping cart lifetime”
• If there is an enabled abandoned cart email notification which time is bigger than the shopping cart lifetime, show Error Message “There is at least one abandoned cart notification which time is bigger than the shopping cart lifetime”
• Update allowed range for Shopping Cart Lifetime (it should be in range between 1 and 876000)

DESIGN: https://invis.io/CW10NLS86GBJ 

4) Abandoned Cart Emails

Add tab to ‘Email Notifications’ > ‘Emails’ page called “Abandoned Cart Emails”

Shows list of emails by new email type "Abandoned Cart Email"

Tab will only be visible when the Abandoned Cart Recovery extension is enabled/active.

5) Abandoned Cart Email

LIQUID object should contain following data:

• ShoppingCart
  • same object as on shopping cart
• TrackingURL
  • see (6) Tracking URL logic
• RestoreCartURL
  • see (7) Restore cart functionality

Email Sending Logic:

• Create a history record (Email Sent Recording) regarding Email sent. See “History Data” below.
• Add following image tag before closing </body> tag of the email content
  •  <img src="{{this.trackingURL}}" height="1" width="1">
• Send email

On email save:

• disallow saving if there is no </body> tag in this email content OR the assigned email template (since this is required for the pixel image tracking). Show error message “Email content should contains <body></body> tag”
• disallow saving if there is no{{this.RestoreCartURL}}tag in the content. Show error message “Email content must contains{{this.RestoreCartURL}}liquid tag”

6) Tracking URL logic

• Pattern
  • https://<siteDomain>/public/api/track-email/abandoned-cart/open?id=<ShoppingCartid>&notificationId=<idOfAbandonedCartNotificationStep>&guid=<guid>
• Logic
  • If there is NO Email Opened Recording history record with such guid in the history:
    • Create a history record (Email Opened Recording) to track email opening events. See “History Data” below.
  • return 1px x 1px transparent png image as a response (with Content-Type: image/png)

7) Restore cart functionality

• Restore cart link Pattern
  • https://<siteDomain>/public/api/abandoned-cart/restore?id=<ShoppingCartid>&abandonedCartNotificationId=<idOfAabandonedCartNotificationStep>
• Logic
  • this request should restore the shopping cart and redirect the user to the shopping cart page
    • Get Shopping Cart by id
    • Create a history record (Shopping Cart Recovered Recording) to track shopping cart recovery. See “History Data” below.
    • restore Shopping Cart
      • set it as a current active shopping cart
    • redirect a user to the /shopping-cart page

8) Abandoned Cart Extension Page

Add new menu item

• ‘Extensions’ > ‘Abandoned Cart Recovery’

Content

• Notifications
• Abandoned Carts
• Reports

Menu item and page will only display if the Abandoned Cart Recovery extension is enabled/active.

9) Abandoned Cart Recovery -> Notifications tab

List of all Abandoned Cart Notifications ordered by interval set in ‘Send Email After’ setting.

• Table columns
  • Send Email After
    • {SendEmailAfter value}Hours From Abandonment
  • Emails Sent
    • Number of sent emails
  • Email Open Rate
    • Percent of unique opened emails among all sent emails
  • Cart Recovery Rate
    • Percent of all Recovered shopping carts among all shopping carts marked as Abandoned
  • Actions
• each row
  • has edit button
  • has delete buttons
    • when deleting the notification - do not restore its hour statistics when new notification with the same interval will be created, for example:
      • 12 hours notification has 25% recovery rate  and 30% open rate
      • user deletes this notification
      • then user creates new notification and sets interval to 12 hours
      • new created notification should have 0% recovery rate and 0% open rate
  • may display disabled state
• ability to sort by columns - Name ASC (default)
• pagination
• ability to bulk delete selected items
• ability to filter items by state:
  • All (default)
  • Enabled
  • Disabled
• Remember last selected show filter

DESIGN: https://invis.io/8C10J9OPQM7D 

Add new notification functionality:

• “Add New Notification” button
  • Display Add/Edit Form side panel
    • Send Email After Cart Abandonment Delay (in hrs) (numeric)
      • allowed range between 1 and 876000
      • number of hours should be less than eCommerce -> Settings -> Shop Settings -> Shopping Cart Lifetime In Hours. Else error message: “Abandoned cart notification can't be created outside of the shopping cart lifetime.”
      • validate that selected number of hours is still not selected for another email. Else error message: “Abandoned cart notification for the selected delay is already exists”
    • Email (dropdown - list of Abandoned Cart Emails)
    • Enabled

DESIGN: https://projects.invisionapp.com/share/8C10J9OPQM7D#/screens/447828839

10) ‘Abandoned Cart Recovery’ > ‘Abandoned Carts’ tab

List of all abandoned carts.

• Table columns
  • Name (left empty if shopping cart has no owner)
  • Email
  • Total Cost
  • Lifetime
    • Difference in hours between Current Date Time and Created Date Time
    • Pattern
      • if difference is more than 24 hours:
        [<numberOfDays> days  ]<numberOfHours> hours
      • if difference is less than 24 hours:
        [<numberOfHours> hours]<numberOfMinutes> minutes
    • Sorting should be done by decimal, eg:
      • 3 hrs and 30 minutes would be 3.50
      • 3 hrs and 31 minutes would be 3.52
  • Created Date Time
  • Last Update Date
  • Expiry Date (datetime when shopping cart will be deleted)
  • Actions
• each row
  • has view and delete buttons
• ability to sort by columns (Lifetime DESC - default)
• pagination
• ability to bulk delete selected items

DESIGN: https://projects.invisionapp.com/share/8C10J9OPQM7D#/screens/447828837

Abandoned Cart Details page

• Details tab ( https://prnt.sc/ZIAX_np-6OGI)
  • Currency/Country
  • Assigned To (email)
  • Total Cost
  • Created Date Time
  • Last Update Date
  • Expiry Date
• Products tab
  • shows shopping cart info (order lines, discount, gift voucher, shipping option data, etc.)

DESIGN: https://projects.invisionapp.com/share/8C10J9OPQM7D#/screens/447828838

11) History data

1. Email Sent Recording (Store the following data)
   1. ShoppingCartId
   2. Email (shopping cart owner email)
   3. AbandonedCartNotificationId
   4. Record DateTime
   5. Type (EmailSent)
2. Email Opened Recording (Store the following data)
   1. ShoppingCartId
   2. Email (shopping cart owner email)
   3. AbandonedCartNotificationId
   4. Record DateTime
   5. Type (EmailOpened)
3. Shopping Cart Recovered Recording (Store the following data)
   1. ShoppingCartId
   2. Email (shopping cart owner email)
   3. AbandonedCartNotificationId
   4. Record DateTime
   5. Type (ShoppingCartRecovered)
4. Shopping Cart Become Abandoned Recording (Store the following data)
   1. ShoppingCartId
   2. TotalCost
   3. Email (shopping cart owner email)
   4. Record DateTime
   5. Type (ShoppingCartBecomeAbandoned)
5. Shopping Cart Become Deleted Recording (Store the following data)
   1. ShoppingCartId
   2. TotalCost
   3. Email (shopping cart owner email)
   4. Record DateTime
   5. Type (ShoppingCartDeleted)

12) Shopping cart delete operation upgrade

Before shopping cart delete action add a history record (Shopping Cart Become Deleted Recording). See (11.5)

13)  ‘Abandoned Cart Recovery’ > ‘Reports’ tab

• Abandoned and recovered carts
• Abandoned and recovered carts amounts
• Abandoned and recovered carts report

DESIGN: https://projects.invisionapp.com/share/C2130V1FMP5X#/screens

14) Analytics dashboard charts

Provide ability to add

• Abandoned and recovered carts
• Abandoned and recovered carts amounts
• Abandoned and recovered carts report

Show these charts only if Abandoned Cart Recovery extension is enabled/active

DESIGN: https://invis.io/7910J9P1H3CG

15) Admin User Role Restrictions

Add following admin user role restrictions

• Abandoned Carts
  • Can View
  • Can Delete
• Abandoned Cart Notifications
  • Can View
  • Can Add
  • Can Edit
  • Can Delete
• Abandoned Cart Emails
  • Can View
    • allows to see Abandoned Cart Emails tab on ‘Email Notifications’ > ‘Emails’ page
  • Can Add
    • allows to show add button on ‘Email Notifications’ > ‘Emails’ page (tab Abandoned Cart Emails).
    • allows to show add new follow-up email button on create follow-up form
  • Can Edit
  • Can Delete
    • these 2 restriction above should allow to view ‘edit’ and ‘delete’ buttons on ‘Email Notifications’ > ‘Emails’ page (tab Abandoned Cart Emails)
• Abandoned Cart Report
  • Can View

Show these restrictions only if Abandoned Cart Recovery extension is enabled/active.

On create new admin user role set all restrictions above to true by default.

Disable detail layout feature

New module setting:

Add new module setting called “Disable detail layout” (checkbox - false by default)

Logic:

If ‘Disable detail layout’ is TRUE:

• Make unreachable all module items URLs of the module
  • add "?<moduleId>/" to the module slug and hide it on module settings tab
    • this action will prevent item urls from being accessible since saved url will contain ? character which CMS will determine as a URL parameter, eg:
      • /detail-allowed-module-slug/item-slug-1
        • could be accessed by URL https://domain.my/detail-allowed-module-slug/item-slug-1?someParam=33
        • because item url will be taken as /detail-allowed-module-slug/item-slug-1
      • ?1234/detail-not-allowed-module-slug/item-slug-2
        • could NOT be accessed by any URL. For example https://domain.my/?1234/detail-not-allowed-module-slug/item-slug-2
        • will be determined as /
• Show module URL field as inactive.
  • Show but do not allow to change it from Admin UI and ignore changing on Backend
• Show module item URL field as inactive.
  • Show but do not allow to change it from Admin UI and ignore changing on Backend
    • on edit module item action from Admin UI
    • on edit module item from frontend action
• Hide Detail Layout dropdown on add/edit module item form in admin UI
  • preset "Don't use" value as default on backend on create item
• Do not add items of the module to the SITEMAP
• On Import process if creating a new item
  • if there is a detail layout column and it's value is empty set ‘Don't use’ layout instead of the first existed detail layout of the module (like it works now and should work when ‘Disable detail layout’ is FALSE)

The logic of Detail layout "Don't use" logic improvement

If module item has Detail layout property selected as "Don't use"

• show 404 page content (with 404 status code) when accessing the item by URL
• Do not add such items to the SITEMAP

Module item rating

1) Module item rating in the items list and detail forms (admin UI)

Provide ability to add Item Rating column in module -> table setup to show rating in item list view

Add new system property to Edit module item form

• “Item Rating” (text)
  • Always readonly
  • if somehow value is posted via edit item endpoint, ignore value from request AND do NOT override value in DB (it should be calculated automatically once comments rating for this item are added edited or deleted)
  • Value=Average rating posted via comments to this item (Approved ratings counted only)

2) New module item liquid property

Add a new property to the module item (in liquid)

• “Item_Rating” (numeric)
  • Value=Average rating posted via comments to this item (Approved ratings counted only)

3) Searching logic

Provide the ability to search by ‘Item_Rating’ property when using{% component type:"module", isSearchResult:"true"%}for searching, same as for Number custom property - via requesting a range using:

• prop_Item_Rating_Min
• prop_Item_Rating_Max

4) Sorting logic

Provide the ability to sort by ‘Item_Rating’ field in module component tag, eg:

{% component type:"module", sortBy: "Item_Rating", sortOder: "ASC/DESC" %}

Add full Urls to Export

Add additional column in the export module item file (as a display value only) for the full item URL (parent and slug)

• Column title “URL list”
  • list of all item URLs separated by ;
  • placed after ‘Parents’ column
  • on import action; ignore this column (for display/export purpose only)

Example:
/module-slug/item-slug;/module-slug/parent-item-slug/item-slug

Rename Site information to Site Globals

1) Rename "Site information" to "Site Globals" in ‘Settings’ > ‘Site Information’ page

Example: https://prnt.sc/KpeG14rpKr4w

2) Change liquid aliases accordingly

• {{siteinformation}}to{{siteglobals}}
• {{si}}to{{sg}}

NOTE: Provide backward compatibility so that{{siteinformation}}and{{si}}will still continue to work.

3) Change "Site information" to "Site Globals" in OSE

OSE Related Improvements

• Change the page tab title to “Edit <Page name>'”
• If a multiline custom property or a Content system property contains <script, <style, {{, {% this property should be blocked for editing via OSE.
• If a multiline custom property or a Content system property contains blocks with a data attribute 'cms_ose_editable_text' all content from this block should be parsed into a separate WYSIWYG like a multiline custom property. A title for this section should be determined from a data attribute 'cms_ose_editable_text_title'. If this attribute is not found the title for this WYSIWYG should be constructed as follows: '<this property name> Text Block <index>'.
• If some page doesn't have custom modules for editing and this page can be edited, all editable properties should be shown by default on the toolbox.
• Add a javascript event trigger 'CMS_TriggerRefreshOSEItems' for a 'load more' function on the site frontend for a list of module items refreshing on the toolbox. This one should be triggered after AJAX.
• Do some small UI/UX changes: https://invis.io/9U12ZSAU5NZY
• Add a module name to the toolbox title
• Add an "add new item" button on the items list at the first position (if it's available on a module).

Multiline Text property changes

• Rename ‘Enable WYSIWYG’ to ‘WYSIWYG’
  • default unchecked
  • if selected - allow the ability to use WYSIWYG view on add/edit item form in Admin
• add ‘Code Editor‘ setting
  • default checked
  • if selected - allow the ability to use Code view on add/edit item form in Admin
• if no option is selected - show the property as general textarea.

Eg: https://prnt.sc/c4PmuscwOLMd

Feature flags changes (v6.8)

Bug

Liquid in domain_settings

https://treepl.slack.com/archives/C023SU50YQP/p1659597522511109

Liquid data is not correctly outputting the Currency Name.

Bug

CRM Contact - in secure zone not display ID

https://treepl.slack.com/archives/C023SU50YQP/p1655388079321519

CRMContacts component is not displaying the Secure Zone ID in the Secure Zone data.

Bug

Site Information - edit datapicker

Go to Site Information

In option Date Time add possibility to set time https://prnt.sc/aE6rxofG-tnr

https://treepl.slack.com/archives/C023SU50YQP/p1658336160885129

Bug

Page caching - desktop/mobile

Page is caching ‘device_type’ value in Liquid ‘request’ object.

Bug

Create/update item from front

Using <input type="checkbox" name="prop_Enabled" value="false"> in a custom module Add and Edit form to set it’s Enabled state doesn't seem to work.   https://treepl.slack.com/archives/C023SU50YQP/p1663164691768169

Site Storage Email Notification

Extend the "approaching limit" email notification repetition for site storage (when storage exceeds 90% capacity)

Now to be once a week instead of once a day

Preview and Draft Mode

Preview and Draft mode on pages and custom modules.

DESIGN:

https://invis.io/TXX3577QCWJ 

1) Draft Mode logic

Provide the ability to:

• save draft content of ‘Settings’ and ‘SEO’ tabs for Module Items
• save draft content of ‘Settings’ tab for Content Templates
• delete the draft version of the content
• switch between draft and live mode
• preview draft
  • the draft should be accessible by the same URL but with GET param ?DraftPreview=true
  • if no draft content is available - show live content of the item
• Save draft content to live
  • clicking on the ‘Publish’ button commits the draft version to live (overriding the previous live version)
  • draft content should be deleted on this operation

On opening edit item form

• always show live version of the content

2) FTP sync of pages logic

• Changes made via FTP applied to Live content ONLY

3) Special Properties Exceptions

Changing these fields on draft should be ignored:

• SKU Code
• URL slug
• Parent items
• Home page state
• Secure zone assignment
• Product Downloadable File
• Recurring Type

eg: https://prnt.sc/sba18v 

4) Draft accessibility

Ability to switch to draft mode should be allowed/restricted via Admin User Roles for the ‘Can View And Manage Draft’ option.

5) Admin User Roles/Permissions

Add permissions option to the following module groups:

• Each Custom module permissions group
• Default Custom Module permissions group
• Page permissions group
• Content Template permissions group
• Blogs permissions group
• Blog Posts permissions group
• Banner Groups permissions group
• Banners permissions group
• Galleries/Sliders permissions group
• Slides permissions group
• FAQ Groups permissions
• FAQ Questions permissions
• Authors permissions group
• Products permissions group
• Catalogs permissions group
• Events Group permissions
• Event permissions group

Permissions option:

• Can View And Manage Draft
  if restriction is disabled; do not show switcher between draft and live mode on item edit form in admin [UI]

{{order}} Object To Be Generally Available

Original request:
https://webinone.com/public-backlog-state/request/_order-object-to-be-generally-available

Documentation (shown all places where order object is not available but should)
https://docs.webinone.com/liquid/order-object#secOrderObjectAvailability
Screen shot: https://prnt.sc/ytsrt6

1) BUG Fix:

Supplier System Email:
In ‘Email template’ - {{this.order}} data not working

2) BUG Fix:

All system Emails and autoresponders:
‘From name’ and ‘Subject’ are not parsed via liquid with the same context as body.

3) Improvement: When product with supplier is purchased add supplier email to the order line object https://prnt.sc/s5dy3k 

4) Improvement: Further ‘order’ object support:
Add ‘this.order’ object to the following places (set null value if no payment occurred)

• form thankyou page
  • for paid secure membership (generic form)
• workflow (Body)
  • for paid secure membership (generic form)
• workflow (From, Subject fields)
  • for paid secure membership (generic form)
  • for paid form (generic form)
  • for paid form (single item form)
  • for paid form (checkout form)
• autoresponer (Body)
  • for paid secure membership (generic form)
• autoresponer (From, Subject fields)
  • for paid secure membership (generic form)
• Supplier Email (From, Subject fields)
  • for paid form (checkout form)
• Low Stock Email (From, Subject fields)
  • for paid form (checkout form)
• Gift Voucher Email (Body)
  • for paid form (checkout form)
  • custom send via the admin http://prntscr.com/ytvvbc
• Gift Voucher Email (From, Subject fields)
  • for paid form (checkout form)
  • custom send via the admin http://prntscr.com/ytvvbc
• Secure Zone Details Email (Body)
  • for paid secure membership (generic form)
• Secure Zone Details Email (From, Subject fields)
  • for paid secure membership (generic form)

[Portal] Emergency Settings

Add a new page in the Portal for Emergency Settings

Page should contain the following settings (just store saved data. No additional logic based on these are required)

All fields are NOT required

• First name
• Last name
• Email
• Phone number
• Any additional info

Design:
https://invis.io/8512E2GQU7XY 

Add Shipping Address Fields to Form Builder

1) Address fields on the form settings

Add ‘Shipping Address’ and ‘Billing Address’ buttons to Form builder http://prntscr.com/1juqgk3.

Once selected add a group of fields to the default layout of the form.

Show them on the form builder as a group of fields: https://prnt.sc/fVWSzhSGvoa-

Fields that should be added to the form layout are:

• Shipping Address
  • Payment_ShippingAddress (Shipping Address)
  • Payment_ShippingCity (Shipping City)
  • Payment_ShippingState (Shipping State)
  • Payment_ShippingZipCode (Shipping ZIP Code)
  • Payment_ShippingCountry (Shipping Country)

• Billing Address
  • Payment_BillingAddress (Billing Address)
  • Payment_BillingCity (Billing City)
  • Payment_BillingState (Billing State)
  • Payment_BillingZipCode (Billing ZIP Code)
  • Payment_BillingCountry (Billing Country)

Both fields can be marked as required. And once marked as required - all fields inside the group become required (address, city, zip etc) and vice-versa.

2) Form submission flow

When such a form is submitted - add ‘Shipping Address’ and ‘Billing Address’ data to the CRM Order object (like it works previously for Shipping Address fields)

NOTE:

• For backward compatibility - use value of the ‘formData.Zip_Code’ as value for shipping zip code as well as the value of ‘formData.Payment_ShippingZipCode’
  • if both occurred in the ‘formData’ then use ‘formData.Payment_ShippingZipCode’
• For backward compatibility - always check if Shipping fields are present in ‘formData’ even if they are not selected on the form builder.
• Do not use value of ‘Payment_ShippingCountry’ on form (type “checkout”). Use value of the selected shipping country from the shopping cart.

3) Attach billing and shipping address fields to appropriate CRM entities

• Add ‘billing address’ fields to the ‘contact’ entity
  • migrate data from contact address to contact billing address
  • setup payment logic to take the address from the contact billing address field instead of the contact address field
    • if the billing address field is empty - use the contact address fields
• Add ‘shipping address’ fields to the ‘order’ entity

4) Update the billing address from the payment gateway

• When changes to the billing address come from payment providers update ‘contact billing address’ fields instead of ‘contact address’ fields

5) Liquid output

• Add the following properties to the ‘contact’ liquid object
  • BillingAddress
  • BillingCity
  • BillingState
  • BillingZipCode
  • BillingCountry

• Contact liquid object occurrence
  • {{request.currentmember}}
  • item from {% component type: "CRMContacts" %}
  • {{ this.member }} on system pages
  • {{ this.member }} on system emails
  • {{ this.member }} on autoresponder emails
    • on form submission
    • on create module item submission
  • {{ this.member }} on workflow and follow-up emails

6) Add these fields to Import/Export processes

• add billing address fields to contact import/export
• add shipping address to order import/export

7) Restore to default "checkout" form upgrade

• Remove adding hard-coded shipping fields to the HTML layout of the form with the type "checkout" when clicking "restore to default" on form layout

Alphabetised Related Products list

Original description:

Currently the ‘related products’ for any product are not listed in alphabetical order and there is no search field.

This means you have to try to locate the product you want by scrolling through a random list of products, to try and find the right product to add as ‘related’.

This needs to be alphabetised based on the name of the product as well as have a search function so you can quickly locate the correct product to add.

Improvement:

Both alphabetical list and search fields added to Related Products UI.

DESIGN:
https://invis.io/V810G318WBN6

eCommerce User Input Field For Products

Allow the capture of user input data (text) against a purchased product.

New Attribute type

• User Input field

Output via liquid

• Add new attribute type to ‘item_attributes’ liquid component.
• Should be output as a text input on the default attributes layout.
• Add it to the orderline of ‘order’ and ‘shopping cart’ object (the same as any other attribute data)

Advanced Logic of the attribute type

• If a product with User Input attribute is added to cart more than once, unique text input should specify unique orderline (order, shopping cart), as opposed to adding an additional quality to the same product orderline.

Product Import/Export

Output value via Export function and apply value via an Import

Format:

• [attribute name][is_required]|[attribute_type]|[is_inventory_item]:;
  • [attribute_type] is ‘8’ or ‘UserInput’

Example

• Test attr text*|UserInput|False:;

Output via admin UI

• Display in “Order” > “Products” on orderline

Updated Output in default layouts

• invoice email
• shopping cart
• item_attributes component default layout

DESIGN:
https://invis.io/DY10G2CWHK9S 

Custom reCAPTCHA Key Setup

1) Add new properties to the Settings -> Misc => Recaptcha Settings group (under Recaptcha Version field)

• reCAPTCHA v2 Site Key
• reCAPTCHA v2 Secret Key
• reCAPTCHA v3 Site Key
• reCAPTCHA v3 Secret Key

All of these fields should be empty by default

2) Rename incorrect reCAPTCHA labels

• Rename all ‘Recaptcha’ labels in admin to ‘reCAPTCHA’

3) Add the reCaptcha property to the ‘this’ object of the form:

• {{this.recaptcha_sitekey}}  
  • the value should be determined based on what reCaptcha is added to the form.
  • If no reCaptcha is added to the form - set null

Use Settings -> Misc => reCAPTCHA Settings group fields to retrieve keys for the object.

• If reCAPTCHA v2 Site Key, reCAPTCHA v3 Site Key are empty - use our system keys

4) Add property ‘system_recaptcha_sitekey’ property to the ‘request’ liquid object which renders the key as saved above or the system key if no custom key is available:

• {{request.system_recaptcha_sitekey}}

5) Replace reCAPTCHA key instances for the following:

• all web form layouts
• default form layouts  (when generated by restore to default request)
• system form layouts (when generated by toolbox request)
• System pages
  • 401
  • reset-password
  • request-reset-password
• System pages default layouts (when generated by restore to default request)
  • 401
  • reset-password
  • request-reset-password
• CMS ‘Add scripts to head’ functionality (for Google reCAPTCHA API)

6) Change reCaptcha validation logic to use the secret key and site key stored in Settings -> Misc => reCAPTCHA Settings (or system keys if null)

The feature is based on:
https://webinone.com/public-backlog-state/request/custom-recaptcha-key-setup

Custom Modules - Show Image thumbnail in Table Columns

Original Description

The ability to show thumbnail in Custom Module table.

Where a Custom Module has an Item Property>Custom Property that is type Media.

In that Custom Module’s > Table of items can we add the option to show a thumbnail of the actual image as well as the current option to show its path.

https://webinone.com/public-backlog-state/request/custom-modules-show-image-thumbnail-in-table-columns

Improvement:

Show the value of the media property type (if it’s a displayable image format) as an image thumbnail.

Add tooltip on hover that will show image URL.

Images Caching Issues

Add ‘Empty Image Cache’ button to the gear menu.

Once clicked - clear all Image processor cache.

Once done - show message: “Image cache was successfully cleared.”

DESIGN:
https://invis.io/N4YDTMBRUFY

Source:
https://forum.treepl.co/t/images-caching-issues-in-custom-modules-blog-posts/106

Event Anniversary Emails

1) Create a new Settings section on a module settings page

Called “Follow Up Emails” which includes the option:

• Enable Follow-Up Emails (checkbox) - preset to ‘true’ for Events module

Show section only if “Module” > “Advanced Settings” > “Enable bookings” is true.

2) Create a new tab "DEFAULT FOLLOW-UP EMAILS" on a module edit page

Display only if the module has ‘Follow Up Emails’ -> ‘Enable Follow-Up Emails’ setting set to ‘true’ AND if ‘Module’ -> ‘Advanced Settings’ -> ‘Enable bookings’ is true

Content:

• List of default follow-up emails
• ability to add new default follow-up email
• ability to edit and delete default follow up email

DESIGN:
https://projects.invisionapp.com/share/JA10JVKP2K78#/screens/447175909

Add ‘Date Field’ column after ‘Delivery Type’

• Show field display name if field exists
• Show saved field alias if field doesn't exist any more (but alias is saved for a follow-up)

3) Create a new tab "CUSTOM FOLLOW-UP EMAILS" on a module item edit page

• Display only if the module has ‘Follow Up Emails’ -> ‘Enable Follow-Up Emails’ setting set to ‘true AND if ‘Module’ -> ‘Advanced Settings’ -> ‘Enable bookings’ is true.

Content

• “Send only custom follow-up emails” (checkbox)
  • When enabled, allow to add/edit/delete custom follow-up emails
    • List of custom follow-up emails
    • ability to add new custom follow-up email
    • ability to edit and delete custom follow up email

DESIGN:
https://projects.invisionapp.com/share/JA10JVKP2K78#/screens/447175909

• Set title Delivery Time instead Delivery Date
• Add Date Field column after Delivery Type
  • Show field display name if field exists
  • Show saved field alias if field doesn't exist any more (but alias is saved for a follow-up)

4) Change “Email Notification” -> “Workflow emails” page

Rename default admin menu item name from “Workflow Emails” to “Emails” and EntityAlias from ‘WorkflowEmails’ to ‘Emails’

In custom admin menus, find menu item with alias ‘WorkflowEmails’ and rename to ‘Emails’

Add tabs:

• Workflow Emails
  • Place existing listing and “add workflow emails” logic here
• Follow-Up Emails
  • Add listing and add/edit/delete Follow-up emails logic here
  • Show tab only if site plan is BUSINESS or higher

Set following restrictions based on site plan

• Show ‘Email Notification’ -> ‘Emails’ page starting from BUSINESS plan
  • Show ‘Workflow Emails’ tab starting from PRO plan
  • Show ‘Follow-Up Emails’ tab starting from BUSINESS plan

5) Create/edit follow up email logic

• Select one of the already created follow-up emails or create a new one (like it works on workflows - https://prnt.sc/TyNsogEjZwIa)
• Choose the trigger date field
  • Release Date
  • Expiry Date
  • Event Date Start
    • show if the module has ‘Advanced Settings’ -> ‘Enable Booking’ = true
  • Event Date End
    • show if the module has ‘Advanced Settings’ -> ‘Enable Booking’ = true
  • all custom properties with type datetime
• Choose a time shift for the chosen trigger date field: https://prnt.sc/nKOv35KSrxTw
  • Delivery Time (numeric)
  • Delivery Type (dropdown)
    • Days After
    • Days Before
    • Hours After
    • Hours Before
  • Date Field (dropdown) - list of module item date fields
    • system fields:
      • Release Date
      • Expiration Date
      • Event Date Start
      • Event Date End
    • custom fields (display name is the name of the custom field)
  • on edit
    • do not allow to save follow-up if Date Field is empty (only set field to be empty if the saved alias belongs to the date field that doesn't exist anymore)

6) Follow-Up Email sending logic

If the module has’Follow Up Emails’ -> ‘Enable Follow-Up Emails’ setting set to ‘true’ AND ‘Module’ -> ‘Advanced Settings’ -> ‘Enable bookings’ is true

• Schedule sending follow-up emails for each module item (for each subscriber to this module item) based on the selected date field:
  • For module items that have ‘Send only custom follow-up emails’ = true
    • send only custom follow-up emails
      • if there are no custom follow-up emails in the list - no email will be sent for this module item
  • For module items that have ‘Send only custom follow-up emails’ = false
    • send only default follow-up emails

7) Email liquid

‘this’ object should contain the following properties:

• item
  • object that contains same fields as item from component type module (including event fields)
• member
  • module item subscriber

8) Site Plan Restrictions

Allow view and use of ‘Follow Up Emails’ on module settings if site plan is PRO or higher

Hide DEFAULT FOLLOW-UP EMAILS on module view and CUSTOM FOLLOW-UP EMAILS tab on module item view if site plan is lower than BUSINESS

If site's plan is ESSENTIAL

• disallow sending followup emails
• if plan will be restored to BUSINESS or higher all follow-up emails that wasn't sent while site plan was ESSENTIAL should NOT be sent after plan upgrade

9) Admin User Role permissions

Ability to enable/disable Default and custom followup emails should be managed by ‘Can Edit Basic Module Settings’ module's restriction

Add following admin user role permissions:

• Emails
  • Can View
    • if disabled; hide 'Email Notifications' -> 'Emails' menu item and do not allow to open 'Email Notifications' -> 'Emails' page
• Follow-ups
  • Can View
    • if disabled; hide DEFAULT FOLLOW-UP EMAILS on module view and CUSTOM FOLLOW-UP EMAILS tab on module item view
  • Can Add
  • Can Edit
  • Can Delete
    • these 3 restriction above should allow to view ‘add’, ‘edit’ and ‘delete’ buttons on DEFAULT and CUSTOM follow-ups pages
• Follow-up Emails
  • Can View
    • allows to see ‘Follow-up Emails’ tab on mail ‘Notifications’ -> ‘Emails’ page
  • Can Add
    • allows to show ‘add’ button on 'Email Notifications' -> 'Emails' page (tab ‘Follow-up Emails’)
    • allows to show ‘Add new follow-up email’ button on create follow-up form
  • Can Edit
  • Can Delete
    • these 2 restriction above should allow to view ‘edit’ and ‘delete’ buttons on 'Email Notifications' -> 'Emails' page (tab ‘Follow-up Emails’)

On create new admin user role

• set all permissions above to true by default

For all existed admin user roles

• All permissions above should be false
• On update from v6.5 to v6.6
• Add to all existing admin user roles following permissions with preset value
  • ‘Emails’ -> ‘Can View’ with value TRUE if
    • current user role permission has ‘Workflow Emails’ -> ‘Can View’ == true

10) Duplicating module item logic

Duplicate ‘Send only custom follow-up emails’ checkbox when duplicating the module item

Duplicate ‘Custom follow-ups’  when duplicating the module item

11) Duplicating module logic

Duplicate ‘Enable Default Follow-Up Emails’ AND ‘Enable Custom Follow-Up Emails’ settings

Duplicate ‘Default follow-ups’  when duplicating the module

12) Import/Export of module items

Add ‘Send only custom follow-up emails’ checkbox to import/export process

‘Follow-ups’ should NOT be added to module item import/export process

13)  Import/Export of module logic

Add ‘Enable Default Follow-Up Emails’ AND ‘Enable Custom Follow-Up Emails’ checkboxes to module import/export process

Do NOT add ‘Default follow-ups’  to export file

HTML security for GET url params in liquid request object

Add new filter to liquid

• unescape

This filter should decode html entities to its original strings (as an opposite to ‘escape’ filter)

Example

• {{"&lt;br&gt;" | unescape}}
• result = <br>

Improve liquid XSS security by implementing the following improvements in the ‘request.request_url.params’ liquid object

• convert all URL get parameters values to become HTML decoded

Example:

• URL:
  /my_page?myParam=<script>alert(1);</script>
• page content:
  {{request.request_url.params.myParam}}
• expected output
  • &lt;script&gt;alert(1);&lt;/script&gt;
• in case you will need to output original html - using this filter should help
  • {{request.request_url.params.myParam | unescape }}

 Add "Is Main Order" and "Is Recurring Order" property to order fields on Contact and order custom report

Improve Contacts and Orders custom report

• Add "Is Main Order" property to order fields
  • type
    • boolean
  • Add it to the 'Fields' tab ('Order Fields 'section)
  • Add it to the ‘Filters’ tab
  • Logic: Shows if the current order is a main or a suborder
• Add "Is Recurring Order" property to order fields
  • type
    • boolean
  • Add it to the 'Fields' tab ('Order Fields 'section)
  • Add it to the ‘Filters’ tab
  • Logic: Shows if the current order is a main or a suborder

Secure media file - uploaded images display broken

Secure media file - uploaded images display broken

If the user creates an item from the front and upload an image - (media-files folder should be SECURE https://prnt.sc/PsCLJTjnbpig 

Search engineer - expire date

https://treepl.slack.com/archives/C023SU50YQP/p1650902685179869

If item or custom module has expiry date and those modules expire - they should disappear from site map.

Sitemap and robots.txt

If there is no robot.txt file or it is there but empty, paste it there:

otherwise, we do not update the robots.txt file at all

in this way, we will pre-install default settings on all new sites - and if the file is not empty, then we consider that it is already customized and we do not touch it

and if they want to reset to default - let them delete the file or make it empty

Custom module - name of properties with "-"

https://treepl.slack.com/archives/C023SU50YQP/p1643293254025400

If create name of propery with "-" they do not display correctly on "Update form” on front-end: https://skr.sh/sCIsq9GzArG

ALSO doesn't work in JSON {% component source: "2", layout: "List", object: "collection", collectionVariable: "family", type: "module" %}
<pre>{{family.items[0].mother-in-law}}</pre>

Parent/Child custom module - not correctly display name of properties

1. Go to Event and open settings
2. Create several properties on Events and on Event Group
3. After that change location for those properties
4. Click on the first property and display not correct name of the property https://prnt.sc/KVh33JDdU6NV 

VIDEO:

https://treepl.slack.com/archives/C023SU50YQP/p1650437259226309

Custom Reports Filter improvement

Create Feature flag in Beta section called “Improved Custom Reporting”

1) Create new filters for the custom reports:

LOGIC:

• in
  • Found all items that have a property value that is equal to one of the supplied list of values
• not in
  • Found all items that have a property value that is not equal to all of the supplied list of values

DESIGN:

https://www.screencast.com/t/VPxURiSmdzC

2) Provide the ability to select several secure zones (like on tags):

https://www.screencast.com/t/nLWIsnTY 

https://www.screencast.com/t/coZTiKynZ 

3) Order Status filtering improvement:

Rename current filter ‘Order Status’ to ‘Order Status Type’ (https://prnt.sc/hdByF4EMuxnC)

• It should search by type name as it did before

Create new filter ‘Order Status’

• It should search by status name

DESIGN:

https://invis.io/MQ12BUHBSXCF

4) Restrictions

Add following validation error messages:

On Saving filters if there is at least one ‘In’ or ‘Not In’ filter in filters list AND “Improved Custom Reporting” is disabled:

“Filters “In” and “Not in” are not allowed if feature flag “Improved Custom Reporting” is disabled.”

On Retrieving report results if there is at least one ‘In’ or ‘Not In’ filter in filters list AND “Improved Custom Reporting” is disabled:

“Results can’t be retrieved: Filters “In” and “Not in” are not allowed if feature flag “Improved Custom Reporting” is disabled.”

Custom Reports Generation Improvement

Improvements:

‘Report’ -> ‘Results’ tab

• Improve speed of report generation and pagination.
• Improved logic should be used only if feature flag is enabled

‘Report’ -> ‘Filters’ tab

• Date fields value (Type: "DateTime"):
  Replace current logic of showing all dates from all items (https://www.screencast.com/t/USYltiD1) with datepicker element (like https://www.screencast.com/t/OChM9GVksz)

Server monitoring inside dashboard

Provide the ability to manually set up server instances of the web farm to the CMS DB

If web-farm is enabled for the site - show charts of CPU Utilization for each server on the analytics dashboard

DESIGN:
https://invis.io/6T12DFCCWRGA

Server enabling by schedule inside dashboard + hours balance

Ability to schedule second server enabling for the period of time

Add/edit slot form fields:

• Each slot should be at least 3 hrs long (if you need more time - you can add more duration). Available durations:
  • 3
  • 6
  • 9
  • 12
  • 15
  • 18
  • 21
  • 24
• Allow to choose start time with 1hr step starting from 0:00 AM  till 11:00PM
• Allow to setup slot name

When adding/editing slot:

• do not allow to choose duration;
  • that overlap the next slot
  • if there is no gap (at least 1h) between current slot and next slot
• do not allow to choose time that is busy by another slot or if this time is 1hr gap between slots
• do not allow to decrease slot if it is currently active (only increase slot duration allowed)

Do not allow to delete past and currently active slots:

• Allow deleting of future slots

Show time when next server enabling will be performed

Show hours balance

• Buy more button should show popup with text:
  “Please contact us at support@treepl.co to schedule an extra server upgrade.”

DESIGN:
https://invis.io/6T12DFCCWRGA

Public API for Orders

Create public API endpoints:

• CRM ORDERS
  • [GET] Get Orders List
  • [GET] Get Single Order
  • [PUT] Update Order

See temporary API endpoint documentation here.

API Applications setup:

Add new page:

• Settings -> API Applications

Allow to:

• list applications
  • DESIGN
• create new application
  • Fields
    • Name [string] required
    • Enabled [boolean] default: true
  • DESIGN
• Edit application
  • Fields
    • Name [string] required
    • Enabled [boolean] default: true
  • Allow to
    • copy `ClientId` and `ClientSecret`
    • regenerate `ClientSecret`
      • once regenerated - revoke all existed access tokens for the public API
  • DESIGN
• Delete application
  • Show confirm dialog:
    “Are you sure you want to delete this app?”

Site Plan Restrictions:

Allow using Public API starting Pro plan

Admin User Restrictions:

Add restrictions

• API Applications
  • Can View
  • Can Add
  • Can Edit
  • Can Delete

Retrieve access token endpoint:

• URL
  • /api/v1/oauth/token
• Type
  • POST
• Content-Type
  • application/x-www-form-urlencoded
• POST params
  • grant_type
    • client_credentials
  • client_id
    • {{client_id}}
  • client_secret
    • {{client_secret}}
  • scope
    • public_api

On Success return bearer token (life time 4 hours):

{
"access_token": "tokenStringHere",
"expires_in": 14400,
"scope": "public_api",
"token_type": "Bearer"
 }

If an app is disabled - return error:

{
"ErrorCode" : 401001,
"Message"   : "The application is disabled"
}

If clientId/clientSecret pair wasn't found - return error:

{
"ErrorCode" : 401002,
"Message"   : "Invalid client_id and/or client_secret"
}

If site plan is less than Pro:

{
"ErrorCode" : 401003,
"Message"   : "Public API is restricted for your site plan"
}

If scope is invalid:

{
"ErrorCode" : 401006,
"Message"   : "Invalid Scope"
}

If grant_type is invalid

{
"ErrorCode" : 401007,
"Message"   : "Invalid Grant Type"
}

API version 1

All of the following endpoints requires Authorization header with the token retrieved by retrieve access token endpoint

​If any request doesn't contain access token or token can't be found in DB, show error:

{
"ErrorCode" : 401000,
"Message"   : "Invalid Access Token"
}

ElseIf any request contains access token but it has been expired, show error:

{
"ErrorCode" : 401004,
"Message"   : "Access Token expired"
}

ElseIf an app associated with the access token - is disabled:

{
"ErrorCode" : 401001,
"Message"   : "The application is disabled"
}

ElseIf access token - is revoked:

{
"ErrorCode" : 401005,
"Message"   : "The Access Token has been revoked"
}

Update item from front-end - rewrites ‘media’ type data

When user updates custom module item from front-end it rewrites data in any "Media" type properties.