Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-4663

Add an package option to prevent the automatic provisioning of paid pending services

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.4.0
    • Fix Version/s: 5.9.0-b1
    • Component/s: Staff Interface
    • Labels:
      None

      Description

      When using a non-provisioning module, such as the Universal Module, manual action is required by staff to activate the service. However, paid pending services in Blesta are activated automatically if the company setting "Automatically Provision Paid Pending Services" is checked. Rarely would someone want to manually activate every package that is ordered, there would be no need when using a provisioning module like cPanel for example.

      The order form can be set to require manual approval of orders, but a user may have a mix of packages on the order form, some that can be provisioned automatically, and others that cannot.

      The solution seems to be to add an option to packages (Package Add/Edit) that would prevent a pending service using the package from being activated when the "Provision Paid Pending Services" automation task runs.

      The suggestion is:

      • Add a field under Packages Add/Edit, within the Modules tab, at the bottom, called "Hold paid pending services for manual activation" with a tooltip that says, "If this option is checked, pending services using this package must be activated manually. This is intended for use with modules that cannot automate provisioning."

      When the automation task runs, skip any paid pending services that have this option checked.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              15/Dec/23

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 day, 2 hours, 2 minutes
              1d 2h 2m

                Agile