Paul

I see what you're saying, that makes sense.

It's called Cancellation Options because you can do more than just cancel the service, you can schedule it to be canceled at the end of the term, and even stop it from being cancelled if you previously scheduled it to be cancelled but later changed your mind. "Cancellation Options" may not be the best term to describe that, but "Cancel" would be misleading for the above mentioned reasons.

Service meta data (service_fields table values) can be encrypted with AES256. The module controls this, and an example is the cPanel module, which encrypts cPanel passwords. I believe module row data can also be encrypted, but Cody or Tyson will need to confirm.

Almost everything is now being assigned to no fix version, so that we can add them to a specific release as we plan out sprints. Previously, all tasks were assigned the next release, and then shoveled to the subsequent release if not completed.. it's not the right way to do it, and it's too messy. So, we're getting more organized

Good idea, CORE-1467

Yup, CORE-1324. I also suggest setting up 2FA for all staff, if you haven't already.

Have not decided if we are going to use that or not, open to other suggestions. The feature request forum is not terrible, but it's not really designed for feature requests either. Still, it gives us a pretty good idea what people want. When we hear "please add feature xyz" a lot, then we can't ignore it anymore. Making it easier for people to vote has it's upside, but also some people just vote for everything even if they will never need it.

I actually have useresponse.com written on our whiteboard here for possible consideration. Looks like they have a major new version in beta.

We are only fixing bugs and security related issues with the cPanel Extended module. You may be interested in this module - http://www.blesta.com/forums/index.php?/topic/3506-cpanel-module-enhanced-integration/

Also the OP mentions sending invoices once per day. This can be done under Settings > Company > Automation by changing the Interval for Deliver Invoices to 24 hours. Of course, you can't control the time that they are sent, but if the goal is to delay delivery such that the likelihood of someone getting an unpaid invoice that they are paying during checkout then it may suffice. Tyson's recommendation of disabling the delivery of unpaid invoices is probably the best solution however. Settings > Company > Emails. Edit "Invoice Delivery (Unpaid)" and uncheck the "Enabled" box.

Domain manager is a top priority along with mass mailer, and affiliate system. It's also the most complex, and is in the process of being spec'd out. I don't have a precise ETA on it yet, but a 3.5 or 3.6 is likely.

Are you using the Support Manager that ships with Blesta, or Support Manager Pro, a third party modification? I suggest testing with the Support Manager included with Blesta, verify that it is upgraded under Settings > Company > Plugins > Support Manager. If you are using the 3rd party plugin, it may need to be updated to work properly with 3.3.

Yeah, there have been too many tasks that just keep getting pushed forward, rather than assigned to the proper version. We're getting better about this, but it will take another release cycle or so to get everything organized well.

It's not slated for 3.4 Mike, but the Affiliate system is in the process of being fully spec'd out. 3.4 will have a Knowledge Base, Contact logins with ACL permissions, and 2FA for clients and contacts. There will be more, but an Affiliate system is a big task and is unlikely to make it.

There is no direct association between a download from the download manager, and the universal module. The association is that a Package is assigned to the download. Having a service that uses that package gives the client access to the download. The module is irrelevant.

When you add your download under Settings > Plugins > Download Manager, select "Must be logged in", and check "Available to Packages". Then, using the multi-select, move only the packages you want to have access to this download from the right to the left.

Looks really nice!

What about clients that have no services, that you say, invoice manually periodically, or have a recurring invoice set up for? You would still consider these active clients.

If you invoice them for the credit, and then invoice them again when the credit is used you are invoicing the client for $6000 but they are only paying you $3000. Your accountant (or worse, the IRS) might wonder about the discrepancy between billables and revenue. It is better if they just make payment for the credit, and the credit remains on their account until you invoice it. You can subscribe to BCC notices on virtual any client email. Edit your staff group under Settings > System > Staff > Groups, and check under "Email BCC Notices". Whichever ones are enabled here you can then subscribe to under "My Info".

True, but changing SSH ports to something other than 22 cuts down on brute force attacks. Same could be true of changing the admin URL. You should always assume people know what it is, but it's not a bad idea to change it.

Your right. An inactive accounts cannot log in. Only staff can mark an account inactive, or active, or fraud, and a client cannot order new services under an account that is not active unless it is first made active. To be clear, are you asking for the ability for inactive accounts to be made active again by clients who order new services?

We are planning to support drop-in HTML invoice designs that get converted to PDF. These are simpler to make than the 2 PDF invoices we ship with Blesta as those are not simple HTML. Is that what you mean, or do you want to completely replace TCPDF with another engine?

Blesta doesn't allow you to create credits out of thin air. Record Payment > In House Credit is a good way to issue a credit though.

Comments seem like a good idea, do you mean staff and clients can both comment? So, a quote has a threaded reply/conversation with the client? If a quote is accepted, and an invoice results and pro forma is enabled, what is the appropriate action? If a quote is accepted, is that considered a contract and an invoice should be generated, or should a pro forma be generated? In past discussions, there was concert by some that a pro forma invoice doesn't need to be paid. Would it be appropriate to issue a pro forma invoice for an accepted quote?

CORE-1277 exists for Credit Notes. I don't have an ETA on this one yet, but it is planned. CORE-1148 will display payments / credits on invoices, if enabled, and if a payment has been applied toward the invoice whether partial or in full. Tyson was working on this so it is likely to be in 3.4. Also -- while only dates are shown on invoices, Blesta stores all dates/times in the database. So, it would be possible to display times on the invoice with some code modifications.