Totally Rewamp the reporting section

The existing Tickets design is not very efficient, this needs to revamped .. in the line of new design like the proposals/order design.

. Add Header / footer section text. Similar to the design shown above the product line item and below. tis button should then hope the html editor to add text. (If we can use db details field to store the header html text good, if not we can go with new fields for header/footer section.) …

Proposal New Design Read More »

As discussed, we will move from side panel to form creation screens. 1. The form will have basic details to be collected. like customer address, name 2. The side area where the log shows.. will cover details like Tax/Disc class, Shipping/Billing address 3. We will intorduce profile upload/Product upload via the new file uploader as …

Customer/Vendor/Material Form view Read More »

Make same style as proposal

* Display a button in the footer to easily change the language. * Dynamically load language only for current session, not a permanent change.

Application maintenance feature where super admin can active/inactive the application.

1. Add new field in versions table "betachk" Zero meaning it will skip the Beta versions 1 meaning it will allow you to update. 2. With Version 1.4 change the update script to skip "_beta" in the Version field, if the flag in the versions table is "1" then it should allow to update to …

Beta Server Update Feature Read More »

Improve the catalog update procedure to also include dynamic db fields. Allow user system to be remotely updated along with existing SaaS client data.

below are the points it will collect during the wizard. 1. Company details 2. Localization details + currency + date timezone 3. SMTP connection for mail sending.