From b39509088a320c5c60b26f74ced3f420d217c376 Mon Sep 17 00:00:00 2001
From: Manamohan <MS00534989@techmahindra.com>
Date: Thu, 12 Dec 2019 15:15:46 +0530
Subject: Implementing scope and action values from SO-DB to SO-Backend

Issue-ID: SO-2513

Change-Id: I002a35a2a8ff4730d45c23d54f0acd4496b8b585
Signed-off-by: Manamohan <MS00534989@Techmahindra.com>
---
 mso-catalog-db/src/test/resources/schema.sql | 2 ++
 1 file changed, 2 insertions(+)

(limited to 'mso-catalog-db/src/test/resources/schema.sql')

diff --git a/mso-catalog-db/src/test/resources/schema.sql b/mso-catalog-db/src/test/resources/schema.sql
index 67584133f8..573d391980 100644
--- a/mso-catalog-db/src/test/resources/schema.sql
+++ b/mso-catalog-db/src/test/resources/schema.sql
@@ -736,6 +736,8 @@ CREATE TABLE `orchestration_flow_reference` (
   `SEQ_NO` int(11) NOT NULL,
   `FLOW_NAME` varchar(200) NOT NULL,
   `FLOW_VERSION` double NOT NULL,
+  `SCOPE` varchar(200) DEFAULT NULL,
+  `ACTION` varchar(200) DEFAULT NULL,
   `NB_REQ_REF_LOOKUP_ID` int(11) NOT NULL,
   PRIMARY KEY (`id`),
   UNIQUE KEY `UK_orchestration_flow_reference` (`COMPOSITE_ACTION`,`FLOW_NAME`,`SEQ_NO`,`NB_REQ_REF_LOOKUP_ID`),
-- 
cgit 1.2.3-korg

