Some standard ‘reusable user exit are available as part of the standard out-of-the-box product.
Unlike the sample user exit Function Modules, the follow User Exits are expected to be immediately reusable by customers without any coding intervention.
| User Exit Name | Purpose |
|---|---|
| /BTI/TE_EXIT_ADDBTTOFORM_0610 | Can be used so that ActiveControl automatically adds Business Task to a Transport Form when the Transport Form is first opened, where the first characters of the Transport Description match the characters in the Reference field of an existing Business Task. |
| /BTI/TE_EXIT_WSCREATESTER_0080 and /BTI/TE_EXIT_WSCHNGTESTER_0082 | These user exits are used as part of a JIRA integration, and attempt a user mapping based on email address stored against the user assigned to the ticket in JIRA and against the same user in SAP. This was added to overcome the issue whereby most userids in JIRA do not match those in SAP |
| /BTI/TE_EXIT_BTLINKJIRA_0040 | This user exit can be used as part of a JIRA integration, to enable a customer to automatically populate a Web Platform URL into a custom field on the JIRA ticket. More information is available in this Knowledge Article |
| /BTI/TE_EXIT_STOP_APPROVE_0635 | This user exit can be used to prevent “Save and Approve” action in a Test Queue, when the test result is “Waiting” or “Information” . More information is available in this Knowledge Article |
| /BTI/TE_EXIT_AUTOADDTFTYP_0610 | This user exit can be used to automatically populate the Transport Form [Type] field values based on the standard SAP transport type. More information is available in this Change Note |
| //BTI/TE_EXIT_JIRAURLONBT_0040 | This user exit can be used to automatically add a URL attachment on a new Business Task created via JIRA integration, to link back to the URL of the JIRA ticket. More information is available in this Change Note |
Post your comment on this topic.