You are able to run specific scenario through integration functionality. As soon as you create scenario, it possible to run through integration, to do that you should define scenario UUID inside envelope XML in integration rule.
Defined scenario UUID should be inside the <envelope> tag as an attribute scenarioUuid='uuidOfScenario'
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<envelope templateUuid="19089ab8-a828-4447-9129-44b1da1cbc9d" templateVersion="f2e1a1c5-15ac-4bfb-bf31-f1ddba652b89" scenarioUuid="e17db760-580a-4192-bc96-a91683123bea">
...
</envelope>
</xsl:template>
</xsl:stylesheet>
The scenario configuration of chain envelopes will be ignored by default if you create an envelope with a defined scenario inside an integration rule. However, you can define the chain UUID inside the <envelope> tag as the chainUuid='uuidOfChain' attribute. If you want to chain all the envelopes created during the integration, this should be a static UUID that should be defined once in the integration rule, but if you want to chain envelopes created for each file extracted during the integration separately, it should be defined dynamically.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<envelope templateUuid="19089ab8-a828-4447-9129-44b1da1cbc9d" templateVersion="f2e1a1c5-15ac-4bfb-bf31-f1ddba652b89" scenarioUuid="e17db760-580a-4192-bc96-a91683123bea" chainUuid="e17db760-580a-4192-bc96-a91683123ben">
...
</envelope>
</xsl:template>
</xsl:stylesheet>