Tag tracked objects

1. Tag tracked objects

Since of 2112 Figaf Tool supports tagging of tracked objects. This feature helps to find tracked objects easier. You can create, edit and delete tags.

Requirements:

  1. All required Agent Systems have been configured (see Agent Configuration to learn how to do that).

  2. Synchronization of all required Agent Systems has been done (see Synchronization with Agent system section).

To create a tag follow steps:

  1. Go to Tags page.

  2. Click on Create Tag button.

  3. Enter Name. Name must be unique.

  4. Enter Description. It’s not required.

  5. Save tag.

To attach tags to tracked objects follow steps:

  1. Configure required tags.

  2. Go to Change Tracking Tool → Tracked Objects page.

  3. Select objects for which you are going to add tags.

    If you select all objects, you can either attach tags to objects on all pages or to objects on current page.

  4. Click on Attach Tags button.

  5. Select tags in the dialog.

  6. Apply selection.

    It’s possible to attach tags to object from the tracked object page.

  7. Once it’s done, you can filter tracked objects by Tags column in order to find required objects easier.

    Once you attach object with tags to ticket, the same tags will be shown on the ticket page, so you will be able to filer tickets by Tags.

If you need to detach tags from tracked objects, do the same steps as during attaching tags to tracked objects but click on Detach Tags button.

2. Import tags

To import tags follow the steps:

  1. Go to Tags page.

  2. Click on Import Tags button.

  3. Configure setting for import:

    tags import dialog

    1. CSV Payload - csv file with source data. Data should have at least the following columns: column(s) with object name and column(s) with tags.

      PRO example
      PI object Tag1 Tag2

      TEST|TST|Interface|http://figaf.test.com/||

      Custom tag

      TEST|TST|dummy1|http://figaf.test.com||

      Custom tag

      One more tag

      TEST|TST|dummy2|http://figaf.test.com||

      Dummy tag1

      TEST|TST|dummy3|http://figaf.test.com||

      Dummy tag2

      One more tag
      PRO example with several columns for object name
      Sender Party Sender Component Interface Name Interface Namespace Receiver Party Receiver Service Tag1 Tag2 Tag3

      TEST

      TST

      Interface

      http://figaf.test.com/

      Custom tag

      Another tag1

      TEST

      TST

      dummy1

      http://figaf.test.com

      Custom tag

      One more tag

      TEST

      TST

      dummy2

      http://figaf.test.com

      Dummy tag1

      Another tag2

      TEST

      TST

      dummy3

      http://figaf.test.com

      Dummy tag2

      One more tag

      Another tag2
      CPI example
      Displayed Name Tag1 Tag2

      TestIflow_20251028

      Custom tag

      TestIFlow_20251103

      Custom tag

      One more tag

      TestIflow_3_20251028

      Dummy tag1

      TestIFlow_4_20251103

      Dummy tag2

      One more tag

    2. Object Name Mapping Rules for CSV Payload - csv file with mapping rules between objects in csvPayload and objects from the specified target system. CSV file with mappings shouldn’t have columns header, it should have 2 columns, data must be divided by semicolon. Left column is a object name substring, right column is a replacement string.

      Rules are checked in order of their occurrence in the file, and Figaf Tool checks all rules for each object name. It’s done intentionally to be able to configure mapping in a few steps. For example, let’s assume that it’s applying the rule SOURCE;TARGET for object |SOURCE|ZVXX_TMSEI_CUSTMAS.ZVXX_TMSEI_CUSTMAS01|urn:sap-com:document:sap:idoc:messages||, then object is mapped to |TARGET|ZVXX_TMSEI_CUSTMAS.ZVXX_TMSEI_CUSTMAS01|urn:sap-com:document:sap:idoc:messages||. If there is a rule TMSEI_CUSTMAS01;TMSEI_TEST_CUSTMAS01 after the rule SOURCE;TARGET then previously mapped object |TARGET|ZVXX_TMSEI_CUSTMAS.ZVXX_TMSEI_CUSTMAS01|urn:sap-com:document:sap:idoc:messages|| is mapped again to |TARGET|ZVXX_TMSEI_CUSTMAS.ZVXX_TMSEI_TEST_CUSTMAS01|urn:sap-com:document:sap:idoc:messages||.

    3. Has Header defines whether CSV Payload has headers or no.

    4. Overwrite Links - if true, all existing links between tags from request and tracked objects will be deleted and created from scratch. By default, links will be appended.

    5. Agent Platform is platform of the agent system.

    6. System Agent Id - system id of agent.

    7. Tag Name Column Names or Indexes defines an array of column names or indexes from CSV Payload file that is related to the tag names (determination by column name works only when csv has columns header and hasHeader is true).

      For example, for determination by column name: Tag1, Tag2, Tag3, for determination by column index: 6, 7, 8. Column indexes are started from 0.

    8. Integration Object Name Column Names or Indexes defines an array of column names or indexes. In case of PRO systems it’s a set of columns related to the name of ICO/SA/RA (Sender Party, Sender Component, Interface Name, Interface Namespace, Receiver Party, Receiver Service).

      For example, for determination by column names: Sender Party, Sender Component, Interface Name, Interface Namespace, Receiver Party, Receiver Service, for determination by column indexes: 0, 1, 2, 3, 4, 5. Column names must match 1 to 1 to the names in CSV file, otherwise there will be the error.

    9. only PRO Sender Channel Name Column Names Or Indexes defines a set of columns that relate to the name of the sender communication channel.

      For example, for determination by column names: Sender Party Id, Sender Component, Sender Channel.

    10. only PRO Receiver Channel Name Column Names Or Indexes defines a set of columns that relate to the name of the receiver communication channel.

      For example, for determination by column names: Receiver Party, Receiver Component, Receiver Channel.

  4. Once the settings are configured, click on Preview and browse tags that will be imported and linked with objects.

  5. Click on Import.

Then unexisting tags will be created and all tags mentioned in CSV Report will be attached to the related existing objects.