[CORE-1708] Add support for config option logic - Blesta

Details

Type: Story
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 3.4.0
Fix Version/s: Sponsored, 5.1.0-b1
Component/s: Staff Interface
Labels:
None

Description

Create a new option for Configurable Option Groups after 'Edit' and label it "Edit Option Dependencies".

The linked page should control settings for displaying config options based on the selected value of another (we'll call this configurable option logic). This page should contain a tab for each configurable option assigned to the group. Each of these tabs should contain at least a button labeled "Add Condition Set". When clicked a new instance of the following table should be created before the button:

Field Name	Condition	Value	Then	Options
Select menu of config options in this group	Select menu of '>', '<', '=', 'In List'	Select menu of values for the selected option OR text field	Select menu of 'show', 'hide'	Add, Remove

Lists of values should be comma separated, add a tooltip mentioning this.
Value select menu should be should IFF the source field is a select or radio type
A link should be displayed just bellow the table "Remove Set"
A text block should be displayed under the table (before the button but after the link) "OR..."

The DB would be something like:

package_option_group_condition_sets

id	option_group_id	option_id
auto increment Primary Key	Index 1	Index 2

package_option_group_conditionals

id	condition_set_id	trigger_option_id	condition	value	trigger
auto increment Primary Key	Index 1	Index 2	enum(>,<,=,in)	varchar(255)	enum(show,hide)

Option logic would be evaluated client side (javascript) and server side when saved to ensure no invalid options are provided.

When options are fetched for configuration we should also fetch a list of conditionals for the current package (i.e. http://host/blesta/package_options/logic/5), which would return a JSON structure containing the logic for all options in the supplied package.

[
  {
    "option_id": 1,
    "trigger_option_id": 2
    "condition": "=",
    "value": "1024",
    "trigger": "show",
  },
  {
    "option_id": 2,
    "trigger_option_id": 3
    "condition": "=",
    "value": "option value",
    "trigger": "show",
  }
]

Abstracting config option display and validation would be nice