0:06 Welcome to this Application Explainer video, part of our Data Adapters topic range.
0:10 In this video we will cover the subject of Processing Adapters within SLM.
0:15 Processing adapters are components using software applications to facilitate the transformation of data in a bulk manner.
0:23 SLM contains the following processing adapters, renaming objects and unlinking objects.
0:30 The following information will be covered in this training.
0:33 Chapter 1 will be the renaming objects adapter and Chapter 2 will be unlinking objects adapter.
0:43 In chapter 1 we’ll be covering using the renamed objects adapter to change object ID’s in a bulk manner.
0:50 Users only need 4 pieces of data for this, the scope, the type ID, the object ID, and the new object ID.
0:59 In the event where a user would like to rename an object, or in other words change the ID of an object or several objects in the system, the rename object’s adapter can be used.
1:09 These adapters receive a CSV file as an input.
1:13 Let’s take a look at the format of this file.
1:17 The file receives the scope of the object, the type ID of the object, the current object ID, and the new object’s ID.
1:24 Let’s go over an example.
1:30 Let’s say we’d like to rename this interlock and this SIF.
1:35 Let’s get the information for the interlock.
1:41 We get the scope type ID, the current object ID and the new object ID.
2:00 Now let’s get the information for the SIF, the scope type ID, current object ID and the new object ID.
2:23 Let’s save the file and let’s go back to the adapters module.
2:38 Let’s select the input file and now we queue the task.
2:46 We can keep track of the task progress and the processing adapter tasks.
2:54 As we can see, the task has finished.
2:57 Now we can go ahead and verify that the name of the objects has changed.
3:02 The interlock has been renamed and the SIF has also been renamed.
3:09 In Chapter 2, we’ll be covering using the Unlinked Objects Adapter to disassociate objects from their parents in a bulk manner.
3:18 When a user wishes to unlink an object in a bulk manner, the Unlinked Object Adapter is employed to perform this task.
3:26 This adapter receives a CSV file as an input.
3:30 Let’s take a look at the format of this file, the information required child type ID, the child object ID, the parent type ID, the parent object ID, and the scope.
3:45 The scope will be the object ID of the site where those objects are found.
3:50 Let’s go over a couple of scenarios.
3:57 Here we can see the interlock 10 I 001 and the SIF 10 SIF 003.
4:04 These two objects are linked to two different units, the 10 crude unit and the 42 hydro cracker unit.
4:13 In this scenario, we’d like to unlink the interlock and the SIF from the 42 hydro cracker unit.
4:21 Let’s start gathering that information.
4:27 We need a type ID.
4:30 In this scenario.
4:31 The child type ID is interlock.
4:36 We need the object ID.
4:43 We need the parent information from where we are unlinking the interlock.
4:49 In this scenario, it’s the unit, the object ID of the unit, and the scope of the unit.
5:04 Now let’s gather information for the SIF type ID, object ID, and we know that we’re unlinking this SIF from the same unit, the 42 Hydra cracker, which is under the same scope.
5:28 Let’s save this file.
5:32 Let’s get back to the adapters module.
5:40 Let’s input the file and let’s queue the task.
5:46 We can keep track of the task progress in the processing adapter tasks.
5:54 As we can see, the process has finished.
5:56 Now let’s go back and check that the object has been unlinked.
6:01 We can see that the interlock 10 I 001 is no longer linked to the Fortitude Hydra cracker unit and this SIF 10 SIF 003 is no longer linked to the 42 Hydro cracker unit as well.
