snow-flow 1.2.3 → 1.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,720 @@
1
+ #!/usr/bin/env node
2
+ "use strict";
3
+ /**
4
+ * Flow Examples - Demonstrates proper flow structure creation
5
+ * Shows how to use the flow structure builder for various common flow patterns
6
+ */
7
+ Object.defineProperty(exports, "__esModule", { value: true });
8
+ exports.createIncidentNotificationFlow = createIncidentNotificationFlow;
9
+ exports.createRequestApprovalFlow = createRequestApprovalFlow;
10
+ exports.createEquipmentProvisioningFlow = createEquipmentProvisioningFlow;
11
+ exports.convertLegacyFlowExample = convertLegacyFlowExample;
12
+ exports.createTestFlow = createTestFlow;
13
+ exports.demonstrateXMLGeneration = demonstrateXMLGeneration;
14
+ const flow_structure_builder_1 = require("./flow-structure-builder");
15
+ /**
16
+ * Example 1: Incident Notification Flow
17
+ * Triggers when high-priority incidents are created
18
+ */
19
+ function createIncidentNotificationFlow() {
20
+ const flowDef = {
21
+ name: 'High Priority Incident Notification',
22
+ description: 'Automatically notify management when high-priority incidents are created',
23
+ table: 'incident',
24
+ trigger: {
25
+ type: 'record_created',
26
+ table: 'incident',
27
+ condition: 'priority<=2' // High or Critical priority
28
+ },
29
+ activities: [
30
+ {
31
+ id: 'check_priority',
32
+ name: 'Verify Priority Level',
33
+ type: 'condition',
34
+ inputs: {
35
+ condition: '${record.priority} <= 2',
36
+ field_to_check: 'priority',
37
+ operator: 'less_than_or_equal',
38
+ value: '2'
39
+ },
40
+ outputs: {
41
+ condition_result: 'boolean'
42
+ }
43
+ },
44
+ {
45
+ id: 'send_management_alert',
46
+ name: 'Send Management Alert',
47
+ type: 'notification',
48
+ condition: '${check_priority.condition_result} == true',
49
+ inputs: {
50
+ recipient: 'it-management@company.com',
51
+ subject: 'URGENT: High Priority Incident Created',
52
+ message: `High priority incident has been created:
53
+
54
+ Incident: \${record.number}
55
+ Priority: \${record.priority}
56
+ Description: \${record.short_description}
57
+ Assigned to: \${record.assigned_to}
58
+
59
+ Please review immediately.`
60
+ },
61
+ outputs: {
62
+ notification_sent: 'boolean',
63
+ notification_id: 'string'
64
+ }
65
+ },
66
+ {
67
+ id: 'log_notification',
68
+ name: 'Log Notification Action',
69
+ type: 'script',
70
+ inputs: {
71
+ script: `
72
+ gs.info('High priority incident notification sent for ' + current.number, 'IncidentFlow');
73
+ current.work_notes = 'Management notification sent at ' + new GlideDateTime();
74
+ current.u_management_notified = true;
75
+ current.update();
76
+ `.trim()
77
+ },
78
+ outputs: {
79
+ log_result: 'string'
80
+ }
81
+ }
82
+ ],
83
+ variables: [
84
+ {
85
+ id: 'incident_priority',
86
+ name: 'Incident Priority',
87
+ type: 'integer',
88
+ input: true,
89
+ output: false,
90
+ default_value: '3'
91
+ },
92
+ {
93
+ id: 'notification_status',
94
+ name: 'Notification Status',
95
+ type: 'string',
96
+ input: false,
97
+ output: true,
98
+ default_value: 'pending'
99
+ }
100
+ ],
101
+ connections: [],
102
+ error_handling: []
103
+ };
104
+ return (0, flow_structure_builder_1.generateFlowComponents)(flowDef);
105
+ }
106
+ /**
107
+ * Example 2: Request Approval Flow
108
+ * Handles service catalog request approvals with multiple approvers
109
+ */
110
+ function createRequestApprovalFlow() {
111
+ const flowDef = {
112
+ name: 'Service Request Approval Process',
113
+ description: 'Multi-stage approval process for service catalog requests',
114
+ table: 'sc_request',
115
+ trigger: {
116
+ type: 'record_created',
117
+ table: 'sc_request',
118
+ condition: 'approval=requested'
119
+ },
120
+ activities: [
121
+ {
122
+ id: 'validate_request',
123
+ name: 'Validate Request Details',
124
+ type: 'script',
125
+ inputs: {
126
+ script: `
127
+ var validation = {
128
+ valid: true,
129
+ errors: [],
130
+ warnings: []
131
+ };
132
+
133
+ // Check required fields
134
+ if (!current.requested_for) {
135
+ validation.errors.push('Requested for field is required');
136
+ validation.valid = false;
137
+ }
138
+
139
+ if (!current.short_description) {
140
+ validation.errors.push('Short description is required');
141
+ validation.valid = false;
142
+ }
143
+
144
+ // Check business rules
145
+ if (current.u_cost && parseFloat(current.u_cost) > 10000) {
146
+ validation.warnings.push('High cost request requires additional approval');
147
+ }
148
+
149
+ gs.info('Request validation completed: ' + JSON.stringify(validation), 'ApprovalFlow');
150
+ return validation;
151
+ `.trim()
152
+ },
153
+ outputs: {
154
+ validation_result: 'object',
155
+ is_valid: 'boolean'
156
+ }
157
+ },
158
+ {
159
+ id: 'manager_approval',
160
+ name: 'Manager Approval',
161
+ type: 'approval',
162
+ condition: '${validate_request.is_valid} == true',
163
+ inputs: {
164
+ approver: '${record.requested_for.manager}',
165
+ message: 'Please review and approve this service request:\n\nRequest: ${record.number}\nDescription: ${record.short_description}\nRequested by: ${record.requested_for}\nEstimated cost: ${record.u_cost}',
166
+ due_date: '+3 days',
167
+ approval_type: 'manager'
168
+ },
169
+ outputs: {
170
+ approval_result: 'string',
171
+ approved_by: 'string',
172
+ approval_comments: 'string'
173
+ }
174
+ },
175
+ {
176
+ id: 'finance_approval',
177
+ name: 'Finance Approval (High Cost)',
178
+ type: 'approval',
179
+ condition: '${manager_approval.approval_result} == "approved" && ${record.u_cost} > 5000',
180
+ inputs: {
181
+ approver: 'finance.team',
182
+ message: 'High-cost request requires finance approval:\n\nRequest: ${record.number}\nDescription: ${record.short_description}\nCost: ${record.u_cost}\nManager approved by: ${manager_approval.approved_by}',
183
+ due_date: '+2 days',
184
+ approval_type: 'finance'
185
+ },
186
+ outputs: {
187
+ finance_approval_result: 'string',
188
+ finance_approved_by: 'string',
189
+ finance_comments: 'string'
190
+ }
191
+ },
192
+ {
193
+ id: 'create_fulfillment_task',
194
+ name: 'Create Fulfillment Task',
195
+ type: 'create_record',
196
+ condition: '${manager_approval.approval_result} == "approved"',
197
+ inputs: {
198
+ table: 'sc_task',
199
+ fields: {
200
+ request: '${record.sys_id}',
201
+ short_description: 'Fulfill: ${record.short_description}',
202
+ description: '${record.description}',
203
+ assigned_to: 'fulfillment.team',
204
+ state: '1', // Open
205
+ priority: '${record.priority}',
206
+ due_date: '+5 days'
207
+ }
208
+ },
209
+ outputs: {
210
+ task_sys_id: 'string',
211
+ task_number: 'string'
212
+ }
213
+ },
214
+ {
215
+ id: 'notify_requester',
216
+ name: 'Notify Requester of Status',
217
+ type: 'notification',
218
+ inputs: {
219
+ recipient: '${record.requested_for}',
220
+ subject: 'Service Request Update - ${record.number}',
221
+ message: `Your service request has been processed:
222
+
223
+ Request Number: \${record.number}
224
+ Status: \${manager_approval.approval_result == "approved" ? "Approved and assigned for fulfillment" : "Pending approval"}
225
+ ${manager_approval.approval_result == "approved" ? "Fulfillment Task: " + create_fulfillment_task.task_number : ""}
226
+
227
+ You will receive another notification when work begins.`
228
+ },
229
+ outputs: {
230
+ notification_sent: 'boolean'
231
+ }
232
+ }
233
+ ],
234
+ variables: [
235
+ {
236
+ id: 'request_cost',
237
+ name: 'Request Cost',
238
+ type: 'decimal',
239
+ input: true,
240
+ output: false,
241
+ default_value: '0.00'
242
+ },
243
+ {
244
+ id: 'approval_chain',
245
+ name: 'Approval Chain Status',
246
+ type: 'string',
247
+ input: false,
248
+ output: true,
249
+ default_value: 'pending'
250
+ },
251
+ {
252
+ id: 'fulfillment_task_id',
253
+ name: 'Fulfillment Task ID',
254
+ type: 'string',
255
+ input: false,
256
+ output: true,
257
+ default_value: ''
258
+ }
259
+ ],
260
+ connections: [],
261
+ error_handling: [
262
+ {
263
+ id: 'approval_timeout_handler',
264
+ name: 'Handle Approval Timeout',
265
+ trigger: 'on_timeout',
266
+ action: 'escalate',
267
+ parameters: {
268
+ escalation_target: 'department.manager',
269
+ timeout_message: 'Approval request has timed out and requires attention'
270
+ }
271
+ }
272
+ ]
273
+ };
274
+ return (0, flow_structure_builder_1.generateFlowComponents)(flowDef);
275
+ }
276
+ /**
277
+ * Example 3: Equipment Provisioning Flow
278
+ * Complex flow with multiple integrations and conditional logic
279
+ */
280
+ function createEquipmentProvisioningFlow() {
281
+ const flowDef = {
282
+ name: 'IT Equipment Provisioning',
283
+ description: 'Automated provisioning of IT equipment including ordering, configuration, and delivery',
284
+ table: 'sc_request',
285
+ trigger: {
286
+ type: 'record_updated',
287
+ table: 'sc_request',
288
+ condition: 'cat_item.name=iPhone 15 Pro^approval=approved'
289
+ },
290
+ activities: [
291
+ {
292
+ id: 'extract_requirements',
293
+ name: 'Extract Equipment Requirements',
294
+ type: 'script',
295
+ inputs: {
296
+ script: `
297
+ // Extract equipment details from catalog item variables
298
+ var requirements = {
299
+ device_type: '',
300
+ model: '',
301
+ color: '',
302
+ storage: '',
303
+ carrier: '',
304
+ accessories: [],
305
+ delivery_location: '',
306
+ user_profile: {}
307
+ };
308
+
309
+ // Get catalog item variables
310
+ var variables = current.variables;
311
+ if (variables) {
312
+ var varsObj = JSON.parse(variables);
313
+ requirements.device_type = varsObj.device_type || 'iPhone';
314
+ requirements.model = varsObj.model || '15 Pro';
315
+ requirements.color = varsObj.color || 'Natural Titanium';
316
+ requirements.storage = varsObj.storage || '256GB';
317
+ requirements.carrier = varsObj.carrier || 'Verizon';
318
+ requirements.accessories = varsObj.accessories || [];
319
+ requirements.delivery_location = varsObj.delivery_location || current.requested_for.location;
320
+ }
321
+
322
+ // Get user profile information
323
+ requirements.user_profile = {
324
+ sys_id: current.requested_for.sys_id,
325
+ name: current.requested_for.name,
326
+ email: current.requested_for.email,
327
+ department: current.requested_for.department,
328
+ manager: current.requested_for.manager,
329
+ location: current.requested_for.location
330
+ };
331
+
332
+ gs.info('Equipment requirements extracted: ' + JSON.stringify(requirements), 'ProvisioningFlow');
333
+ return requirements;
334
+ `.trim()
335
+ },
336
+ outputs: {
337
+ requirements: 'object',
338
+ device_details: 'object',
339
+ user_info: 'object'
340
+ }
341
+ },
342
+ {
343
+ id: 'check_inventory',
344
+ name: 'Check Equipment Inventory',
345
+ type: 'rest_step',
346
+ inputs: {
347
+ endpoint: 'https://inventory-api.company.com/check',
348
+ method: 'POST',
349
+ headers: {
350
+ 'Content-Type': 'application/json',
351
+ 'Authorization': 'Bearer ${sys_properties.inventory_api_token}'
352
+ },
353
+ body: {
354
+ device_type: '${extract_requirements.device_details.device_type}',
355
+ model: '${extract_requirements.device_details.model}',
356
+ storage: '${extract_requirements.device_details.storage}',
357
+ color: '${extract_requirements.device_details.color}'
358
+ }
359
+ },
360
+ outputs: {
361
+ in_stock: 'boolean',
362
+ available_quantity: 'integer',
363
+ estimated_delivery: 'string',
364
+ supplier_info: 'object'
365
+ }
366
+ },
367
+ {
368
+ id: 'order_equipment',
369
+ name: 'Order Equipment from Supplier',
370
+ type: 'rest_step',
371
+ condition: '${check_inventory.in_stock} == false',
372
+ inputs: {
373
+ endpoint: 'https://supplier-api.company.com/order',
374
+ method: 'POST',
375
+ headers: {
376
+ 'Content-Type': 'application/json',
377
+ 'Authorization': 'Bearer ${sys_properties.supplier_api_token}'
378
+ },
379
+ body: {
380
+ item_details: '${extract_requirements.requirements}',
381
+ delivery_address: '${extract_requirements.user_info.location}',
382
+ priority: 'standard',
383
+ purchase_order: '${record.number}',
384
+ cost_center: '${extract_requirements.user_info.department.cost_center}'
385
+ }
386
+ },
387
+ outputs: {
388
+ order_id: 'string',
389
+ order_status: 'string',
390
+ tracking_number: 'string',
391
+ estimated_delivery_date: 'string'
392
+ }
393
+ },
394
+ {
395
+ id: 'allocate_from_inventory',
396
+ name: 'Allocate from Existing Inventory',
397
+ type: 'rest_step',
398
+ condition: '${check_inventory.in_stock} == true',
399
+ inputs: {
400
+ endpoint: 'https://inventory-api.company.com/allocate',
401
+ method: 'POST',
402
+ headers: {
403
+ 'Content-Type': 'application/json',
404
+ 'Authorization': 'Bearer ${sys_properties.inventory_api_token}'
405
+ },
406
+ body: {
407
+ item_details: '${extract_requirements.requirements}',
408
+ allocated_to: '${extract_requirements.user_info.sys_id}',
409
+ request_number: '${record.number}',
410
+ allocation_type: 'permanent'
411
+ }
412
+ },
413
+ outputs: {
414
+ allocation_id: 'string',
415
+ serial_number: 'string',
416
+ asset_tag: 'string'
417
+ }
418
+ },
419
+ {
420
+ id: 'create_asset_record',
421
+ name: 'Create Asset Record in CMDB',
422
+ type: 'create_record',
423
+ inputs: {
424
+ table: 'alm_asset',
425
+ fields: {
426
+ display_name: '${extract_requirements.device_details.device_type} - ${extract_requirements.user_info.name}',
427
+ model: '${extract_requirements.device_details.model}',
428
+ serial_number: '${allocate_from_inventory.serial_number || "TBD"}',
429
+ asset_tag: '${allocate_from_inventory.asset_tag || "TBD"}',
430
+ assigned_to: '${extract_requirements.user_info.sys_id}',
431
+ location: '${extract_requirements.user_info.location}',
432
+ state: '2', // In use
433
+ cost_center: '${extract_requirements.user_info.department.cost_center}',
434
+ purchase_date: '${gs.nowDateTime()}',
435
+ po_number: '${record.number}',
436
+ ci_class: 'mobile_device'
437
+ }
438
+ },
439
+ outputs: {
440
+ asset_sys_id: 'string',
441
+ asset_number: 'string'
442
+ }
443
+ },
444
+ {
445
+ id: 'setup_mobile_profile',
446
+ name: 'Configure Mobile Device Profile',
447
+ type: 'rest_step',
448
+ inputs: {
449
+ endpoint: 'https://mdm.company.com/api/profile/create',
450
+ method: 'POST',
451
+ headers: {
452
+ 'Content-Type': 'application/json',
453
+ 'Authorization': 'Bearer ${sys_properties.mdm_api_token}'
454
+ },
455
+ body: {
456
+ user_id: '${extract_requirements.user_info.email}',
457
+ device_type: '${extract_requirements.device_details.device_type}',
458
+ department: '${extract_requirements.user_info.department}',
459
+ security_profile: 'corporate_standard',
460
+ apps: [
461
+ 'Microsoft Outlook',
462
+ 'Microsoft Teams',
463
+ 'Company Portal',
464
+ 'VPN Client'
465
+ ],
466
+ restrictions: {
467
+ app_store: true,
468
+ camera: false,
469
+ location_services: true
470
+ }
471
+ }
472
+ },
473
+ outputs: {
474
+ mdm_profile_id: 'string',
475
+ enrollment_token: 'string',
476
+ profile_status: 'string'
477
+ }
478
+ },
479
+ {
480
+ id: 'send_delivery_notification',
481
+ name: 'Send Delivery Instructions',
482
+ type: 'notification',
483
+ inputs: {
484
+ recipient: '${extract_requirements.user_info.email}',
485
+ cc: '${extract_requirements.user_info.manager.email}',
486
+ subject: 'iPhone Provisioning Update - ${record.number}',
487
+ message: `Your iPhone request has been processed and is ready for delivery/pickup:
488
+
489
+ Device Details:
490
+ - Model: \${extract_requirements.device_details.model}
491
+ - Storage: \${extract_requirements.device_details.storage}
492
+ - Color: \${extract_requirements.device_details.color}
493
+
494
+ ${check_inventory.in_stock ?
495
+ "✅ Device allocated from inventory\\nSerial Number: " + allocate_from_inventory.serial_number + "\\nAsset Tag: " + allocate_from_inventory.asset_tag :
496
+ "📦 Device ordered from supplier\\nOrder ID: " + order_equipment.order_id + "\\nEstimated Delivery: " + order_equipment.estimated_delivery_date}
497
+
498
+ Next Steps:
499
+ 1. You will receive device setup instructions via email
500
+ 2. Your manager has been notified of the allocation
501
+ 3. Please report any issues to IT Support
502
+
503
+ Asset Record: \${create_asset_record.asset_number}
504
+ MDM Profile: \${setup_mobile_profile.mdm_profile_id}
505
+
506
+ IT Support Team`
507
+ },
508
+ outputs: {
509
+ notification_sent: 'boolean',
510
+ notification_id: 'string'
511
+ }
512
+ }
513
+ ],
514
+ variables: [
515
+ {
516
+ id: 'device_specifications',
517
+ name: 'Device Specifications',
518
+ type: 'object',
519
+ input: true,
520
+ output: false,
521
+ default_value: '{}'
522
+ },
523
+ {
524
+ id: 'provisioning_status',
525
+ name: 'Provisioning Status',
526
+ type: 'string',
527
+ input: false,
528
+ output: true,
529
+ default_value: 'pending'
530
+ },
531
+ {
532
+ id: 'asset_information',
533
+ name: 'Asset Information',
534
+ type: 'object',
535
+ input: false,
536
+ output: true,
537
+ default_value: '{}'
538
+ }
539
+ ],
540
+ connections: [],
541
+ error_handling: [
542
+ {
543
+ id: 'inventory_api_error',
544
+ name: 'Handle Inventory API Errors',
545
+ trigger: 'on_api_error',
546
+ action: 'retry_with_fallback',
547
+ parameters: {
548
+ max_retries: 3,
549
+ fallback_action: 'manual_procurement',
550
+ notification_recipient: 'it.procurement@company.com'
551
+ }
552
+ },
553
+ {
554
+ id: 'mdm_setup_failure',
555
+ name: 'Handle MDM Setup Failures',
556
+ trigger: 'on_error',
557
+ action: 'create_manual_task',
558
+ parameters: {
559
+ task_assignment_group: 'mobile_device_management',
560
+ task_description: 'Manual MDM profile setup required for ${extract_requirements.user_info.name}'
561
+ }
562
+ }
563
+ ]
564
+ };
565
+ return (0, flow_structure_builder_1.generateFlowComponents)(flowDef);
566
+ }
567
+ /**
568
+ * Example 4: Converting Legacy Flow Format
569
+ * Shows how to convert existing flow definitions to the new structure
570
+ */
571
+ function convertLegacyFlowExample() {
572
+ // Example of legacy flow format that might exist in the system
573
+ const legacyFlow = {
574
+ name: 'Legacy Password Reset Flow',
575
+ description: 'Old format password reset workflow',
576
+ trigger_type: 'manual',
577
+ table: 'sys_user',
578
+ condition: '',
579
+ actions: [
580
+ {
581
+ name: 'Verify User Identity',
582
+ type: 'script',
583
+ config: {
584
+ script: 'var verified = verifyUserIdentity(current); return verified;'
585
+ }
586
+ },
587
+ {
588
+ name: 'Reset Password',
589
+ type: 'script',
590
+ config: {
591
+ script: 'if (verified) { resetUserPassword(current); }'
592
+ }
593
+ },
594
+ {
595
+ name: 'Send Confirmation Email',
596
+ type: 'email',
597
+ config: {
598
+ to: '${current.email}',
599
+ subject: 'Password Reset Confirmation',
600
+ body: 'Your password has been reset successfully.'
601
+ }
602
+ }
603
+ ],
604
+ inputs: [
605
+ {
606
+ name: 'user_id',
607
+ type: 'string',
608
+ description: 'User sys_id for password reset'
609
+ }
610
+ ],
611
+ outputs: [
612
+ {
613
+ name: 'reset_successful',
614
+ type: 'boolean',
615
+ description: 'Whether password reset was successful'
616
+ }
617
+ ]
618
+ };
619
+ // Convert to modern format
620
+ const modernFlow = (0, flow_structure_builder_1.convertToFlowDefinition)(legacyFlow);
621
+ // Generate components
622
+ return (0, flow_structure_builder_1.generateFlowComponents)(modernFlow);
623
+ }
624
+ /**
625
+ * Example 5: Testing Flow Structure
626
+ * Demonstrates how to create test flows for validation
627
+ */
628
+ function createTestFlow(name = 'Integration Test Flow') {
629
+ const testFlow = {
630
+ name,
631
+ description: `Test flow for validation: ${name}`,
632
+ table: 'incident',
633
+ trigger: {
634
+ type: 'manual',
635
+ table: 'incident',
636
+ condition: ''
637
+ },
638
+ activities: [
639
+ {
640
+ id: 'test_log',
641
+ name: 'Test Log Action',
642
+ type: 'script',
643
+ inputs: {
644
+ script: `gs.info('Test flow "${name}" executed at ' + new GlideDateTime(), 'TestFlow');`
645
+ },
646
+ outputs: {
647
+ execution_time: 'string'
648
+ }
649
+ }
650
+ ],
651
+ variables: [
652
+ {
653
+ id: 'test_parameter',
654
+ name: 'Test Parameter',
655
+ type: 'string',
656
+ input: true,
657
+ output: false,
658
+ default_value: 'test_value'
659
+ }
660
+ ],
661
+ connections: [],
662
+ error_handling: []
663
+ };
664
+ return (0, flow_structure_builder_1.generateFlowComponents)(testFlow);
665
+ }
666
+ /**
667
+ * Utility to demonstrate XML generation
668
+ */
669
+ function demonstrateXMLGeneration() {
670
+ const components = createIncidentNotificationFlow();
671
+ // This would generate the full Update Set XML
672
+ // In a real scenario, you'd import this XML into ServiceNow
673
+ return `
674
+ <!-- Example XML structure (truncated for brevity) -->
675
+ <?xml version="1.0" encoding="UTF-8"?>
676
+ <unload unload_date="${new Date().toISOString()}">
677
+ <sys_hub_flow action="INSERT_OR_UPDATE">
678
+ <sys_id>${components.flowRecord.sys_id}</sys_id>
679
+ <name>${components.flowRecord.name}</name>
680
+ <description>${components.flowRecord.description}</description>
681
+ <active>true</active>
682
+ <type>flow</type>
683
+ <!-- ... more fields ... -->
684
+ </sys_hub_flow>
685
+
686
+ <sys_hub_trigger_instance action="INSERT_OR_UPDATE">
687
+ <sys_id>${components.triggerInstance.sys_id}</sys_id>
688
+ <flow>${components.flowRecord.sys_id}</flow>
689
+ <type>${components.triggerInstance.type}</type>
690
+ <!-- ... more fields ... -->
691
+ </sys_hub_trigger_instance>
692
+
693
+ ${components.actionInstances.map(action => `
694
+ <sys_hub_action_instance action="INSERT_OR_UPDATE">
695
+ <sys_id>${action.sys_id}</sys_id>
696
+ <flow>${action.flow}</flow>
697
+ <name>${action.name}</name>
698
+ <action_type>${action.action_type}</action_type>
699
+ <!-- ... more fields ... -->
700
+ </sys_hub_action_instance>`).join('')}
701
+
702
+ ${components.logicChain.map(logic => `
703
+ <sys_hub_flow_logic action="INSERT_OR_UPDATE">
704
+ <sys_id>${logic.sys_id}</sys_id>
705
+ <flow>${logic.flow}</flow>
706
+ <from_element>${logic.from_element}</from_element>
707
+ <to_element>${logic.to_element}</to_element>
708
+ <!-- ... more fields ... -->
709
+ </sys_hub_flow_logic>`).join('')}
710
+ </unload>
711
+ `.trim();
712
+ }
713
+ exports.default = {
714
+ createIncidentNotificationFlow,
715
+ createRequestApprovalFlow,
716
+ createEquipmentProvisioningFlow,
717
+ convertLegacyFlowExample,
718
+ createTestFlow,
719
+ demonstrateXMLGeneration
720
+ };