Ticket page

Ticket page shows the ticket details and provides functionality for ticket management. It looks:

ticket details

There are the following tabs on this page:

On each tab you are able to:

  1. Open another ticket details clicking on open another button and selecting a ticket.

  2. View linked release details clicking on <Release Title>. It opens release page.

  3. Move the ticket to next or previous stages depending on its type:

    1. Development is used with development within one landscape.

    2. Migration is used when it is needed to migrate objects from one landscape to another.

Development and Migration ticket types provide similar workflow with small differences:

  • Development tickets have the following statuses:

    • In development is the stage when objects are attached, updated, detached from the ticket.

    • In transport is the stage when development part is done, operations available on In development stage are blocked, objects are prepared for transport through the landscape. If the landscape has Integrated transport management, transports with objects attached to the ticket will be created automatically. Otherwise, if Integrated transport management is false, user needs to attach transports to the ticket. Ticket can be resolved only if all related active transports are imported (see Transport Statuses for details).

    • Completed is the stage when transport stage is successfully completed, the ticket is marked as Completed. It means that all objects are available and operational on all systems in the landscape.

    • Canceled is finish stage if ticket can’t be resolved due to any reason.

      The picture below shows development ticket status transitions:

      development ticket diagram

  • Migration tickets have the following statuses:

    • Prepared is the stage similar to In development.

    • In development is the same as for development ticket, but for migration ticket we assume that changes will not be done with source objects because the main goal for migration is to migrate objects between landscapes, it is not about their changes in the old landscape.

    • In transport is the same as for development ticket.

    • Migrated is the stage when transport stage is successfully completed, the ticket is marked as Migrated. It means that all objects are available and operational on all systems in the landscape. It is possible to process development ticket creation and transport configuration copying on that stage.

    • Canceled is finish stage if ticket can’t be resolved due to any reason.

      The picture below shows migration ticket status transitions:

      migration ticket diagram

  1. Ticket Details tab provides ticket details updating. See almost all ticket properties here. Additional properties:

    1. Depends on tickets

    2. Dependent tickets

      Landscape (for development ticket), Source Landscape, Target Landscape, and Migration Landscape (for migration ticket) can’t be modified.

  2. Tracked Objects tab provides functionality for attached tracked object management:

    ticket tracked objects

    Here you can:

    1. Attach Tracked Objects clicking on Attach Tracked Objects button. It opens 'Attach tracked objects to ticket' dialog box with predefined Agent: for development ticket - the first item from target landscape, for migration ticket - the first item from migration landscape. So it is possible to manually attach only development objects.

      Attaching objects should be licensed for DevOps or Migration (see Configure Object Licenses for details).

      All object versions in the table are the latest.

      If the object has been already selected, it is not visible in the table, but you can see the count of such objects.

      Previous object version becomes detached.

    2. Update selected object(s) to the latest version clicking on Update to the latest version. It attaches the latest version of chosen object(s) to the ticket (versions are looked up in CTT).

    3. Attach all dependent objects of selected object(s) clicking on Attach all dependent objects. It attaches the latest versions of all child dependencies of chosen object(s) recursively.

      For channels, it gets a parent link to component/system and then again parent link to the party.

    4. Detach selected Tracked Objects clicking on Detach Tracked Objects. It marks chosen object versions in the ticket as detached (versions are still visible in the table) if Detach Only option is selected. It deletes chosen object versions from the ticket if Delete Links option is selected.

    5. Compare versions of two selected objects clicking on Compare Versions. It opens 'Tracked Object Differences' dialog box with two selected object versions.

      These objects must have the same type in the change tracking.

      BPMN model and Simplified model can be compared for integration flows.

    6. Start synchronization on chosen Agent clicking on Synchronize (read about synchronization here).

      It is possible to select Agents which are used in related landscape(s).

    7. View tracked object details clicking on its Name. It opens 'Name page' with tracked object details.

  3. Test Cases tab provides functionality for test case management and looks:

    ticket test cases

    Here you can:

    1. Add/remove recommended test cases clicking on Lookup related Test Cases. It opens 'Assign Test Cases To Ticket' dialog box, where you can select test cases recommended for adding or removal:

      assign test cases to ticket

      Test cases recommended for adding are test cases related to the attached ICOs, Sender Agreements, CPI Iflows, B2B Scenarios tracked objects.

      Test cases recommended for removal are previously added test cases related to the detached from the ticket ICOs, Sender Agreements, CPI Iflows, B2B Scenarios tracked objects.

    2. Open related test suite clicking on Open Test Suite. It opens Test Suite page.

    3. Detach selected test cases clicking on Detach from Ticket. It triggers test case detaching operation from test suite.

    4. Run the related test suite clicking on run or run on buttons:

      • Run uses static links to test objects defined in the test case.

      • Run on resolves these links dynamically at the moment of test run. It is possible to see how these links are resolved through Current Mapping Configuration button - it opens 'Mapping Configuration' dialog box:

        mapping configuration

        There are Agent Objects (parent nodes) and Test Objects (child nodes) in opened dialog box.

Test cases aren’t run on deleted test objects. Such objects are skipped and listed in a warning message box (Test cases will not be run on the following test objects because these objects are deleted: …​), while the other test objects and test cases of the run are processed. A test suite in which no test case has a runnable test object isn’t run at all, and no test suite run is created.

+

You can’t run test suite without linked test cases.

  1. Last Testing Result tab shows results of last running. On this page you can:

    1. View Agent and Test Objects clicking on Agent Object Title or Test Object Title. It opens Integration Object Details page.

    2. Poll remote results clicking on Poll remote results.

      Since Figaf Tool 2.15 automatic polling is added for SAP CPI Agents. Once the messages have been run successfully, automatic polling is started.

      Since Figaf Tool 2.15.2 active polling statistics can be viewed. If there is polling in progress for the integration objects and you open another poll remote data dialog, then

      • recordings/test runs which are in both polling requests will be marked as SKIPPED_AS_DUPLICATE and statistics will be copied from original item and shown on UI in the new one.

      • recordings/test runs which are not in the original polling request will be SKIPPED in the new one.

      Since Figaf Tool 2305 polling will not be started if there is already a started polling requests with same objects in progress or polling has been already completed for all selected objects.

      If you have polled almost all messages and you just need to poll small number of messages to finish testing, you can enable option Ignore messages cache during polling on Application configuration page. When this option is enabled, already polled messages won’t be skipped. It affects performance when the amount of messages is large and you just need to poll small number to finish testing.

    3. View last polling result clicking on Open Last Polling Result.

      Open Last Polling Result button is available after polling remote data and until page is refreshed.

    4. Export as a test case to PIT (only for PRO) clicking on Export as a Test Case to PIT.

      Export as a Test Case to PIT is available only for licensed version after the test suite running.

    5. Compare testing results and build reports clicking on check button.

      The option reprocesses comparison and report generation asynchronously. It makes sense to execute the option once you have configured a new "ignore rule".

    6. Do the following actions clicking on menu and choosing corresponding option:

      1. Rerun reruns required test case.

      2. View testcase opens 'Test Case Details' page.

      3. Download report.

        Report type can be one of 2 types:

        1. xlsx report:

          • Contains information about test run/test suite run results.

          • By default only failed results are added to xlsx report. If you want to change this behavior, go to Configuration → Application page and enable Show successful messages in the test suite’s report property.

        2. zip archive with 3 csv reports:

          • test-run-metadata.csv - contains common information about test run/test suite run (e.g. test object, counters for success/error/unexpected/not/compared/unfinished test run/test suite run results).

          • diff-report.csv - contains diff report for test run/test suite run.

          • processed-messages-report.csv - contains processed messages report for test run/test suite run.

        The report type is defined from Use bundled CSV report generation strategy property configured on Application configuration page. If it’s true, the report type is zip, otherwise, it’s xlsx.

      4. View results opens Test Run Details page.

  2. Alerts tab shows alerts attached to the ticket.

  3. Transports tab shows linked transports (see transport page for details about transports) and looks:

    ticket transports

    Here you can:

    1. View transport details clicking on its details button. It opens transport page.

    2. Delete selected transports clicking on red trash button.

  4. Reports tab contains built reports and looks:

    ticket reports

    Here you can:

    1. Build new report clicking on Report button. It starts report building and new row is added to the table (with IN PROGRESS status). To get built report wait for a while and click on Refresh button.

    2. Download built xlsx report clicking on report button.

    3. Delete a report clicking on its decline button.

  5. Transports Overview shows relationship between tickets and transports in CPI and Api Management composite landscapes so that it clarifies how the set of transports has been done in the history.

    Include lookup by transported object version enables browsing of other graphs that also cover the source objects state in the current ticket.