Card:

This epic is focusing on supporting Service Dependency through SDC UI

The final result should be the same SDC Model created by Import API 

Comments on UI:

MMF

1. Feature is handled as a new tab added to the right panel – we should be able to hide it by configuration
2. Clicking on Checkbox – open ability to define filters
3. On Filters – all fields are mandatory
   1. First – the chosen node input parameters
   2. Second – operation
   3. Third – Source of second field – based on chosen value second line is created – user can choose Static value, Main Service Input parameter,another node in composition (last one not MMF)
4. By opening a filter user can cancel (the X), add (created, back to previous), add another (created, can create a new one – not MMF)

Additional Requirements

1. Ability to move between filters within the filter
2. Removing checkbox – create a warning… if user approved deleting – filters will be deleted
3. On right panel – filter is shown on Hover
4. Have an icon in composition marking the node as dependent (only if doing directly in ONAP)

BE Model should follow TOSCA node filter (just using service filter)  

TOSCA Model

The Service Filter Create two parts in Mode

Mark as Dependent --> Affect the directive

Filters - each filter add a filter to the Service Filter section

Supported Operations: For now equal, greater less

Supported TOSCA Methods:

Decided by UI Source field

static - simple- without method

Get_Property:

By Service Property

Get_Input

By Service input

Testing:

1. Distributed model of service dependency created by UI should be identical to model created by BE in Import CSAR

2. UI must be able to show a service dependency of service created by Import CSAR, meaning - the new UI should enable designer to see and update dependency imported through BE API 

3. UI must follow above expected behaviour