CLOUD Terms & Concepts
This section is about the settings of workflows with SAP Transport Panel functionality (SAP Transport Panel post functions).
Terms
| SAP Transport Panel | This SAP Transport Panel specific panel is displayed in an issue. All transport request links are displayed within this panel and can be added or removed. |
| Create transport | Through the SAP Transport Panel post function Create transport a new transport is created in the connected SAP system via the rest interface, which is connected to the Jira issue. The ID of this new transport is then entered in the stored custom field of the issue (e.g. transport number). |
| Copy & Release Transport | Through the SAP Transport Panel post function Copy and release transport a copy of the transport linked with Jira is created in SAP and released directly. This transport copy is also linked to a new issue in Jira. |
| Release final transport | Through the SAP Transport Panel post function Release final transport the SAP transport with the linked ID from the issue is released |
| Add comment post function | Through the SAP Transport Panel post function Add comment the information of the Transport Panel and specific custom fields can be documented in a issue comment. There is also the option to sent this comment to a group of recipients via e-mail, so that a SAP Admin can manually import the Transports on the respective System. |
| Original transport management workflow | This SAP Transport Panel specific workflow is about the process of the original transports. |
| Import Feedback | The SAP component of the SAP Transport Panel provides the option to configure an Return code feedback per system. This needs to be configured on each relevant system. |
Concepts
The SAP Transport Panel is designed to link your SAP with your Jira instance, so you can manage your SAP transports easily and gain maximum transparency throughout the entire development process. In order for this to work we had to develop two components for the interface. One for SAP, one for Jira. The SAP component was developed by NTT DATA, a worldwide operating SAP Partner. The Jira component was developed by greenique, an Atlassian Platinum Solution Partner. Together they form an interface (SAP Transport Panel), so your SAP and Jira instances can communicate. However, both components need a proper implementation on your systems which will be done by NTT DATA and greenique to ensure the functionality of the app.
With SAP Transport Panel creating and releasing a transport follows status changes of a Jira issue. REST calls to an interface enable control of the transport in SAP. These calls are attached to a individual Jira Workflow. This enables you to automatically create a transport for a issue, when you move your Jira issue along your workflow and get the necessary transport automatically in SAP. In addition you can link several transports to one issue. This makes the creation of a transport as easy as drag and drop. Moving your Jira issue along your Kanban board will create or release a transport depending on the corresponding status.
The preferred workflow from greenique provides a solution for the creation, release and the automatic transition of issues, when a transport is released on the productive system.
Architecture & data storage
For a cloud app, it is particularly important to know where data is stored. In this case, your data is located in the respective data warehouse in which your Atlassian products are located. In addition, we also have to store the permitted request paths in our code. This is stored in the data warehouse for the Atlassian Marketplace Apps. The SAP data is saved in our SAP component in your SAP systems.
The following pages will help you find your way through all features of your installed app from an administrators perspective to ensure that you have all you need to make the most out of it, for you and the users.