From 6cd4cd003930da807440647d41fc4a0649bd5a8d Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Thu, 13 Oct 2022 22:34:31 +0530 Subject: [PATCH 01/12] Create script.js --- Background scripts/script.js | 1 + 1 file changed, 1 insertion(+) create mode 100644 Background scripts/script.js diff --git a/Background scripts/script.js b/Background scripts/script.js new file mode 100644 index 0000000000..8b13789179 --- /dev/null +++ b/Background scripts/script.js @@ -0,0 +1 @@ + From dea746afbfa4ab042797614f8c59d03f0c131323 Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Thu, 13 Oct 2022 22:41:57 +0530 Subject: [PATCH 02/12] Delete Background scripts directory --- Background scripts/script.js | 1 - 1 file changed, 1 deletion(-) delete mode 100644 Background scripts/script.js diff --git a/Background scripts/script.js b/Background scripts/script.js deleted file mode 100644 index 8b13789179..0000000000 --- a/Background scripts/script.js +++ /dev/null @@ -1 +0,0 @@ - From 0b8b632b726a4704c8d6619a26360b1bd2408c38 Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Thu, 13 Oct 2022 22:45:07 +0530 Subject: [PATCH 03/12] Create Convert comma separated values in string to columns --- .../Convert comma separated values in string to columns | 1 + 1 file changed, 1 insertion(+) create mode 100644 Useful-scripts/Convert comma separated values in string to columns diff --git a/Useful-scripts/Convert comma separated values in string to columns b/Useful-scripts/Convert comma separated values in string to columns new file mode 100644 index 0000000000..8b13789179 --- /dev/null +++ b/Useful-scripts/Convert comma separated values in string to columns @@ -0,0 +1 @@ + From 3de4451138efcdaf00be703e88aa7af45ecc9fcb Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Thu, 13 Oct 2022 22:54:26 +0530 Subject: [PATCH 04/12] Delete Convert comma separated values in string to columns --- .../Convert comma separated values in string to columns | 1 - 1 file changed, 1 deletion(-) delete mode 100644 Useful-scripts/Convert comma separated values in string to columns diff --git a/Useful-scripts/Convert comma separated values in string to columns b/Useful-scripts/Convert comma separated values in string to columns deleted file mode 100644 index 8b13789179..0000000000 --- a/Useful-scripts/Convert comma separated values in string to columns +++ /dev/null @@ -1 +0,0 @@ - From b0fadf463ace47b2704558e92b8bc9078f864938 Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Sun, 8 Oct 2023 00:23:31 +0530 Subject: [PATCH 05/12] Create MID Server availability inside MID cluster.js --- .../MID Server availability inside MID cluster.js | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js diff --git a/Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js b/Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js new file mode 100644 index 0000000000..c14bd1f1cc --- /dev/null +++ b/Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js @@ -0,0 +1,10 @@ +var flag = 0; //initial flag to 0 + var glideCluster = new GlideRecord('ecc_agent_cluster_member_m2m'); //m2m table stores cluser and all the midserver relation + glideCluster.addQuery('cluster', "sys_id of the cluster"); //replace "sys_id of the cluster" with sys_id of the MID server cluster + glideCluster.query(); + while(glideCluster.next()){ + if(glideCluster.agent.status=='Up'){ + outputs.flag = 1; //if any one MID server is up proceed next step in the integration + break; + } + //else returns 0 and no MID server are up inside the cluster, abort integration logic and report to the concerened team From bd82bd4e19998ea1bc6c9c18af3892f8fa3cee1e Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Sun, 8 Oct 2023 00:31:03 +0530 Subject: [PATCH 06/12] Create reame.md --- .../reame.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 Flow Actions/Check MID Servers status inside MID Server cluster/reame.md diff --git a/Flow Actions/Check MID Servers status inside MID Server cluster/reame.md b/Flow Actions/Check MID Servers status inside MID Server cluster/reame.md new file mode 100644 index 0000000000..1c0f688507 --- /dev/null +++ b/Flow Actions/Check MID Servers status inside MID Server cluster/reame.md @@ -0,0 +1,7 @@ +During integration set up with flow designers which involves MID servers , its better to check if MID server is up and running before we proceed with next steps in the integration. +when we are using MID Server cluster (where more than one MID server as a failover) its recommended to verify if atleast one MID server is up and establish the connect +MID server status inside cluster.js logic check if atleast one MID server is up if yes process next step in the integration if not abort the integration (we can have process to inform concered team) +example flow action : +where "inputs.midServerCluster.sys_id" is Cluster sys_id as input to the action +![image](https://github.com/gowdah/code-snippets/assets/42912180/59561199-3547-4ce2-a57e-d39ae65dbfcc) + From e6d6fd179fa2d17d25c7b051766f7b0cf6c51d3d Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Sun, 8 Oct 2023 00:34:50 +0530 Subject: [PATCH 07/12] Update MID Server availability inside MID cluster.js --- .../MID Server availability inside MID cluster.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js b/Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js index c14bd1f1cc..304b03aeb1 100644 --- a/Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js +++ b/Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js @@ -7,4 +7,4 @@ var flag = 0; //initial flag to 0 outputs.flag = 1; //if any one MID server is up proceed next step in the integration break; } - //else returns 0 and no MID server are up inside the cluster, abort integration logic and report to the concerened team + //else returns 0 and no MID server are up inside the cluster, abort integration logic and report to the concerened team. From 4c241247b6f4e457bfe64796d031524936fb89b1 Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Sun, 8 Oct 2023 00:44:18 +0530 Subject: [PATCH 08/12] Delete Flow Actions/Check MID Servers status inside MID Server cluster directory --- .../MID Server availability inside MID cluster.js | 10 ---------- .../reame.md | 7 ------- 2 files changed, 17 deletions(-) delete mode 100644 Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js delete mode 100644 Flow Actions/Check MID Servers status inside MID Server cluster/reame.md diff --git a/Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js b/Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js deleted file mode 100644 index 304b03aeb1..0000000000 --- a/Flow Actions/Check MID Servers status inside MID Server cluster/MID Server availability inside MID cluster.js +++ /dev/null @@ -1,10 +0,0 @@ -var flag = 0; //initial flag to 0 - var glideCluster = new GlideRecord('ecc_agent_cluster_member_m2m'); //m2m table stores cluser and all the midserver relation - glideCluster.addQuery('cluster', "sys_id of the cluster"); //replace "sys_id of the cluster" with sys_id of the MID server cluster - glideCluster.query(); - while(glideCluster.next()){ - if(glideCluster.agent.status=='Up'){ - outputs.flag = 1; //if any one MID server is up proceed next step in the integration - break; - } - //else returns 0 and no MID server are up inside the cluster, abort integration logic and report to the concerened team. diff --git a/Flow Actions/Check MID Servers status inside MID Server cluster/reame.md b/Flow Actions/Check MID Servers status inside MID Server cluster/reame.md deleted file mode 100644 index 1c0f688507..0000000000 --- a/Flow Actions/Check MID Servers status inside MID Server cluster/reame.md +++ /dev/null @@ -1,7 +0,0 @@ -During integration set up with flow designers which involves MID servers , its better to check if MID server is up and running before we proceed with next steps in the integration. -when we are using MID Server cluster (where more than one MID server as a failover) its recommended to verify if atleast one MID server is up and establish the connect -MID server status inside cluster.js logic check if atleast one MID server is up if yes process next step in the integration if not abort the integration (we can have process to inform concered team) -example flow action : -where "inputs.midServerCluster.sys_id" is Cluster sys_id as input to the action -![image](https://github.com/gowdah/code-snippets/assets/42912180/59561199-3547-4ce2-a57e-d39ae65dbfcc) - From 991faa6d9e63c97021118797ca77867eb902e077 Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Sun, 5 Oct 2025 12:37:14 +0530 Subject: [PATCH 09/12] Create BusinessRule.js --- .../Business Rules/BusinessRule.js | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 Server-Side Components/Business Rules/BusinessRule.js diff --git a/Server-Side Components/Business Rules/BusinessRule.js b/Server-Side Components/Business Rules/BusinessRule.js new file mode 100644 index 0000000000..c1bf98e00f --- /dev/null +++ b/Server-Side Components/Business Rules/BusinessRule.js @@ -0,0 +1,14 @@ +(function executeRule(current, previous /*null when async*/ ) { + /* + Fire this BR when a tag is removed/deleted from a record. + Retrieve the tag name, the user who removed the tag, and the tag removal date. + Update the above information onto the tag-referenced record in this example, In this example its incident record + */ + var updateRecord = new GlideRecord(current.table); + if (updateRecord.get(current.table_key)) { + var notes = "Tag Name:" + " " + current.label.getDisplayValue() + "\n" + "Tag Removed By:" + " " + current.sys_updated_by + "\n" + "Tag Removed On:" + " " + current.sys_updated_on; + //updateRecord.setValue("work_notes", notes); + updateRecord.work_notes = notes; + updateRecord.update(); + } +})(current, previous); From f9065467cf9671ba71617a82be18813f5c71e8b7 Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Sun, 5 Oct 2025 12:46:40 +0530 Subject: [PATCH 10/12] Delete Server-Side Components/Business Rules/BusinessRule.js --- .../Business Rules/BusinessRule.js | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 Server-Side Components/Business Rules/BusinessRule.js diff --git a/Server-Side Components/Business Rules/BusinessRule.js b/Server-Side Components/Business Rules/BusinessRule.js deleted file mode 100644 index c1bf98e00f..0000000000 --- a/Server-Side Components/Business Rules/BusinessRule.js +++ /dev/null @@ -1,14 +0,0 @@ -(function executeRule(current, previous /*null when async*/ ) { - /* - Fire this BR when a tag is removed/deleted from a record. - Retrieve the tag name, the user who removed the tag, and the tag removal date. - Update the above information onto the tag-referenced record in this example, In this example its incident record - */ - var updateRecord = new GlideRecord(current.table); - if (updateRecord.get(current.table_key)) { - var notes = "Tag Name:" + " " + current.label.getDisplayValue() + "\n" + "Tag Removed By:" + " " + current.sys_updated_by + "\n" + "Tag Removed On:" + " " + current.sys_updated_on; - //updateRecord.setValue("work_notes", notes); - updateRecord.work_notes = notes; - updateRecord.update(); - } -})(current, previous); From 43ef12f65caf0469e03e782ef788db3c37b94853 Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Sun, 5 Oct 2025 12:47:48 +0530 Subject: [PATCH 11/12] Create BusinessRule.js --- .../BusinessRule.js | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 Server-Side Components/Business Rules/Track Tag Removal Using Delete Business Rule/BusinessRule.js diff --git a/Server-Side Components/Business Rules/Track Tag Removal Using Delete Business Rule/BusinessRule.js b/Server-Side Components/Business Rules/Track Tag Removal Using Delete Business Rule/BusinessRule.js new file mode 100644 index 0000000000..c1bf98e00f --- /dev/null +++ b/Server-Side Components/Business Rules/Track Tag Removal Using Delete Business Rule/BusinessRule.js @@ -0,0 +1,14 @@ +(function executeRule(current, previous /*null when async*/ ) { + /* + Fire this BR when a tag is removed/deleted from a record. + Retrieve the tag name, the user who removed the tag, and the tag removal date. + Update the above information onto the tag-referenced record in this example, In this example its incident record + */ + var updateRecord = new GlideRecord(current.table); + if (updateRecord.get(current.table_key)) { + var notes = "Tag Name:" + " " + current.label.getDisplayValue() + "\n" + "Tag Removed By:" + " " + current.sys_updated_by + "\n" + "Tag Removed On:" + " " + current.sys_updated_on; + //updateRecord.setValue("work_notes", notes); + updateRecord.work_notes = notes; + updateRecord.update(); + } +})(current, previous); From 925176cce637886725985fe39b5cc7f2e6483471 Mon Sep 17 00:00:00 2001 From: gowdah <42912180+gowdah@users.noreply.github.com> Date: Sun, 5 Oct 2025 12:53:51 +0530 Subject: [PATCH 12/12] Create readme.md --- .../readme.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 Server-Side Components/Business Rules/Track Tag Removal Using Delete Business Rule/readme.md diff --git a/Server-Side Components/Business Rules/Track Tag Removal Using Delete Business Rule/readme.md b/Server-Side Components/Business Rules/Track Tag Removal Using Delete Business Rule/readme.md new file mode 100644 index 0000000000..e7e62a3022 --- /dev/null +++ b/Server-Side Components/Business Rules/Track Tag Removal Using Delete Business Rule/readme.md @@ -0,0 +1,17 @@ +**Configure the following business rule on the label_entry table:** + +1.Ensure the "Delete" operation is selected and the rule runs onBefore. + +2.Retrieve the table name where the tag is removed. + +3.Update the worknotes to track who removed the tag and when it was removed. +image +image + + +**Output:** + +image + +image +